About this Document............................................2
What is NetBSD?................................................2
Changes Between The NetBSD 3.1 release and 3.1.1 update........3
Supported devices...........................................3
Kernel......................................................3
Networking..................................................3
File system.................................................3
Security....................................................3
Miscellaneous...............................................4
alpha specific..............................................4
mac68k specific.............................................4
sparc specific..............................................4
xen specific................................................4
The Future of NetBSD...........................................4
Sources of NetBSD..............................................5
NetBSD 3.1.1 Release Contents..................................5
NetBSD/evbppc subdirectory structure........................6
Binary distribution sets....................................7
NetBSD/evbppc System Requirements and Supported Devices........8
Supported devices...........................................8
Unsupported devices.........................................9
Supported boot devices and media............................9
Getting the NetBSD System on to Useful Media..................10
Preparing your System for NetBSD installation.................12
Booting over a serial line.................................12
Booting from the network...................................12
Installing the NetBSD System..................................16
Booting the installer......................................16
Example of a normal boot...................................16
Common Problems and Error Messages.........................16
Running the sysinst installation program...................16
Introduction............................................16
Possible PCMCIA issues..................................16
General.................................................17
Quick install...........................................17
Booting NetBSD..........................................18
Network configuration...................................18
Installation drive selection and parameters.............18
Partitioning the disk...................................19
Preparing your hard disk................................19
Getting the distribution sets...........................19
Installation using ftp..................................20
Installation using NFS..................................20
Installation from CD-ROM................................20
Installation from an unmounted file system..............20
Installation from a local directory.....................21
Extracting the distribution sets........................21
Finalizing your installation............................21
Post installation steps.......................................21
Upgrading a previously-installed NetBSD System................24
Compatibility Issues With Previous NetBSD Releases............24
Issues affecting an upgrade from NetBSD 3.1 and older......24
Using online NetBSD documentation.............................24
Administrivia.................................................25
Thanks go to..................................................25
We are........................................................30
Legal Mumbo-Jumbo.............................................36
The End.......................................................42
This document describes the installation procedure for
NetBSD3.1.1
on the
evbppc
platform.
It is available in four different formats titled
INSTALL.ext,
where
.ext
is one of
.ps, .html, .more,
or .txt:
.ps.html.moremore(1)
and
less(1)
pager utility programs.
This is the format in which the on-line
man
pages are generally presented.
.txtYou 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 NetBSD3.1.1 release contains complete binary releases for many different system architectures. (A few ports are not fully supported at this time and are thus not part of the binary distribution. For information on them, please see the NetBSD web site at http://www.NetBSD.org/.)
NetBSD is a completely integrated system. In addition to its highly portable, high performance kernel, NetBSD features a complete set of user utilities, compilers for several languages, the X Window System, firewall software and numerous other tools, all accompanied by full source code.
NetBSD is a creation of the members of the Internet community. Without the unique cooperation and coordination the net makes possible, it's likely that NetBSD wouldn't exist.
The NetBSD 3.1.1 update is the first security/critical update of the NetBSD 3.1 release branch. This represents a selected subset of fixes deemed critical in nature for stability or security reasons.
These fixes will also appear in future releases (NetBSD 3.2 etc), together with other less-critical fixes and feature enhancements.
Specific updates are as follows:
wd(4):
fix broken Seagate drive ST3160811A.
vnd(4)
image with block size 0 to avoid a kernel panic.
dhcpd.conf(5)
to make
dhcpd(8)
use the DNS hostname as the DHCP hostname given to the client.
ipfilter(4).
dump(8)
when using -X (filesystem internal snapshots).
glob(3),
which affected
ftpd(8)
and possibly other programs (SA2006-027).
iso(4)
which could potentially lead to a local root compromise (SA2007-004).
file(1)
which could lead to an exploitable heap overflow.
racoon(8)
which could allow an attacker to disrupt a connection between IPSec peers.
veriexec(4)
flaws have been fixed: users can no longer rename a file to a veriexec
protected file or run unfingerprinted files at strict level two or above.
file(1)
has been updated to version 4.21, including and integer underflow and an
integer overflow fix (CVE-2007-1536 and CVE-2007-2799).
etcupdate(8)
for upgrading.
passwd(1):
display a message indicating who's password is being changed, to avoid
confusion after
su(1).
This is the third major release of NetBSD/evbppc.
The NetBSD Foundation has been incorporated as a non-profit organization. Its purpose is to encourage, foster and promote the free exchange of computer software, namely the NetBSD Operating System. The foundation will allow for many things to be handled more smoothly than could be done with our previous informal organization. In particular, it provides the framework to deal with other parties that wish to become involved in the NetBSD Project.
The NetBSD Foundation will help improve the quality of NetBSD by:
We intend to begin narrowing the time delay between releases. Our ambition is to provide a full release every six to eight months.
We hope to support even more hardware in the future, and we have a rather large number of other ideas about what can be done to improve NetBSD.
We intend to continue our current practice of making the NetBSD-current development source available on a daily basis.
We intend to integrate free, positive changes from whatever sources submit them, providing that they are well thought-out and increase the usability of the system.
Above all, we hope to create a stable and accessible system, and to be
responsive to the needs and desires of
NetBSD
users, because it is for
and because of them that
NetBSD
exists.
Refer to
http://www.NetBSD.org/mirrors/.
The root directory of the NetBSD3.1.1 release is organized as follows:
.../NetBSD-3.1.1/
CHANGESLAST_MINUTEMIRRORSREADME.filesTODOpatches/source/In addition to the files and directories listed above, there is one directory per architecture, for each of the architectures for which NetBSD3.1.1 has a binary distribution.
The source distribution sets can be found in subdirectories of the
source
subdirectory of the distribution tree.
They contain the complete sources to the system.
The source distribution sets are as follows:
config(8);
and
dbsym(8).
All the above source sets are located in the
source/sets
subdirectory of the distribution tree.
The source sets are distributed as compressed tar files.
Except for the
pkgsrc
set, which is traditionally unpacked into
/usr/pkgsrc,
all sets may be unpacked into
/usr/src
with the command:
#( cd / ; tar -zxpf - ) < set_name.tgz
In each of the source distribution set directories, there are files which contain the checksums of the files in the directory:
BSDSUMCKSUMMD5SYSVSUMThe 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.
evbppc
subdirectory of the distribution:
.../NetBSD-3.1.1/evbppc/.
It contains the following files and directories:
INSTALL.htmlINSTALL.psINSTALL.txtINSTALL.more.more
file contains underlined text using the
more(1)
conventions for indicating italic and bold display.
binary/kernel/netbsd-WALNUT.gznetbsd.img-WALNUT.gznetbsd-INSTALL_WALNUT.gznetbsd-INSTALL_WALNUT.img.gzsets/installation/evbppc/binary/sets
subdirectory
of the
NetBSD3.1.1
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.
/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.
/netbsd
and the same kernel in the format needed by the bootloader as
/netbsd.img.
These kernels are specific to the IBM 405GP based Walnut evaluation board.
You
must
install this distribution set.
/usr/share.
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 evbppc binary distribution sets are distributed as gzipped tar files
named with the extension
.tgz,
e.g.
base.tgz.
The instructions given for extracting the source sets work equally
well for the binary sets, but it is worth noting that if you use that
method, the filenames stored in the sets are relative and therefore
the files are extracted
below the current directory.
Therefore, if you want to extract the binaries into your system, i.e.
replace the system binaries with them, you have to run the
tar -xpf
command from the root directory (
/
) of your system.
This utility is used only in a Traditional method installation.
NetBSD/evbppc is a port of NetBSD to PowerPC based evaluation board. At the present time, the IBM PowerPC 405GP based walnut evaluation board is the only board supported by this port. As a result, this documentation is specific to installing NetBSD/evbppc on that particular piece of hardware. More evaluation boards will be added in due course, and this documentation will be updated accordingly.
Note: This does not concern booting the kernel itself, since that is done by the firmware. For using an NFS root you will have to provide a supported network card, though.
The first step is setting the IP addresses of both the walnut itself and the host that will be serving the kernel image. From the main menu, choose 3 to set the IP address of the machine:
1 - Enable/disable tests
2 - Enable/disable boot devices
3 - Change IP addresses
4 - Ping test
5 - Toggle ROM monitor debugger
6 - Toggle automatic menu
7 - Display configuration
8 - Save changes to configuration
9 - Set baud rate for s1 boot
A - Enable/disable I cache (Enabled )
B - Enable/disable D cache (Enabled )
0 - Exit menu and continue
-> 3
Set the IP address for the local Ethernet with 1:
--- CHANGE IP ADDRESS ---
Device List:
001 Enabled Ethernet [ENET]
local=0.0.0.0 remote=0.0.0.0 hwaddr=0004ace312bd
004 Disabled Serial Port 2 [S2]
local=8.1.1.2 remote=255.255.255.255 hwaddr=ffffffffffff
----------------------------
select device to change ->1
1 - Change local address
2 - Change remote address
0 - Return to main menu
->1
Current IP address = (0.0.0.0)
Enter new IP address ->Enter IP address in dot notation, (eg. 8.1.1.2)
Here you enter the machine's IP address, e.g. 10.0.0.1. Now you need to do the same thing to set the host IP address (choice 2 from the menu above).
Once both the local and remote addresses are set, you can use the ping test to make sure the ethernet is working; or you can simply use option 0, "Exit menu and continue" to try to boot the machine, if you already set up the remote machine to provide a kernel image. For details on how to do that, see the Booting from the network section below.
You should now be able to boot the operating system.
Note that if you are installing or upgrading from a writable media, the media can be write-protected if you wish. These systems mount a root image from inside the kernel, and will not need to write to the media. If you booted from a floppy, the floppy disk may be removed from the drive after the system has booted.
Installation is supported from several media types, including:
The steps necessary to prepare the distribution sets for installation depend upon which installation medium you choose. The steps for the various media are outlined below.
binary/sets
and
evbppc/binary/sets.
Proceed to the instruction on installation.
split(1)
command, running e.g.
split -b 235k base.tgz base.
to split the
base.tgz
file from
evbppc/binary/sets
into files named
base.aa,
base.ab,
and so on.
Repeat this for all
set_name.tgz
files, splitting them into
set_name.xx
files.
Count the number of
set_name.xx
files that make up the
distribution sets you want to install or upgrade.
You will need one sixth that number of 1.44 MB floppies.
Format all of the floppies with
MS-DOS.
Do
not
make any of them bootable
MS-DOS
floppies, i.e. don't use
format /s
to format them.
(If the floppies are bootable, then the
MS-DOS
system files that make them bootable will take up some space, and you
won't be able to fit the distribution set parts on the disks.)
If you're using floppies that are formatted for
MS-DOS
by their manufacturers, they probably aren't bootable, and you can use
them out of the box.
Place all of the
set_name.xx
files on the
MS-DOS
disks.
Once you have the files on MS-DOS disks, 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.
204.152.184.75
and the IPv6 address is
2001:4f8:4:7:2e0:81ff:fe21:6563
(as of June, 2004).
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.
/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 you don't have DHCP available on your network and the server is not on a network directly connected to the machine on which you're installing or upgrading NetBSD, you need to know the numeric IP address of the router closest to the NetBSD machine. Finally, you need to know the numeric IP address of the NetBSD machine itself.
Once the NFS server is set up properly and you have the information mentioned above, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading.
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-3.1.1
# cd evbppc/binary
# tar -cf tape_device misc etc kern
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.
When installing NetBSD for your NetBSD/evbppc system, you have two options: Via serial port or via network. The firmware does not support loading the kernel from a disk.
To netboot a evbppc, you must configure one or more servers to provide
information and files to your evbppc (the
`client ).'
If you are using
NetBSD
(any architecture) on your netboot server(s), the information
provided here should be sufficient to configure everything.
Additionally, you may wish to look at the
diskless(8)
manual page and the manual pages for each daemon you'll be configuring.
If the server(s) are another operating system, you should consult the
NetBSD Diskless HOW-TO, which will walk you through the steps necessary to
configure the netboot services on a variety of platforms.
http://www.NetBSD.org/Documentation/network/netboot/
You may either netboot the installer so you can install onto a locally attached disk, or you may run your system entirely over the network.
Briefly, the netboot
process involves discovery, kernel and file system stages.
In the first stage, the client discovers information
about where to find the kernel image.
Once the kernel is loaded, it starts executing.
For RAM disk kernels, it mounts the RAM disk file system and begins
executing the installer from the RAM disk.
For normal (non-RAM disk) kernels, the
kernel tries to mount the NFS share that had the kernel and starts
executing
the installation tools or
init(8).
All evbppc systems use BOOTP for the discovery stage.
TFTP is used in the bootstrap phase to download
the kernel via the on-board Ethernet card by the firmware.
Thus,
NetBSD
support for the on-board card is not needed in this step.
For NFS mounting a file system on the other hand,
NetBSD
support for the Ethernet card is needed, and the on-board one
will not suffice; you have to provide a second Ethernet card
supported by
NetBSD.
We will use
`CC:CC:CC:CC:CC:CC'
as the MAC address (ethernet hardware address) of your netboot client
machine.
You should have determined this address in an earlier stage.
In this example, we will use
`192.168.1.10'
as the IP address of your client and
`client.test.net'
as its name.
We will assume you're providing all of your netboot services
on one machine called
`server.test.net'
with the client's files exported from the directory
/export/client/root.
You should, of course, replace all of these with the names, addresses,
and paths appropriate to your environment.
You should set up each netboot stage in order (i.e. discovery, bootstrap, kernel, and then file system) so that you can test them as you proceed.
dhcpd(8)
in
bootpd(8)
compatible mode
Put the following lines in your
/etc/dhcpd.conf
(see
dhcpd.conf(5)
and
dhcp-options(5)
for more information):
ddns-update-style none;
# Do not use any dynamic DNS features
#
allow bootp; # Allow bootp requests, thus the dhcp server
# will act as a bootp server.
#
authoritative; # master DHCP server for this subnet
#
subnet 192.168.1.0 netmask 255.255.255.0 {
# Which network interface to listen on.
# The zeros indicate the range of addresses
# that are allowed to connect.
}
group {
# Set of parameters common to all clients
# in this "group".
#
option broadcast-address 192.168.1.255;
option domain-name "test.net";
option domain-name-servers dns.test.net;
option routers router.test.net;
option subnet-mask 255.255.255.0;
#
# An individual client.
#
host client.test.net {
hardware ethernet CC:CC:CC:CC:CC:CC;
fixed-address 192.168.1.10;
#
# Name of the host (if the fixed address
# doesn't resolve to a simple name).
#
option host-name "client";
#
# Name of the kernel image to download via tftp.
# Note: Plain (ELF) kernels won't work, you
# have to use the corresponding *.img file.
#
filename "netbsd-INSTALL_WALNUT.img"
#
# Name of the bootloader or kernel
# to download via tftp.
#
# The path on the NFS server.
#
option root-path "/export/client/root";
#
# If your DHCP server is not your NFS server, supply the
# address of the NFS server. Since we assume you run everything
# on one server, this is not needed.
#
# next-server server.test.net;
}
#you may paste another "host" entry here for additional
#clients on this network
}
You will need to make sure that the
dhcpd.leases
file exists.
# touch /var/db/dhcpd.leases
You will need to start the dhcpd. If it's already running, you will need to restart it to force it to re-read its configuration file. If the server is running NetBSD, you can achieve this with:
# /etc/rc.d/dhcpd restart
tftpd(8)
The default configuration of the TFTP server is to run in a
chroot(8)
environment in the
/tftpboot
directory.
Thus, the first order of business is to create this directory:
# mkdir -p /tftpboot
Next, edit
/etc/inetd.conf
and uncomment the line with the TFTP daemon:
tftp dgram udp wait root /usr/libexec/tftpd tftpd -l -s /tftpboot
Now, restart
inetd(8).
If the server is running
NetBSD,
you can achieve this with:
# /etc/rc.d/inetd restart
Now, you need to copy the
kernel
for your evbppc machine to
/tftpboot.
Just to be sure, let's make everything readable.
# chmod -R a+rX /tftpboot
Sometimes, the
arp(8)
table gets messed up, and the TFTP server can't communicate with the
client.
In this case, it will write a log message (via
syslogd(8))
to
/var/log/messages
saying:
`tftpd: write: Host is down'.
If this is the case, you may need to force the server to map your client's
ethernet address to its IP address:
# arp -s client CC:CC:CC:CC:CC:CC
nfsd(8),
mountd(8),
and
rpcbind(8)
You can either boot a kernel, or the RAM disk-based installer
binary/kernel/netbsd-INSTALL.img.gz.
In the first case you'll also need an NFS-mounted userland.
Let's set up the NFS server.
Create the directory you are exporting for the netboot client:
# mkdir -p /export/client/root
Put the following line in
/etc/exports
to enable NFS sharing:
/export/client/root -maproot=root client.test.net
If your server is currently running an NFS server, you only need to
restart
mountd(8).
Otherwise, you need to start
rpcbind(8)
and
nfsd(8).
If the server is running
NetBSD,
you can achieve this with:
# /etc/rc.d/rpcbind start
# /etc/rc.d/nfsd start
# /etc/rc.d/mountd restart
If you are netbooting the installer, use
binary/kernel/netbsd-INSTALL_WALNUT.img.gz
(this has the installation tools in a RAM disk).
Also, copy the distribution files to the client's root directory.
# cp *tgz /export/client/root
# gunzip netbsd-INSTALL.img.gz
# mv netbsd-INSTALL.img /export/client/root/netbsd
If you are running your evbppc diskless, simply use
binary/kernel/netbsd.img-WALNUT.gz.
You can skip this step if you do not plan to run your client diskless after installation. Otherwise, you need to extract and set up the client's installation of NetBSD. The Diskless HOW-TO describes how to provide better security and save space on the NFS server over the procedure listed here. http://www.NetBSD.org/Documentation/network/netboot/nfs.html
# cd /export/client/root
# tar -xpzf /path/to/files/base.tgz
# tar -xpzf /path/to/files/etc.tgz
Continue with the other non-essential distribution sets if desired.
# mkdir /export/client/root/swap
# dd if=/dev/zero of=/export/client/swap bs=4k count=4k
# echo '/export/client/swap -maproot=root:wheel client.test.net' | cat >> /etc/exports
# /etc/rc.d/mountd restart
# cd /export/client/root/dev
# ./MAKEDEV all
This procedure only works on NetBSD hosts.
fstab(5)
Create a file in
/export/client/root/etc/fstab
with the following lines:
server:/export/client/swap none swap sw,nfsmntpt=/swap
server:/export/client/root / nfs rw 0 0
rc.conf(5)
Edit
/export/client/root/etc/rc.conf
rc_configured=YES
hostname="client"
defaultroute="192.168.1.1"
nfs_client=YES
auto_ifconfig=NO
net_interfaces=""
Make sure rc does not reconfigure the network device since it will lose its connection to the NFS server with your root file system.
hosts(5)
file.
Edit
/export/client/root/etc/hosts
::1 localhost
127.0.0.1 localhost
192.168.1.10 client.test.net client
192.168.1.5 server.test.net server
If you want
these services to start up every time you boot
your server, make sure the following lines are present in your
/etc/rc.conf:
nfs_server=YES # enable server daemons
mountd=YES
rpcbind=YES rpcbind_flags="-l" # -l logs libwrap
Also, you'll need to make sure the
tftpd
line in
/etc/inetd.conf
remains uncommented.
/netbsd
on your root file system, otherwise some kernel grovellers won't work.
Using sysinst, installing NetBSD is a relatively easy process. You still should read this document and have it in hand when doing the installation process. This document tries to be a good guideline for the installation and as such covers many details for the sake of completeness. Do not let this discourage you; the install program is not hard to use.
Machines with PCMCIA slots may have problems during installation. If you do not have PCMCIA on your machine (PCMCIA is only really used on laptop machines), you can skip this section, and ignore the ``[PCMCIA]'' notes. If you do have PCMCIA in your machine, you can safely ignore this section and the ``[PCMCIA]'' the first time, as you are likely to not have problems. Should troubles occur during floppy boot, they may be PCMCIA specific. You should then re-read this section and try again, following the instructions in the ``[PCMCIA]'' notes.
This section explains how to work around the installation problem.
The kernel keeps careful track of what interrupts
and I/O ports are in use during autoconfiguration.
It then allows the
PCMCIA
devices to pick unused interrupts and I/O ports.
Unfortunately, the
INSTALL
kernel may not detect all devices in your system.
This may be because the
INSTALL
kernel only supports the minimum set of devices to install
NetBSD
on your system, or it may be that
NetBSD
does not have support for the device causing the conflict.
For example, suppose your laptop has a
soundblaster device built in; the
INSTALL
kernel has no sound support.
The
PCMCIA
code might allocate your soundblaster's
IRQ
and I/O ports to
PCMCIA
devices, causing them not to work, or to lock up the system.
This is especially bad if one of the devices in question is your ethernet card.
The kernel attempts to probe for available interrupts that are usable by the PCIC (PCMCIA interrupt controller), which should alleviate interrupt conflicts; however, I/O port conflicts are still possible.
This problem will impact some, but not all, users of PCMCIA. If this problem is affecting you, watch the ``[PCMCIA]'' notes that will appear in this document.
The following is a walk-through of the steps you will take while
getting
NetBSD
installed on your hard disk.
sysinst
is a menu driven
installation system that allows for some freedom in doing the
installation.
Sometimes, questions will be asked and in many cases
the default answer will be displayed in brackets
(``[ ]'')
after the question.
If you wish to stop the installation, you may press
CONTROL-C
at any time, but if you do, you'll have to begin the installation
process again from scratch by running the
/sysinst
program from the command prompt.
It is not necessary to reboot.
First, let's describe a quick install. The other sections of this document go into the installation procedure in more detail, but you may find that you do not need this. If you want detailed instructions, skip to the next section. This section describes a basic installation, using a CD-ROM install as an example.
.***********************************************.
* NetBSD-3.1.1 Install System *
* *
*>a: Install NetBSD to hard disk *
* b: Upgrade NetBSD on a hard disk *
* c: Re-install sets or install additional sets *
* d: Reboot the computer *
* e: Utility menu *
* x: Exit Install System *
.***********************************************.
root,
and set a password for that account.
You are also advised to edit the file
/etc/rc.conf
to match your system needs.
/usr/X11R6/lib/X11/doc.
Further information can be found on
http://www.xfree86.org/.
You may want to read the
boot messages, to notice your disk's name and capacity.
Its name will be something like
sd0
or
wd0
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
wd0
is
NetBSD's
name for your first IDE disk,
wd1
the second, etc.
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.
If you will not use network operation during the installation, but you do want your machine to be configured for networking once it is installed, you should first go to the Utility menu, and select the Configure network option. If you only want to temporarily use networking during the installation, you can specify these parameters later. If you are not using the Domain Name System (DNS), you can give an empty response in reply to answers relating to this.
To start the installation, select Install NetBSD to hard disk 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
sd0
or
sd1.
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.
The partition table of the NetBSD part of a disk is called a disklabel. There are 4 layouts for the NetBSD part of the disk that you can pick from: Standard, Standard with X, Custom and Use Existing. The first two use a set of default values (that you can change) suitable for a normal installation, possibly including X. With the Custom option you can specify everything yourself. The last option uses the partition info already present on the disk.
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/)
bcd-pe
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 will be ok for most purposes. If you choose to name it something different, make sure the name is a single word and contains no special characters. You don't need to remember this name.
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.
The NetBSD distribution consists of a number of sets, that come in the form of gzipped tarfiles. A few sets must be installed for a working system, others are optional. At this point of the installation, you will be presented with a menu which enables you to choose from one of the following methods of installing the sets. Some of these methods will first load the sets on your hard disk, others will extract the sets directly.
For all these methods, the first step is making the sets available for extraction, and then do the actual installation. The sets can be made available in a few different ways. The following sections describe each of those methods. After reading the one about the method you will be using, you can continue to the section labeled `Extracting the distribution sets'.
To be able to install using ftp, you first need to configure
your network setup, if you haven't already at the start of
the install procedure.
sysinst
will do this for you, asking you
if you want to use DHCP, and if not
to provide data like IP address, hostname, etc.
If you do not have name service set up for the machine that you
are installing on, you can just press
RETURN
in answer to these questions, and DNS will not be used.
You will also be asked to specify the host that you want to transfer the sets from, the directory on that host, the account name and password used to log into that host using ftp, and optionally a proxy server to use. If you did not set up DNS when answering the questions to configure networking, you will need to specify an IP address instead of a hostname for the ftp server.
sysinst will proceed to transfer all the default set files from the remote site to your hard disk.
To be able to install using NFS, you first need to configure
your network setup, if you haven't already at the start of
the install procedure.
sysinst
will do this for you, asking you
if you want to use DHCP, and if not
to provide data like IP address, hostname, etc.
If you do not have name service set up for the machine that you
are installing on, you can just press
RETURN
in answer to these questions, and DNS will not be used.
You will also be asked to specify the host that you want to transfer the sets from, and the directory on that host that the files are in. This directory should be mountable by the machine you are installing on, i.e. correctly exported to your machine.
If you did not set up DNS when answering the questions to configure networking, you will need to specify an IP address instead of a hostname for the NFS server.
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.
In order to install from a local file system, you will
need to specify the device that the file system resides
on
(for example sd1e)
the type of the file system,
and the directory on the specified file system where the sets are located.
sysinst
will then check if it
can indeed access the sets at that location.
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.
After the install sets containing the NetBSD distribution have been made available, you can either extract all the sets (a full installation), or only extract sets that you have selected. In the latter case, you will be shown the currently selected sets, and given the opportunity to select the sets you want. Some sets always need to be installed (kern, base) and etc they will not be shown in this selection menu.
Before extraction begins, you can elect to watch the files being extracted; the name of each file that is extracted will be shown. This can slow down the installation process considerably, especially on machines with slow graphics consoles or serial consoles.
After all the files have been extracted, all the necessary device node files will be created. If you have already configured networking, you will be asked if you want to use this configuration for normal operation. If so, these values will be installed in the network configuration files. The next menu will allow you to select the time zone that you're in, to make sure your clock has the right offset from UTC. Finally you will be asked to select a password encryption algorithm and can than set a password for the "root" account, to prevent the machine coming up without access restrictions.
Congratulations, you have successfully installed NetBSD3.1.1. You can now reboot the machine, and boot NetBSD from hard disk.
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.
/etc/rc.conf
If you or the installation software haven't done any configuration of
/etc/rc.conf
(sysinst
usually will),
the system will drop you into single user mode on first reboot with the
message
/etc/rc.conf is not configured. Multiuser boot aborted.
and with the root file system
(/)
mounted read-only.
When the system asks you to choose a shell, simply press
RETURN
to get to a
/bin/sh
prompt.
If you are asked for a terminal type, respond with
vt220
(or whatever is appropriate for your terminal type)
and press
RETURN.
You may need to type one of the following commands to get your delete key
to work properly, depending on your keyboard:
# stty erase '^h'
# stty erase '^?'
At this point, you need to configure at least
one file in the
/etc
directory.
You will need to mount your root file system read/write with:
# /sbin/mount -u -w /
Change to the
/etc
directory and take a look at the
/etc/rc.conf
file.
Modify it to your tastes, making sure that you set
rc_configured=YES
so that your changes will be enabled and a multi-user boot can
proceed.
Default values for the various programs can be found in
/etc/defaults/rc.conf,
where some in-line documentation may be found.
More complete documentation can be found in
rc.conf(5).
If your
/usr
directory is on a separate partition and you do not know how to use
ed,
you will have to mount your
/usr
partition to gain access to
ex
or
vi.
Do the following:
# mount /usr
# export TERM=vt220
If you have
/var
on a separate partition, you need to repeat that step for it.
After that, you can edit
/etc/rc.conf
with
vi(1).
When you have finished, type
exit
at the prompt to
leave the single-user shell and continue with the multi-user boot.
Other values that need to be set in
/etc/rc.conf
for a networked environment are
hostname
and possibly
defaultroute,
furthermore add an
ifconfig_int
for your
<int>
network interface,
along the lines of
ifconfig_de0="inet 123.45.67.89 netmask 255.255.255.0"
or, if you have
myname.my.dom
in
/etc/hosts:
ifconfig_de0="inet myname.my.dom netmask 255.255.255.0"
To enable proper hostname resolution, you will also want to add an
/etc/resolv.conf
file or (if you are feeling a little more adventurous) run
named(8).
See
resolv.conf(5)
or
named(8)
for more information.
Instead of manually configuring network and naming service,
DHCP can be used by setting
dhclient=YES
in
/etc/rc.conf.
Other files in
/etc
that may require modification or setting up include
/etc/mailer.conf,
/etc/nsswitch.conf,
and
/etc/wscons.conf.
After reboot, you can log in as
root
at the login prompt.
Unless you've set a password in
sysinst,
there
is no initial password.
If you're using the machine in a networked environment,
you should create an account for yourself (see below) and protect it and the
``root''
account with good passwords.
By default, root login from the network is disabled (even via
ssh(1)).
One way to become root over the network is to log in as a different
user that belongs to group
``wheel''
(see
group(5))
and use
su(1)
to become root.
Unless you have connected an unusual terminal device as the console
you can just press
RETURN
when it prompts for
Terminal type? [...].
Use the
useradd(8)
command to add accounts to your system.
Do not
edit
/etc/passwd
directly! See
vipw(8)
and
pwd_mkdb(8)
if you want to edit the password database.
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.
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.
3.1.1/evbppc/All
subdir.
You can install them with the following commands under
sh(1):
# PKG_PATH=ftp://ftp.NetBSD.org/pub/NetBSD/packages/3.1.1/evbppc/All # export PKG_PATH # pkg_add -v tcsh # pkg_add -v bash # pkg_add -v perl # pkg_add -v apache # pkg_add -v kde # pkg_add -v mozilla ...
If you are using
csh(1)
then replace the first two lines with the following:
# setenv PKG_PATH ftp://ftp.NetBSD.org/pub/NetBSD/packages/3.1.1/evbppc/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
README
and
doc/pkgsrc.txt
files in the extraction directory (e.g.
/usr/pkgsrc/README)
for more information.
/etc/mail/aliases
to forward root mail to the right place.
Don't forget to run
newaliases(1)
afterwards.
/etc/mail/sendmail.cf
file will almost definitely need to be adjusted;
files aiding in this can be found in
/usr/share/sendmail.
See the
README
file there for more information.
If you prefer postfix as MTA, adjust
/etc/mailer.conf.
/etc/rc.local
to run any local daemons you use.
/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.
This is the first release of
NetBSD/evbppc,
and as such, there is no ability to upgrade from a prior release.
Users upgrading from previous versions of NetBSD may wish to bear the following problems and compatibility issues in mind when upgrading to NetBSD3.1.1.
/etc/pam.d
with appropriate configuration files for the Pluggable Authentication Modules
(PAM) because you will not be able to login any more otherwise. Using
postinstall
as described below will take care of this. Please refer to
http://www.netbsd.org/guide/en/chap-pam.html
for documentation about PAM.
The following issues can generally be resolved by extracting the etc set into a temporary directory and running postinstall:
postinstall -s /path/to/etc.tgz check
postinstall -s /path/to/etc.tgz fix
Issues fixed by postinstall:
/etc
need upgrading.
These include:
/etc/defaults/*
/etc/mtree/*
/etc/pam.d/*
/etc/daily
/etc/weekly
/etc/monthly
/etc/security
/etc/rc.subr
/etc/rc
/etc/rc.shutdown
/etc/rc.d/*
The following issues need to be resolved manually:
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.
If you've got something to say, do so! We'd like your input. There are various mailing lists available via the mailing list server at majordomo@NetBSD.org. To get help on using the mailing list server, send mail to that address with an empty body, and it will reply with instructions.
There are various mailing lists set up to deal with comments and questions about this release. Please send comments to: netbsd-comments@NetBSD.org.
To report bugs, use the
send-pr(1)
command shipped with
NetBSD,
and fill in as much information about the problem as you can.
Good bug reports include lots of details.
Additionally, bug reports can be sent by mail to:
netbsd-bugs@NetBSD.org.
Use of
send-pr(1)
is encouraged, however, because bugs reported with it
are entered into the
NetBSD
bugs database, and thus can't slip through
the cracks.
There are also port-specific mailing lists, to discuss aspects of each port of NetBSD. Use majordomo to find their addresses, or visit http://www.NetBSD.org/MailingLists/. If you're interested in doing a serious amount of work on a specific port, you probably should contact the `owner' of that port (listed below).
If you'd like to help with this effort, and have an idea as to how you could be useful, send us mail or subscribe to: netbsd-help@NetBSD.org.
As a favor, please avoid mailing huge documents or files to these mailing lists. Instead, put the material you would have sent up for FTP or WWW somewhere, then mail the appropriate list about it, or, if you'd rather not do that, mail the list saying you'll send the data to those who want it.
Keith Bostic Ralph Campbell Mike Karels Marshall Kirk McKusick
for their ongoing work on BSD systems, support, and encouragement.
AMD - Advanced Micro Devices, Inc. ASA Computers Aaron Wall ABE Masayuki AboveNet Communications, Inc. Achim Grolms Adam Kasper Adaptec Advanced System Products, Inc. Akihiro IIJIMA Alex Poylisher Algorithmics, Ltd. Alistair Crooks Allegro Networks Aloys Keller Andreas Berg Andreas Jellinghaus Andrew Brown Andrew Gillham Andy Hagans Antonio Larripa Arend Harrewijne Armijn Hemel Atsushi YOKOYAMA Avalon Computer Systems Bay Area Internet Solutions Ben Collver Benoit Lepage Bernhard Moellemann Bill Coldwell Bill Sommerfeld Bill Squier Brad Salai Brains Corporation, Japan Brian Carlstrom Brian McGroarty Brian Mitchell Canada Connect Corporation Carl Shapiro Castor Fu Central Iowa (Model) Railroad Charles Conn Charles D. Cranor Charles M. Hannum Chris Legrow Chris Townsend Christer O. Andersson Christopher G. Demetriou Christos Zoulas Chuck Silvers Cologne Chip AG Computer und Literatur Verlag Computertechnik Krienke & Nolte Computing Services Department, The University of Liverpool Convert Tools Co-operative Research Centre for Enterprise Distributed Curt Sampson DAYOMON from Japan Damicon Kraa, Finland Daniel de Kok Dave Burgess Dave Rand Dave Tyson David Brownlee Dayton Clark Demon Internet, UK Derek Fellion Digital Equipment Corporation Distributed Processing Technology Distro Jockey Douglas J. Trainor Dr.ir. F.W. Dillema Easynet, UK Ed Braaten Edward Richley emuty Eric and Rosemary Spahr Erik Berls Erik E. Fair Erkki Ruohtula Ernst Lehmann Espen Randen Ewald Kicker Florent Parent Frank Kardel Free Hardware Foundation Front Range *BSD User Group FUKAUMI Naoki Gan Uesli Starling Garth R. Patil Geert Hendrickx (ghen) Geert Jan de Groot GK Meier Gordon Zaft Grant Beattie Greg Gingerich Greg Girczyc Guenther Grau HP Sweden Hanno Wagner Hans Huebner Harald Koerfgen Haroon Khalid Harry McDonald Hauke Fath Heiko W. Rupp Herb Peyerl Hernani Marques Madeira Hidekichi Ookubo Hideyuki Kido Hisashi Fujinaka Holger Weiss Hubert Feyrer IBM Corporation IMAI Kiyoshi Innovation Development Enterprises of America Intel Internet Software Consortium Internet Users Forever IKI Interoute Telecommunications, UK JNUG (raised at JNUG meeting & BOF August 2005) James Bursa James Chacon Jan Joris Vereijken Jason Birnschein Jason Brazile Jason R. Thorpe Jeff Rizzo Jeff Woodall - Portland, OR Jens Schoenfeld Jim Wise Joachim Nink Joachim Thiemann Joel CARNAT John Heasley John Kohl John P. Refling Jonathan P. Kay Jordan K. Hubbard Jorgen Lundman Karl Wagner Kenji Hisazumi Kenneth Alan Hornstein Kenneth P. Stox Kevin Keith Woo Kevin Sullivan Klaus Lichti Kimmo Suominen Korea BSD User Forum Krister Waldfridsson Kwok Ng Lars Mathiassen Lehmanns Fachbochhandlung Lex Wennmacher LinuxFest Northwest Luke Maurits Luke Mewburn MS Macro System GmbH, Germany Maki Kato Marc Tooley Marcus Wyremblewski Mark Brinicombe Mark Houde Mark Perkins Mark S. Thomas Mason Loring Bliss Martin Cernohorsky Martin J. Ekendahl Matt Dainty Matt Thomas Matthew Jacob Matthew Sporleder Matthias Scheler Mattias Karlsson Mel Kravitz Michael Graff Michael "Kvedulv" Moll Michael L. Hitch Michael Richardson Michael Thompson Michael W. James Mike Price Mirko Thiesen (Thiesi) Murphy Software BV, Netherlands Neil J. McRae Noah M. Keiserman Norman R. McBride Numerical Aerospace Simulation Facility, NASA Ames Research Olaf "Rhialto" Seibert Oliver Cahagne Oppedahl & Larson LLP Palle Lyckegaard Paul Ripke Paul Southworth Pawel Rogocz Pearson Education Perry E. Metzger Petar Bogdanovic Peter C. Wallace Peter J. Bui Peter Postma Petri T. Koistinen Phil Thomas Piermont Information Systems Inc. Pierre-Philipp Braun Precedence Technologies Ltd Public Access Networks Corporation Ralph Campbell Randy Ray Real Weasel Reinoud Zandijk Renewed Health Company Richard Nelson Rob Windsor Robert Pankratz Robert Thille Roland Lichti Ross Harvey Ryan Campbell SDF Public Access Unix, Inc. 501(c)(7) SMC Networks Inc. Salient Systems Inc. Sander van Dijk Scott Ellis Scott Kaplan Scott Walters Sean Davis Simon Burge Soren Jacobsen Soren Jorvang Stephen Borrill Stephen Early Steve Allen Steve Wadlow Steven M. Bellovin SunROOT# Project Sylvain Schmitz Takahiro Kambe TAKEUCHI Yoji Tamotsu Kanoh Tasis Michalakopoulos (Athens, Greece) Tatoku Ogaito Ted Lemon Ted Spradley The Names Database The NetBSD Mission The People's Republic of Ames Thierry Lacoste Thierry Laronde Thomas Runge Thor Lancelot Simon Tim Law Timo Scholer Tino Hanich Tino Wildenhain Tom Coulter Tom Ivar Helbekkmo Tom Lyon Tomas Dabasinskas Torsten Harenberg Toru Nishimura Toshiba Turbocat's Development Tyler Sarna UTN Web Directory VMC Harald Frank, Germany Warped Communications, Inc. Wasabi Systems, Inc. Whitecross Database Systems Ltd. William Gnadt Worria Affordable Web Hosting Worria Web Hosting wwwTrace Traceroute Server Directory Yusuke Yokota Zach Metzinger
(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: | |||
| Allen Briggs | briggs@NetBSD.org | ||
| Matt Thomas | matt@NetBSD.org | ||
| Valeriy E. Ushakov | uwe@NetBSD.org | ||
| YAMAMOTO Takashi | yamt@NetBSD.org | ||
| Christos Zoulas | christos@NetBSD.org | ||
|
| |||
| The portmasters (and their ports): | |||
| Ta | |||
| Allen Briggs | briggs@NetBSD.org | sandpoint | |
| Anders Magnusson | ragge@NetBSD.org | vax | |
| Andrey Petrov | petrov@NetBSD.org | sparc64 | |
| Ben Harris | bjh21@NetBSD.org | acorn26 | |
| Chris Gilbert | chris@NetBSD.org | cats | |
| Christian Limpach | cl@NetBSD.org | xen | |
| Eduardo Horvath | eeh@NetBSD.org | evbppc | |
| Frank van der Linden | fvdl@NetBSD.org | amd64 | |
| Frank van der Linden | fvdl@NetBSD.org | i386 | |
| Gavan Fantom | gavan@NetBSD.org | iyonix | |
| IWAMOTO Toshihiro | toshii@NetBSD.org | hpcarm | |
| Ichiro Fukuhara | ichiro@NetBSD.org | hpcarm | |
| Ignatios Souvatzis | is@NetBSD.org | amiga | |
| Izumi Tsutsui | tsutsui@NetBSD.org | hp300 | |
| Izumi Tsutsui | tsutsui@NetBSD.org | news68k | |
| Jason Thorpe | thorpej@NetBSD.org | algor | |
| Jason Thorpe | thorpej@NetBSD.org | evbarm | |
| Jason Thorpe | thorpej@NetBSD.org | shark | |
| Jeremy Cooper | jeremy@NetBSD.org | sun3 | |
| Jonathan Stone | jonathan@NetBSD.org | pmax | |
| Julian Coleman | jdc@NetBSD.org | atari | |
| Jun-ichiro itojun Hagino | itojun@NetBSD.org | evbsh3 | |
| Jun-ichiro itojun Hagino | itojun@NetBSD.org | mmeye | |
| Kazuki Sakamoto | sakamoto@NetBSD.org | bebox | |
| Lennart Augustsson | augustss@NetBSD.org | pmppc | |
| Marcus Comstedt | marcus@NetBSD.org | dreamcast | |
| Martin Husemann | martin@NetBSD.org | sparc64 | |
| Matt DeBergalis | deberg@NetBSD.org | next68k | |
| Matt Fredette | fredette@NetBSD.org | hp700 | |
| Matt Fredette | fredette@NetBSD.org | sun2 | |
| Matt Thomas | matt@NetBSD.org | alpha | |
| Matt Thomas | matt@NetBSD.org | netwinder | |
| Matthias Drochner | drochner@NetBSD.org | cesfic | |
| NISHIMURA Takeshi | nsmrtks@NetBSD.org | x68k | |
| NONAKA Kimihiro | nonaka@NetBSD.org | prep | |
| Nathan Williams | nathanw@NetBSD.org | sun3 | |
| Noriyuki Soda | soda@NetBSD.org | arc | |
| Paul Kranenburg | pk@NetBSD.org | sparc | |
| Phil Nelson | phil@NetBSD.org | pc532 | |
| Reinoud Zandijk | reinoud@NetBSD.org | acorn32 | |
| Ross Harvey | ross@NetBSD.org | alpha | |
| Søren Jørvang | soren@NetBSD.org | cobalt | |
| Søren Jørvang | soren@NetBSD.org | sgimips | |
| Scott Reynolds | scottr@NetBSD.org | mac68k | |
| Shin Takemura | takemura@NetBSD.org | hpcmips | |
| Simon Burge | simonb@NetBSD.org | evbmips | |
| Simon Burge | simonb@NetBSD.org | evbppc | |
| Simon Burge | simonb@NetBSD.org | pmax | |
| Simon Burge | simonb@NetBSD.org | sbmips | |
| Steve Woodford | scw@NetBSD.org | evbsh5 | |
| Steve Woodford | scw@NetBSD.org | mvme68k | |
| Steve Woodford | scw@NetBSD.org | mvmeppc | |
| Tohru Nishimura | nisimura@NetBSD.org | luna68k | |
| Tsubai Masanari | tsubai@NetBSD.org | macppc | |
| Tsubai Masanari | tsubai@NetBSD.org | newsmips | |
| UCHIYAMA Yasushi | uch@NetBSD.org | hpcsh | |
| UCHIYAMA Yasushi | uch@NetBSD.org | playstation2 | |
| Wayne Knowles | wdk@NetBSD.org | mipsco | |
| Wolfgang Solfrank | ws@NetBSD.org | ofppc | |
|
| |||
| The NetBSD 3.1.1 Release Engineering team: | |||
| Grant Beattie | grant@NetBSD.org | ||
| Erik Berls | cyber@NetBSD.org | ||
| James Chacon | jmc@NetBSD.org | ||
| Julian Coleman | jdc@NetBSD.org | ||
| Håvard Eidnes | he@NetBSD.org | ||
| Jun-ichiro itojun Hagino | itojun@NetBSD.org | ||
| Geert Hendrickx | ghen@NetBSD.org | ||
| Soren Jacobsen | snj@NetBSD.org | ||
| SAITOH Masanobu | msaitoh@NetBSD.org | ||
| Luke Mewburn | lukem@NetBSD.org | ||
| Jeff Rizzo | riz@NetBSD.org | ||
| Matthias Scheler | tron@NetBSD.org | ||
| Curt Sampson | cjs@NetBSD.org | ||
| Jim Wise | jwise@NetBSD.org | ||
|
| |||
| NetBSD Developers: | |||
| Nathan Ahlstrom | nra@NetBSD.org | ||
| Steve Allen | wormey@NetBSD.org | ||
| Jukka Andberg | jandberg@NetBSD.org | ||
| Julian Assange | proff@NetBSD.org | ||
| Lennart Augustsson | augustss@NetBSD.org | ||
| Christoph Badura | bad@NetBSD.org | ||
| Bang Jun-Young | junyoung@NetBSD.org | ||
| Dieter Baron | dillo@NetBSD.org | ||
| Robert V. Baron | rvb@NetBSD.org | ||
| Alan Barrett | apb@NetBSD.org | ||
| Grant Beattie | grant@NetBSD.org | ||
| Jason Beegan | jtb@NetBSD.org | ||
| Erik Berls | cyber@NetBSD.org | ||
| Hiroyuki Bessho | bsh@NetBSD.org | ||
| John Birrell | jb@NetBSD.org | ||
| Mason Loring Bliss | mason@NetBSD.org | ||
| Charles Blundell | cb@NetBSD.org | ||
| Rafal Boni | rafal@NetBSD.org | ||
| Sean Boudreau | seanb@NetBSD.org | ||
| Manuel Bouyer | bouyer@NetBSD.org | ||
| John Brezak | brezak@NetBSD.org | ||
| Allen Briggs | briggs@NetBSD.org | ||
| Mark Brinicombe | mark@NetBSD.org | ||
| Aaron Brown | abrown@NetBSD.org | ||
| Andrew Brown | atatat@NetBSD.org | ||
| David Brownlee | abs@NetBSD.org | ||
| Frederick Bruckman | fredb@NetBSD.org | ||
| Jon Buller | jonb@NetBSD.org | ||
| Simon Burge | simonb@NetBSD.org | ||
| Robert Byrnes | byrnes@NetBSD.org | ||
| D'Arcy J.M. Cain | darcy@NetBSD.org | ||
| Dave Carrel | carrel@NetBSD.org | ||
| Daniel Carosone | dan@NetBSD.org | ||
| James Chacon | jmc@NetBSD.org | ||
| Bill Coldwell | billc@NetBSD.org | ||
| Julian Coleman | jdc@NetBSD.org | ||
| Ben Collver | ben@NetBSD.org | ||
| Jeremy Cooper | jeremy@NetBSD.org | ||
| Chuck Cranor | chuck@NetBSD.org | ||
| Alistair Crooks | agc@NetBSD.org | ||
| Aidan Cully | aidan@NetBSD.org | ||
| Garrett D'Amore | gdamore@NetBSD.org | ||
| Johan Danielsson | joda@NetBSD.org | ||
| John Darrow | jdarrow@NetBSD.org | ||
| Jed Davis | jld@NetBSD.org | ||
| Matt DeBergalis | deberg@NetBSD.org | ||
| Rob Deker | deker@NetBSD.org | ||
| Chris G. Demetriou | cgd@NetBSD.org | ||
| Tracy Di Marco White | gendalia@NetBSD.org | ||
| Jaromír Dolecek | jdolecek@NetBSD.org | ||
| Andy Doran | ad@NetBSD.org | ||
| Roland Dowdeswell | elric@NetBSD.org | ||
| Emmanuel Dreyfus | manu@NetBSD.org | ||
| Matthias Drochner | drochner@NetBSD.org | ||
| Jun Ebihara | jun@NetBSD.org | ||
| Elad Efrat | elad@NetBSD.org | ||
| Håvard Eidnes | he@NetBSD.org | ||
| Stoned Elipot | seb@NetBSD.org | ||
| Michael van Elst | mlelstv@NetBSD.org | ||
| Enami Tsugutomo | enami@NetBSD.org | ||
| Bernd Ernesti | veego@NetBSD.org | ||
| Erik Fair | fair@NetBSD.org | ||
| Gavan Fantom | gavan@NetBSD.org | ||
| Hubert Feyrer | hubertf@NetBSD.org | ||
| Jason R. Fink | jrf@NetBSD.org | ||
| Liam J. Foy | liamjfoy@NetBSD.org | ||
| Matt Fredette | fredette@NetBSD.org | ||
| Thorsten Frueauf | frueauf@NetBSD.org | ||
| Castor Fu | castor@NetBSD.org | ||
| Ichiro Fukuhara | ichiro@NetBSD.org | ||
| Quentin Garnier | cube@NetBSD.org | ||
| Thomas Gerner | thomas@NetBSD.org | ||
| Simon J. Gerraty | sjg@NetBSD.org | ||
| Justin Gibbs | gibbs@NetBSD.org | ||
| Chris Gilbert | chris@NetBSD.org | ||
| Eric Gillespie | epg@NetBSD.org | ||
| Adam Glass | glass@NetBSD.org | ||
| Michael Graff | explorer@NetBSD.org | ||
| Brian C. Grayson | bgrayson@NetBSD.org | ||
| Matthew Green | mrg@NetBSD.org | ||
| Andreas Gustafsson | gson@NetBSD.org | ||
| Jun-ichiro itojun Hagino | itojun@NetBSD.org | ||
| Juergen Hannken-Illjes | hannken@NetBSD.org | ||
| Charles M. Hannum | mycroft@NetBSD.org | ||
| Ben Harris | bjh21@NetBSD.org | ||
| Ross Harvey | ross@NetBSD.org | ||
| Eric Haszlakiewicz | erh@NetBSD.org | ||
| John Hawkinson | jhawk@NetBSD.org | ||
| HAMAJIMA Katsuomi | hamajima@NetBSD.org | ||
| HAYAKAWA Koichi | haya@NetBSD.org | ||
| John Heasley | heas@NetBSD.org | ||
| Geert Hendrickx | ghen@NetBSD.org | ||
| René Hexel | rh@NetBSD.org | ||
| Iain Hibbert | plunky@NetBSD.org | ||
| Kouichirou Hiratsuka | hira@NetBSD.org | ||
| Michael L. Hitch | mhitch@NetBSD.org | ||
| Jachym Holecek | freza@NetBSD.org | ||
| Christian E. Hopps | chopps@NetBSD.org | ||
| Ken Hornstein | kenh@NetBSD.org | ||
| Marc Horowitz | marc@NetBSD.org | ||
| Eduardo Horvath | eeh@NetBSD.org | ||
| Nick Hudson | skrll@NetBSD.org | ||
| Shell Hung | shell@NetBSD.org | ||
| Martin Husemann | martin@NetBSD.org | ||
| Dean Huxley | dean@NetBSD.org | ||
| Love Hörnquist Åstrand | lha@NetBSD.org | ||
| Bernardo Innocenti | bernie@NetBSD.org | ||
| Tetsuya Isaki | isaki@NetBSD.org | ||
| ITOH Yasufumi | itohy@NetBSD.org | ||
| IWAMOTO Toshihiro | toshii@NetBSD.org | ||
| Matthew Jacob | mjacob@NetBSD.org | ||
| Soren Jacobsen | snj@NetBSD.org | ||
| Lonhyn T. Jasinskyj | lonhyn@NetBSD.org | ||
| Darrin Jewell | dbj@NetBSD.org | ||
| Chris Jones | cjones@NetBSD.org | ||
| Søren Jørvang | soren@NetBSD.org | ||
| Takahiro Kambe | taca@NetBSD.org | ||
| Antti Kantee | pooka@NetBSD.org | ||
| Masanori Kanaoka | kanaoka@NetBSD.org | ||
| Frank Kardel | kardel@NetBSD.org | ||
| Mattias Karlsson | keihan@NetBSD.org | ||
| KAWAMOTO Yosihisa | kawamoto@NetBSD.org | ||
| Mario Kemper | magick@NetBSD.org | ||
| Min Sik Kim | minskim@NetBSD.org | ||
| Thomas Klausner | wiz@NetBSD.org | ||
| Klaus Klein | kleink@NetBSD.org | ||
| John Klos | jklos@NetBSD.org | ||
| Wayne Knowles | wdk@NetBSD.org | ||
| Takayoshi Kochi | kochi@NetBSD.org | ||
| John Kohl | jtk@NetBSD.org | ||
| Daniel de Kok | daniel@NetBSD.org | ||
| Paul Kranenburg | pk@NetBSD.org | ||
| Martti Kuparinen | martti@NetBSD.org | ||
| Kentaro A. Kurahone | kurahone@NetBSD.org | ||
| Kevin Lahey | kml@NetBSD.org | ||
| Johnny C. Lam | jlam@NetBSD.org | ||
| Martin J. Laubach | mjl@NetBSD.org | ||
| Greg Lehey | grog@NetBSD.org | ||
| Ted Lemon | mellon@NetBSD.org | ||
| Christian Limpach | cl@NetBSD.org | ||
| Frank van der Linden | fvdl@NetBSD.org | ||
| Joel Lindholm | joel@NetBSD.org | ||
| Mike Long | mikel@NetBSD.org | ||
| Michael Lorenz | macallan@NetBSD.org | ||
| Warner Losh | imp@NetBSD.org | ||
| Tomasz Luchowski | zuntum@NetBSD.org | ||
| Federico Lupi | federico@NetBSD.org | ||
| Brett Lymn | blymn@NetBSD.org | ||
| Paul Mackerras | paulus@NetBSD.org | ||
| Anders Magnusson | ragge@NetBSD.org | ||
| MAEKAWA Masahide | gehenna@NetBSD.org | ||
| David Maxwell | david@NetBSD.org | ||
| Dan McMahill | dmcmahill@NetBSD.org | ||
| Gregory McGarry | gmcgarry@NetBSD.org | ||
| Jared D. McNeill | jmcneill@NetBSD.org | ||
| Neil J. McRae | neil@NetBSD.org | ||
| Perry Metzger | perry@NetBSD.org | ||
| Simas Mockevicius | symka@NetBSD.org | ||
| Juan Romero Pardines | xtraeme@NetBSD.org | ||
| Julio M. Merino Vidal | jmmv@NetBSD.org | ||
| Minoura Makoto | minoura@NetBSD.org | ||
| Luke Mewburn | lukem@NetBSD.org | ||
| der Mouse | mouse@NetBSD.org | ||
| Joseph Myers | jsm@NetBSD.org | ||
| Ken Nakata | kenn@NetBSD.org | ||
| Takeshi Nakayama | nakayama@NetBSD.org | ||
| Phil Nelson | phil@NetBSD.org | ||
| John Nemeth | jnemeth@NetBSD.org | ||
| Bob Nestor | rnestor@NetBSD.org | ||
| NISHIMURA Takeshi | nsmrtks@NetBSD.org | ||
| Tohru Nishimura | nisimura@NetBSD.org | ||
| NONAKA Kimihiro | nonaka@NetBSD.org | ||
| Takehiko NOZAKI | tnozaki@NetBSD.org | ||
| Jesse Off | joff@NetBSD.org | ||
| Tatoku Ogaito | tacha@NetBSD.org | ||
| OKANO Takayoshi | kano@NetBSD.org | ||
| Masaru Oki | oki@NetBSD.org | ||
| Atsushi Onoe | onoe@NetBSD.org | ||
| Greg Oster | oster@NetBSD.org | ||
| Jonathan Perkin | sketch@NetBSD.org | ||
| Herb Peyerl | hpeyerl@NetBSD.org | ||
| Matthias Pfaller | matthias@NetBSD.org | ||
| Chris Pinnock | cjep@NetBSD.org | ||
| Adrian Portelli | adrianp@NetBSD.org | ||
| Rui Paulo | rpaulo@NetBSD.org | ||
| Peter Postma | peter@NetBSD.org | ||
| Dante Profeta | dante@NetBSD.org | ||
| Chris Provenzano | proven@NetBSD.org | ||
| Niels Provos | provos@NetBSD.org | ||
| Michael Rauch | mrauch@NetBSD.org | ||
| Marc Recht | recht@NetBSD.org | ||
| Darren Reed | darrenr@NetBSD.org | ||
| Jeremy C. Reed | reed@NetBSD.org | ||
| Antoine Reilles | tonio@NetBSD.org | ||
| Tyler R. Retzlaff | rtr@NetBSD.org | ||
| Scott Reynolds | scottr@NetBSD.org | ||
| Michael Richardson | mcr@NetBSD.org | ||
| Tim Rightnour | garbled@NetBSD.org | ||
| Alan Ritter | rittera@NetBSD.org | ||
| Jeff Rizzo | riz@NetBSD.org | ||
| Gordon Ross | gwr@NetBSD.org | ||
| Steve Rumble | rumble@NetBSD.org | ||
| Ilpo Ruotsalainen | lonewolf@NetBSD.org | ||
| Heiko W. Rupp | hwr@NetBSD.org | ||
| David Sainty | dsainty@NetBSD.org | ||
| SAITOH Masanobu | msaitoh@NetBSD.org | ||
| Kazuki Sakamoto | sakamoto@NetBSD.org | ||
| Curt Sampson | cjs@NetBSD.org | ||
| Wilfredo Sanchez | wsanchez@NetBSD.org | ||
| Ty Sarna | tsarna@NetBSD.org | ||
| SATO Kazumi | sato@NetBSD.org | ||
| Jan Schaumann | jschauma@NetBSD.org | ||
| Matthias Scheler | tron@NetBSD.org | ||
| Karl Schilke (rAT) | rat@NetBSD.org | ||
| Amitai Schlair | schmonz@NetBSD.org | ||
| Konrad Schroder | perseant@NetBSD.org | ||
| Georg Schwarz | schwarz@NetBSD.org | ||
| Lubomir Sedlacik | salo@NetBSD.org | ||
| Christopher SEKIYA | sekiya@NetBSD.org | ||
| Reed Shadgett | dent@NetBSD.org | ||
| John Shannon | shannonjr@NetBSD.org | ||
| Tim Shepard | shep@NetBSD.org | ||
| Takeshi Shibagaki | shiba@NetBSD.org | ||
| Naoto Shimazaki | igy@NetBSD.org | ||
| Takao Shinohara | shin@NetBSD.org | ||
| Takuya SHIOZAKI | tshiozak@NetBSD.org | ||
| Chuck Silvers | chs@NetBSD.org | ||
| Thor Lancelot Simon | tls@NetBSD.org | ||
| Jeff Smith | jeffs@NetBSD.org | ||
| Noriyuki Soda | soda@NetBSD.org | ||
| Wolfgang Solfrank | ws@NetBSD.org | ||
| SOMEYA Yoshihiko | someya@NetBSD.org | ||
| Bill Sommerfeld | sommerfeld@NetBSD.org | ||
| Jörg Sonnenberger | joerg@NetBSD.org | ||
| Ignatios Souvatzis | is@NetBSD.org | ||
| Bill Squier | groo@NetBSD.org | ||
| Jonathan Stone | jonathan@NetBSD.org | ||
| Bill Studenmund | wrstuden@NetBSD.org | ||
| Kevin Sullivan | sullivan@NetBSD.org | ||
| SUNAGAWA Keiki | kei@NetBSD.org | ||
| Kimmo Suominen | kim@NetBSD.org | ||
| Shin Takemura | takemura@NetBSD.org | ||
| TAMURA Kent | kent@NetBSD.org | ||
| Shin'ichiro TAYA | taya@NetBSD.org | ||
| Ian Lance Taylor | ian@NetBSD.org | ||
| Matt Thomas | matt@NetBSD.org | ||
| Jason Thorpe | thorpej@NetBSD.org | ||
| Christoph Toshok | toshok@NetBSD.org | ||
| Greg Troxel | gdt@NetBSD.org | ||
| Tsubai Masanari | tsubai@NetBSD.org | ||
| Izumi Tsutsui | tsutsui@NetBSD.org | ||
| UCHIYAMA Yasushi | uch@NetBSD.org | ||
| Masao Uebayashi | uebayasi@NetBSD.org | ||
| Shuichiro URATA | ur@NetBSD.org | ||
| Valeriy E. Ushakov | uwe@NetBSD.org | ||
| Todd Vierling | tv@NetBSD.org | ||
| Aymeric Vincent | aymeric@NetBSD.org | ||
| Paul Vixie | vixie@NetBSD.org | ||
| Mike M. Volokhov | mishka@NetBSD.org | ||
| Krister Walfridsson | kristerw@NetBSD.org | ||
| Lex Wennmacher | wennmach@NetBSD.org | ||
| Leo Weppelman | leo@NetBSD.org | ||
| Assar Westerlund | assar@NetBSD.org | ||
| Todd Whitesel | toddpw@NetBSD.org | ||
| Nathan Williams | nathanw@NetBSD.org | ||
| Rob Windsor | windsor@NetBSD.org | ||
| Dan Winship | danw@NetBSD.org | ||
| Jim Wise | jwise@NetBSD.org | ||
| Michael Wolfson | mbw@NetBSD.org | ||
| Steve Woodford | scw@NetBSD.org | ||
| Colin Wood | ender@NetBSD.org | ||
| YAMAMOTO Takashi | yamt@NetBSD.org | ||
| Yuji Yamano | yyamano@NetBSD.org | ||
| Reinoud Zandijk | reinoud@NetBSD.org | ||
| S.P.Zeidler | spz@NetBSD.org | ||
| Maria Zevenhoven | maria7@NetBSD.org | ||
| Christos Zoulas | christos@NetBSD.org | ||
|
| |||
| Other contributors: | |||
| Dave Burgess | burgess@cynjut.infonet.net | ||
| Brian R. Gaeke | brg@dgate.org | ||
| Brad Grantham | grantham@tenon.com | ||
| Lawrence Kesteloot | kesteloo@cs.unc.edu | ||
| Waldi Ravens | waldi@moacs.indiv.nl.net |
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.