About this Document............................................2 What is NetBSD?................................................2 Changes Between The NetBSD 1.6 and 2.0 Releases................2 Kernel......................................................3 Networking..................................................3 File system.................................................4 Security....................................................4 System administration and user tools........................4 Miscellaneous...............................................4 sun3 specific...............................................5 Important notes about NetBSD 2.0...............................5 The Future of NetBSD...........................................5 Sources of NetBSD..............................................6 NetBSD 2.0 Release Contents....................................6 NetBSD/sun3 subdirectory structure..........................7 Binary distribution sets....................................7 NetBSD/sun3 System Requirements and Supported Devices..........9 Supported hardware..........................................9 Getting the NetBSD System on to Useful Media..................10 Creating boot/install tapes................................10 Boot/Install from NFS server...............................11 Install/Upgrade from CD-ROM................................11 Install/Upgrade via FTP....................................11 Preparing your System for NetBSD installation.................12 Installing the NetBSD System..................................12 Installing from tape.......................................12 Installing from NFS........................................13 Installing from SunOS......................................14 Booting the Miniroot.......................................14 Miniroot install program...................................15 Post installation steps.......................................15 Upgrading a previously-installed NetBSD System................18 Compatibility Issues With Previous NetBSD Releases............19 Issues affecting an upgrade from NetBSD 1.6................19 Using online NetBSD documentation.............................20 Administrivia.................................................20 Thanks go to..................................................21 We are........................................................23 Legal Mumbo-Jumbo.............................................28 The End.......................................................34
This document describes the installation procedure for
It is available in four different formats titled
is one of
less(1)pager utility programs. This is the format in which the on-line man pages are generally presented.
You are reading the HTML version.
The NetBSD Operating System is a fully functional Open Source UNIX-like operating system derived from the University of California, Berkeley Networking Release 2 (Net/2), 4.4BSD-Lite, and 4.4BSD-Lite2 sources. NetBSD runs on fifty four different system architectures (ports), featuring seventeen machine architectures across fifteen distinct CPU families, and is being ported to more. The NetBSD2.0 release contains complete binary releases for many different system architectures. (A few ports are not fully supported at this time and are thus not part of the binary distribution. For information on them, please see the NetBSD web site at http://www.NetBSD.org/.)
NetBSD is a completely integrated system. In addition to its highly portable, high performance kernel, NetBSD features a complete set of user utilities, compilers for several languages, the X Window System, firewall software and numerous other tools, all accompanied by full source code.
NetBSD is a creation of the members of the Internet community. Without the unique cooperation and coordination the net makes possible, it's likely that NetBSD wouldn't exist.
The NetBSD2.0 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 two years of development that went into the NetBSD2.0 release. Some highlights include:
sysctl(9)was switched from a static binding to a dynamic implementation.
satalink(4)and move SATA support from other controllers into this along with adding support for new controllers.
ipf(8)has been upgraded to version 4.1.3.
tcp(4)now implements path MTU discovery blackhole detection (i.e. it will turn off path MTU discovery if the connection is losing).
wi(4)has support for Host-AP mode, allowing Intersil Prism2/2.5/3-based boards to be used to make an 802.11 Access Point.
ipf(8)has been added to
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 sixth major release of NetBSD/sun3.
In order to retain the functionality that a newly installed system can send mail ``out of the box'', the default has changed so that sendmail will now start by default, and listen for host-local connections.
If this behaviour is not desired, you can either
/etc/mail/submit.cfto point to another host,
/etc/mailer.confto point to something else than sendmail, or
/etc/mail/submit.cf, and set the sendmail_suid variable to ``YES'' in
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
users, because it is for
and because of them that
The root directory of the NetBSD2.0 release is organized as follows:
In addition to the files and directories listed above, there is one directory per architecture, for each of the architectures for which NetBSD2.0 has a binary distribution.
The source distribution sets can be found in subdirectories of the
subdirectory of the distribution tree.
They contain the complete sources to the system.
The source distribution sets are as follows:
All the above source sets are located in the
subdirectory of the distribution tree.
The source sets are distributed as compressed tar files.
Except for the
set, which is traditionally unpacked into
all sets may be unpacked into
with the command:
#( cd / ; tar -zxpf - ) < set_name.tgz
In each of the source distribution set directories, there are files which contain the checksums of the files in the directory:
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.
sun3subdirectory of the distribution:
.../NetBSD-2.0/sun3/. It contains the following files and directories:
.morefile contains underlined text using the
more(1)conventions for indicating italic and bold display.
sun3/binary/setssubdirectory of the NetBSD2.0 distribution tree, and are as follows:
/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.
/etcand 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.
/netbsd. You must install this distribution set.
groff(1), all related programs, and their manual pages.
NetBSD maintains its own set of sources for the X Window System in order to assure tight integration and compatibility. These sources are based on XFree86, and tightly track XFree86 releases. They are currently equivalent to XFree86 4.4.0. Binary sets for the X Window System are distributed with NetBSD. The sets are:
The sun3 binary distribution sets are distributed as gzipped tar files
named with the extension
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
command from the root directory (
) of your system.
This utility is used only in a Traditional method installation.
There is a collection of Sun3 and Sun3X kernels in the
subdirectory of the
The ones named
contain a root file system image and should only be used for the
The others are included for convenience.
(Most people will want to use
Please note that these kernels are simply gzipped and are not tar archives.
NetBSD/sun3 2.0 runs on most Sun3 machines, including:
Note that NetBSD/sun3 now includes support for `Sun3X' machines, which used to be supported with a separate NetBSD/sun3x distribution.
The minimal configuration requires 4 MB of RAM and about 80 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 run X or compile the system, more RAM is recommended. Good performance requires 8 MB of RAM, or 16 MB when running the X Window System.
Here is a table of recommended HD partition sizes for a full install:
|Partition||Suggested||+ X||Needed||+ X|
|/ (root)||20 MB||20 MB||15 MB||15 MB|
|/usr||175 MB||205 MB||75 MB||105 MB|
|/var||20 MB||20 MB||5 MB||5 MB|
As you may note, the recommended size of
is 100 MB greater than
This is to leave room for a kernel source and compile tree as
you will probably want to compile your own kernel.
is large and bulky to accommodate all people).
Note that the sun3 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 (10 MB).
If it's not on this list, there is no support for it in this release.
Installation is supported from several media types, including:
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
The boot tape is created as follows:
# cd .../NetBSD-2.0/sun3/installation/tapeimage
# sh MakeBootTape /dev/nrst0
The install tape is created as follows:
# cd .../NetBSD-2.0/sun3/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
this argument is incompatible with the
Consult the tape-related manual pages on the system where the tapes are
created for more details.
If you are using a
system as the boot-server, have a look at
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.
When instructed to boot over the network, your sun3 expects to be
able to download a second stage bootstrap program via
it has acquired its IP address through
It will attempt to download a file using a name derived from the
machine's recently acquired IP address,
and in the case of sun3x machines, an extension which corresponds to the
(It may be handy to have a hexadecimal
calculator for this next step.)
The filename 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.
sun3x machines use a filename suffix of
For example, a sun3 which has been assigned IP address 220.127.116.11
will make an
and a sun3x will try
Normally, this file
is a symbolic link to the
program, which should
be located in a place where the
daemon can find it.
(Remember, many TFTP daemons run in a chroot'ed environment.)
The netboot program may be found in the install 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-rd kernel in the root area
for your client (no other files are needed in the client root) and
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-rd 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(which you get via FTP). Once you have booted netbsd-rd (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
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
you need to know the numeric IP address of the
router closest to the
Finally, you need to know the numeric IP address of the
Sun3 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.
sd2, target 2 is
It might be a good time to run the diagnostics on your Sun3.
First, attach a terminal to the
serial port, then set the
switch to the Diagnostic position, and power-on the machine.
The Diag. switch setting forces console interaction to occur on ttya.
Note that the 3/80 has a
diag switch you can set at
the PROM monitor prompt.
To turn on diag boot mode, do:
q 70b 12
To return to normal boot mode, do:
q 70b 6.
The console location (ttya, ttyb, or keyboard/display) is controlled
by address 0x1F in the EEPROM, which you can examine and change in
the PROM monitor by entering
followed by a numeric value (or
if you don't want to change it).
Console values are:
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.)
The first example will use the tape on SCSI target 4, where the
second will use SCSI target 5.
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/sun3 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 sun3 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.
First, at the Sun PROM monitor prompt, enter a boot command using the network interface as the boot device. On desktop machines this is le, and ie on the others. Examples:
>b le() -s
>b ie() -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 le0 inet 18.104.22.168 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 22.214.171.124.) You may then need to add a default route if the server is on a different subnet:
ssh> route add default 126.96.36.199 1
You can look at the route table using:
ssh> route show
Now mount the NFS file system containing the miniroot image:
ssh> mount -r 188.8.131.52:/server/path /mnt
The procedure is simpler if you have space for an expanded (not compressed) copy of the miniroot image. In that case:
ssh> dd if=/mnt/miniroot of=/dev/rsd0b bs=8k
Otherwise, you will need to use
to expand the miniroot image while copying.
This is tricky because the
(small shell) does not handle
Instead, you first run the reader in the background with its input set
and then run the other program in the foreground with its output to
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.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 184.108.40.206 zcat miniroot.gz
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
with the command
gzip -dc miniroot.gz | dd of=/dev/rsd0b obs=32k
or if you have already decompressed the miniroot
dd if=miniroot.gz of=/dev/rsd0b obs=32k
Finally, reboot the machine and instruct the ROM to boot from the swap device as described in the next section.
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:
The miniroot's install program will:
foo.bar.org. If, during the process of configuring the network interfaces, you make a mistake, you will be able to re-configure that interface by simply selecting it for configuration again.
First-time installation on a system through a method other than the
installation program is possible, but strongly discouraged.
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.
If you or the installation software haven't done any configuration of
the system will drop you into single user mode on first reboot with the
and with the root file system
When the system asks you to choose a shell, simply press
to get to a
If you are asked for a terminal type, respond with
(or whatever is appropriate for your terminal type)
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
You will need to mount your root file system read/write with:
# /sbin/mount -u -w /
Change to the
directory and take a look at the
Modify it to your tastes, making sure that you set
so that your changes will be enabled and a multi-user boot can
Default values for the various programs can be found in
where some in-line documentation may be found.
More complete documentation can be found in
directory is on a separate partition and you do not know how to use
you will have to mount your
partition to gain access to
Do the following:
# mount /usr
# export TERM=vt220
If you have
on a separate partition, you need to repeat that step for it.
After that, you can edit
When you have finished, type
at the prompt to
leave the single-user shell and continue with the multi-user boot.
Other values that need to be set in
for a networked environment are
furthermore add an
along the lines of
or, if you have
To enable proper hostname resolution, you will also want to add an
file or (if you are feeling a little more adventurous) run
for more information.
Instead of manually configuring network and naming service,
DHCP can be used by setting
Other files in
that may require modification or setting up include
After reboot, you can log in as
at the login prompt.
Unless you've set a password in
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
account with good passwords.
By default, root login from the network is disabled (even via
One way to become root over the network is to log in as a different
user that belongs to group
to become root.
Unless you have connected an unusual terminal device as the console
you can just press
when it prompts for
command to add accounts to your system.
if you want to edit the password database.
If you have installed the X Window System, look at the files in
Don't forget to add
to your path in your shell's dot file so that you have access to the X binaries.
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.
2.0/sun3/Allsubdir. You can install them with the following commands under
# PKG_PATH=ftp://ftp.NetBSD.org/pub/NetBSD/packages/2.0/sun3/All # export PKG_PATH # pkg_add -v tcsh # pkg_add -v bash # pkg_add -v perl # pkg_add -v apache # pkg_add -v kde # pkg_add -v mozilla ...
If you are using
then replace the first two lines with the following:
# setenv PKG_PATH ftp://ftp.NetBSD.org/pub/NetBSD/packages/2.0/sun3/All ...
The above commands will install the Tenex-csh and Bourne Again shell, the perl programming language , Apache web server, KDE desktop environment and the Mozilla web browser as well as all the packages they depend on.
/usr/pkgsrc(though other locations work fine), with the commands:
# mkdir /usr/pkgsrc
#( cd /usr/pkgsrc ; tar -zxpf - ) < pkgsrc.tar.gz
After extracting, see the
files in the extraction directory (e.g.
for more information.
/etc/mail/aliasesto forward root mail to the right place. Don't forget to run
/etc/mail/sendmail.cffile will almost definitely need to be adjusted; files aiding in this can be found in
/usr/share/sendmail. See the
READMEfile there for more information. If you prefer postfix as MTA, adjust
/etc/rc.localto run any local daemons you use.
/etcfiles are documented in section 5 of the manual; so just invoking
# man 5 filename
is likely to give you more information on these files.
It is possible to easily upgrade your existing NetBSD/sun3 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:
# /sbin/fsck -pf
# /sbin/mount -a -t nonfs
/usr/shareon an NFS server, you will want to mount those file systems as well. To do this, you will need to enable the network:
# sh /etc/rc.d/network start
the) base binary set:
# cd /
# pax -zrvpe -f Ar /path/to/base.tgz
# cd /usr/mdec
# cp -p ./ufsboot /mnt/ufsboot
#sync ; sleep 1 ; sync
# /usr/sbin/installboot -v /dev/rsd0a bootxx /ufsboot
# cd /
# pax -zrvpe -f path_to_set
Users upgrading from previous versions of NetBSD may wish to bear the following problems and compatibility issues in mind when upgrading to NetBSD2.0.
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:
/etcneed upgrading. These include:
The following issues need to be resolved manually:
postfix(8)configuration files require upgrading.
cd /usr/share/examples/postfix cp post-install postfix-files postfix-script /etc/postfix postfix check
Documentation is available if you first install the manual
(documentation) are denoted by
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
To view the documentation for
# man 5 passwd
If you are unsure of what man page you are looking for, enter
where subject-word is your topic of interest; a list of possibly related man pages will be displayed.
If you've got something to say, do so! We'd like your input. There are various mailing lists available via the mailing list server at majordomo@NetBSD.org. To get help on using the mailing list server, send mail to that address with an empty body, and it will reply with instructions.
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
command shipped with
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:
is encouraged, however, because bugs reported with it
are entered into the
bugs database, and thus can't slip through
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.
Keith Bostic Ralph Campbell Mike Karels Marshall Kirk McKusick
for their ongoing work on BSD systems, support, and encouragement.
AboveNet Communications, Inc. Advanced System Products, Inc. Alex Poylisher Alistair Crooks Andrew Brown Atsushi YOKOYAMA Avalon Computer Systems Bay Area Internet Solutions Ben Collver Bill Coldwell Bill Sommerfeld Brad Salai Brains Corporation, Japan Brian Carlstrom Brian McGroarty Canada Connect Corporation Castor Fu Central Iowa (Model) Railroad Charles Conn Charles D. Cranor Charles M. Hannum Chris Legrow Christer O. Andersson Christopher g. Demetriou Christos Zoulas Chuck Silvers Co-operative Research Centre for Enterprise Distributed Curt Sampson Dave Burgess Dave Rand David Brownlee Demon Internet, UK Derek Fellion Digital Equipment Corporation Distributed Processing Technology Douglas J. Trainor Easynet, UK Ed Braaten Edward Richley Eric and Rosemary Spahr Free Hardware Foundation Greg Gingerich Guenther Grau Harald Koerfgen Harry McDonald Heiko W. Rupp Herb Peyerl Hubert Feyrer Innovation Development Enterprises of America Internet Software Consortium James Chacon Jan Joris Vereijken Jason Birnschein Jason Brazile Jason R. Thorpe Jim Wise John Kohl Jonathan P. Kay Jordan K. Hubbard Kenneth Alan Hornstein Kevin Keith Woo Kimmo Suominen Krister Waldfridsson Lex Wennmacher LinuxFest Northwest Luke Mewburn MS Macro System GmbH, Germany Mark Brinicombe Mark S. Thomas Mason Loring Bliss Mattias Karlsson Michael Graff Michael L. Hitch Michael Richardson Michael Thompson Michael W. James Mike Price Neil J. McRae Noah M. Keiserman Norman R. McBride Numerical Aerospace Simulation Facility, NASA Ames Research Oliver Cahagne Perry E. Metzger Petri T. Koistinen Piermont Information Systems Inc. Precedence Technologies Ltd Ralph Campbell Reinoud Zandijk Richard Nelson Rob Windsor Ross Harvey SDF Public Access Unix, Inc. 501(c)(7) Salient Systems Inc. Scott Ellis Scott Kaplan Simon Burge Soren Jacobsen Soren Jorvang Steve Allen Steve Wadlow SunROOT# Project Ted Lemon Ted Spradley Thor Lancelot Simon Tim Law Tom Coulter Toru Nishimura VMC Harald Frank, Germany Warped Communications, Inc. Wasabi Systems Whitecross Database Systems Ltd. William Gnadt Worria Web Hosting
(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.)
(in alphabetical order)
|The NetBSD core group:|
|Frank van der Linden||fvdl@NetBSD.org|
|The portmasters (and their ports):|
|Frank van der Linden||fvdl@NetBSD.org||amd64|
|Frank van der Linden||fvdl@NetBSD.org||i386|
|Jun-ichiro itojun Hagino||itojun@NetBSD.org||evbsh3|
|Jun-ichiro itojun Hagino||itojun@NetBSD.org||mmeye|
|The NetBSD 2.0 Release Engineering team:|
|Jun-ichiro itojun Hagino||itojun@NetBSD.org|
|Robert V. Baron||rvb@NetBSD.org|
|Mason Loring Bliss||mason@NetBSD.org|
|D'Arcy J.M. Cain||darcy@NetBSD.org|
|Chris G. Demetriou||cgd@NetBSD.org|
|Tracy Di Marco White||gendalia@NetBSD.org|
|Jason R. Fink||jrf@NetBSD.org|
|Simon J. Gerraty||sjg@NetBSD.org|
|Brian C. Grayson||bgrayson@NetBSD.org|
|Jun-ichiro itojun Hagino||itojun@NetBSD.org|
|Charles M. Hannum||mycroft@NetBSD.org|
|Michael L. Hitch||mhitch@NetBSD.org|
|Christian E. Hopps||chopps@NetBSD.org|
|Love Hörnquist Åstrand||lha@NetBSD.org|
|Lonhyn T. Jasinskyj||lonhyn@NetBSD.org|
|Min Sik Kim||minskim@NetBSD.org|
|Daniel de Kok||daniel@NetBSD.org|
|Johnny C. Lam||jlam@NetBSD.org|
|Martin J. Laubach||mjl@NetBSD.org|
|Frank van der Linden||fvdl@NetBSD.org|
|Jared D. McNeill||jmcneill@NetBSD.org|
|Neil J. McRae||neil@NetBSD.org|
|Juan Romero Pardines||xtraeme@NetBSD.org|
|Julio M. Merino Vidal||jmmv@NetBSD.org|
|Jeremy C. Reed||reed@NetBSD.org|
|Tyler R. Retzlaff||rtr@NetBSD.org|
|Heiko W. Rupp||hwr@NetBSD.org|
|Karl Schilke (rAT)||rat@NetBSD.org|
|Thor Lancelot Simon||tls@NetBSD.org|
|Ian Lance Taylor||ian@NetBSD.org|
|Brian R. Gaekeemail@example.com|
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 University of California, Berkeley and its contributors.