About this Document............................................2
What is NetBSD?................................................2
Changes Between The NetBSD 3.0 and 4.0 Releases................3
Networking..................................................3
File systems................................................4
Drivers.....................................................4
Platforms...................................................6
Kernel subsystems...........................................7
Security....................................................8
Userland....................................................8
Components removed from NetBSD.............................10
The Future of NetBSD..........................................10
Sources of NetBSD.............................................11
NetBSD 4.0 Release Contents...................................11
NetBSD/acorn32 subdirectory structure......................12
Binary distribution sets...................................13
NetBSD/acorn32 System Requirements and Supported Devices......14
Supported devices..........................................14
Unsupported devices........................................16
Getting the NetBSD System on to Useful Media..................16
Preparing your System for NetBSD installation.................18
Software requirements......................................18
Preliminary steps..........................................19
Preparing your hard disk...................................19
Sharing your device........................................20
Using a whole device for NetBSD............................22
Running bb_riscbsd.........................................22
Booting....................................................23
Configuring the !BtNetBSD bootloader before installation...23
Booting the installation kernel............................23
Configuring !BtNetBSD after installation...................23
Installing the NetBSD System..................................23
Running the sysinst installation program...................23
Introduction............................................23
General.................................................24
Quick install...........................................24
Booting NetBSD..........................................25
Network configuration...................................25
Installation drive selection and parameters.............25
Partitioning the disk...................................26
Preparing your hard disk................................26
Getting the distribution sets...........................26
Installation using ftp..................................27
Installation using NFS..................................27
Installation from CD-ROM................................27
Installation from an unmounted file system..............27
Installation from a local directory.....................28
Extracting the distribution sets........................28
Finalizing your installation............................28
Post installation steps.......................................28
Upgrading a previously-installed NetBSD System................31
Compatibility Issues With Previous NetBSD Releases............31
Issues affecting an upgrade from NetBSD 2.1 and older......32
Issues affecting an upgrade from NetBSD 3.x releases.......32
Issues with GDB 6.5...........................................33
Using online NetBSD documentation.............................33
Administrivia.................................................34
Thanks go to..................................................34
We are........................................................35
Dedication....................................................41
Legal Mumbo-Jumbo.............................................41
The End.......................................................47
This document describes the installation procedure for
NetBSD
4.0 on the
acorn32
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 NetBSD 4.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. Please see the NetBSD web site at http://www.NetBSD.org/ for information on them.)
NetBSD is a completely integrated system. In addition to its highly portable, high performance kernel, NetBSD features a complete set of user utilities, compilers for several languages, the X Window System, firewall software and numerous other tools, all accompanied by full source code.
NetBSD is a creation of the members of the Internet community. Without the unique cooperation and coordination the net makes possible, it's likely that NetBSD wouldn't exist.
The NetBSD 4.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 more than a year of development that went into the NetBSD 4.0 release. The complete list of changes can be found in the CHANGES: ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-4.0/CHANGES and CHANGES-4.0: ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-4.0/CHANGES-4.0 files in the top level directory of the NetBSD 4.0 release tree. Some highlights include:
agr(4):
new pseudo-device driver for link level aggregation.
gre(4)
tunnels and the
tun(4)
device.
ndiscvt(8).
options(4)
and
in_getifa(9).
wpa_supplicant(8)
and
wpa_cli(8).
Utilities to connect and handle aspects of 802.11 WPA networks.
hostapd(8).
An authenticator for IEEE 802.11 networks.
carp(4):
imported Common Address Redundancy Protocol to allow multiple hosts to share a set of IP addresses for high availability / redundancy, from OpenBSD.
etherip(4):
new EtherIP tunneling device. It's able to tunnel Ethernet traffic over IPv4 and IPv6 using the EtherIP protocol specified in RFC 3378.
ftpd(8)
can now run in standalone mode, instead of from
inetd(8).
tftp(1)
now has support for multicast TFTP operation in open-loop mode, server is in progress.
tcp(4):
added support for RFC 3465 Appropriate Byte Counting (ABC) and Explicit Congestion Notification as defined in RFC 3168.
scan_ffs(8),
scan_lfs(8):
utilities to find FFSv1/v2 and LFS partitions to recover lost disklabels on disks and image files.
mount_tmpfs(8).
mount_udf(8).
Read-only for now.
vnd(4):
the vnode disk driver can be used on filesystems such as smbfs and tmpfs.
newfs_sysvbfs(8)
and
mount_sysvbfs(8).
auich(4):
added support to handle the AC'97 modem as audio device, enabled with the kernel option
``AUICH_ATTACH_MODEM''
azalia(4):
added support for S/PDIF.
amdpm(4):
added support for the i2c bus on the AMD-8111 used on many Opteron motherboards and for the Analog Devices ADT7464 hardware monitor chip.
adt7467c(4):
new driver for Analog Devices ADT7467 and ADM1030 hardware monitor chips.
ipmi(4):
new driver for motherboards implementing the Intelligent Platform Management Interface 1.5 or 2.0, from OpenBSD.
it(4):
new driver for iTE 8705F/8712F and SiS 950 hardware monitors.
lm(4)
driver was rewritten and support for more chips was added, for example for Winbond W83627HF, W83627THF, W83627DHG and Asus AS99127F.
owtemp(4):
new driver for the 1-Wire temperature sensors.
tmp121temp(4):
new driver for the Texas Instruments TMP121 temperature sensor.
ug(4):
new driver for Abit uGuru hardware monitor found on newer Abit motherboards.
geodewdog(4):
new AMD Geode SC1100 Watchdog Timer driver.
gscpcib(4):
new AMD Geode SC1100 PCI-ISA bridge that provides support for the GPIO interface.
ath(4):
updated HALs with support for WiSOC (AR531x) and 32bit SPARC.
bge(4):
added support for the following chips: BCM5753, BCM5753M, BCM5715, BCM5754, BCM5755 and BCM5787. Numerous improvements and bugfixes were made too.
kse(4):
new driver for Micrel KSZ8842/8841 PCI network cards.
msk(4):
new driver for Marvell Yukon 2 GigE PCI network cards, from OpenBSD.
nfe(4):
new driver for NVIDIA nForce Ethernet network cards, from OpenBSD.
ral(4):
new 802.11 driver for PCI/Cardbus Ralink RT2500, RT2501, RT2600, RT2661 and RT2500 USB chipsets, from OpenBSD.
rum(4):
new 802.11 driver for USB Ralink RT2501 and RT2601 chipsets, from OpenBSD.
sip(4):
now works on sparc64.
tlp(4):
added support for ASIX AX88140A and AX88141.
vr(4):
added support for the VIA Rhine III.
wm(4):
added support for i8003, ICH8, ICH9 and others. Support for IPv6 Rx TCP/UDP Checksum Offloading and more.
wpi(4):
new driver for Intel PRO/Wireless 3945ABG PCI 802.11 network cards, from OpenBSD.
glxsb(4):
new driver for the AMD Geode LX AES Security Block that provides random numbers and AES acceleration, from OpenBSD.
options(4)
for more information.
options(4)
for more information.
ahcisata(4):
new driver for AHCI 1.0 and 1.1 compliant SATA controllers.
ataraid(4):
added support to handle Adaptec HostRAID and VIA V-Tech software RAID.
ciss(4):
new driver for HP/Compaq 5th+ generation Smart ARRAY controllers, from OpenBSD.
fdc(4):
added support for SBus based sparc64 machines and fixed formatting on sparc.
gcscide(4):
new driver for the AMD Geode CS5535 Companion Device IDE controller.
jmide(4):
new driver for JMicron Technology JMB36x PCIe to SATA II/PATA controllers.
mfi(4):
new driver for LSI Logic and Dell MegaRAID SAS controllers, from OpenBSD.
mpt(4):
added support for newer SAS and similar devices.
njata(4):
new driver for Workbit NinjaATA-32 CardBus IDE controller.
pdcsata(4):
added support for the Promise PDC20775, PDC20771, PDC40518, PDC40718 and some bugfixes.
piixide(4):
added support for some ICH8/ICH8-M/ICH9 IDE and SATA controllers.
svwsata(4):
new driver for Serverworks K2 SATA controllers, from OpenBSD.
viaide(4)
added support for the VIA VT8237A SATA controller and AMD CS5536 Companion Device IDE Controller.
ucycom(4):
new driver for Cypress microcontroller based serial devices.
uipaq(4):
new driver for the iPAQ devices.
uslsa(4):
new driver for Silicon Labs CP210x series serial adapters.
utoppy(4):
new driver for the Topfield TF5000PVR range of digital video recorders.
vesafb(4):
added new framebuffer driver that supports VESA BIOS (VBE) 2.0 extensions and up.
teliosio(4)
driver for the Sharp Telios LCD screen and Battery unit.
midi(4)
framework got a complete overhaul for better support of Active Sensing and improved handling of tempo and timebase changes.
ubt(4)
for USB controllers, and
bt3c(4)
for the 3Com Bluetooth PC-Card.
See
bluetooth(4),
bthset(1)
and
btpin(1).
bio(4)
framework from OpenBSD, to query/control block hardware RAID device controllers. Currently supporting the
mfi(4)
driver.
dkctl(8)
can be used to switch buffer queuing strategies on the fly on
wd(4)
disks, see also
bufq(9).
fileassoc(9)
is used by Veriexec, it adds in-kernel and file-system independent file meta-data association interface.
firmload(9):
an API for loading firmware images used by various hardware devices.
gpio(4):
imported General Purpose I/O framework from OpenBSD.
onewire(4):
imported Dallas Semiconductor 1-wire bus framework from OpenBSD.
proplib(3)
protocol was added for sending property lists to/from the kernel using ioctls.
spi(4):
new SPI (Serial Peripherial Interface) framework.
timecounter(9)
adds a new time-keeping infrastructure along with NTP API 4 nanokernel implementation. Almost all platforms were changed to support this API.
wscons(4)
console driver supports splash screens, scrolling, progress bar for kernel and boot messages.
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.
fast_ipsec(4)
for more information.
mprotect(2)
got restrictions to enforce W^X policies, from PaX. See
options(4),
sysctl(3),
and
paxctl(1).
security(8).
kauth(9)
was added, replacing the traditional BSD credential management and privileged operation access control with an abstract layer, allowing the implementation of various security models either as part of the NetBSD distribution or as third-party LKMs.
NetBSD's kernel authorization is a hybrid clean-room implementation of a similar interface developed by Apple, extending its capabilities and combining concepts of credential inheritance control.
cdplay(1):
added digital transfer mode support.
cksum(1)
can now verify checksums.
csplit(1):
new utility that splits a file into pieces. From FreeBSD/OpenBSD.
identd(1):
added support for forwarding ident queries and receiving of proxied ident queries.
getent(1):
added support for the ethers database.
gkermit(1):
new program for transferring files using the Kermit protocol.
mail(1):
added support for Mime and multi-character set handling, command line editing and completion.
utoppya(1):
new utility to interface to the
utoppy(4)
driver.
init(8):
added support for running multi-user in a chroot() environment. Allows / file system on e.g.,
cgd(4),
vnd(4)
or
ccd(4)
volumes.
gpt(8):
new GUID partition table maintenance utility, from FreeBSD.
iscsi-target(8);
Initiator (client) code is underway.
lockstat(8):
new command to display a summary of kernel locking events recorded over the lifetime of a called program.
ofctl(8):
new command to display the OpenPROM or OpenFirmware device tree for the macppc, shark and sparc64.
btconfig(8)
for controller configuration.
btdevctl(8)
to manage pseudo devices relating to remote services.
bthcid(8)
and
btpin(1)
for authenticating radio connections.
sdpd(8)
for providing service discovery to remote devices.
sdpquery(1)
for querying services on remote devices.
rfcomm_sppd(1)
to access remote services over RFCOMM via stdio or pty.
bthset(1)
for making connections to Bluetooth headsets.
Besides this list, there have also been innumerable bug fixes and other miscellaneous enhancements of course.
In this release of NetBSD, some software components known from previous releases were removed from the system. In some cases those were components that are not useful anymore or their utility does not justify maintenance overhead. Other components were not working properly and there was lack of interest in fixing them.
raid(4),
raidctl(8),
and the
NetBSD Guide:
http://www.NetBSD.org/docs/guide/en/chap-rf.html.
sendmail(1)
command line tool. Postfix has been included with NetBSD since NetBSD 1.5 was released in December 2005. Details about Postfix can be found in the
NetBSD Guide:
http://www.NetBSD.org/docs/guide/en/chap-mail.html.
For those who need Sendmail, it is available from pkgsrc in the
mail/sendmail
and
mail/sendmail813
packages.
net/uucp
package. The
cu(1)
command is available as a frontend to
tip(1).
lang/gcc3-f77
package.
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 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 NetBSD 4.0 release is organized as follows:
.../NetBSD-4.0/
CHANGESCHANGES-4.0CHANGES.prevLAST_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 NetBSD 4.0 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(1);
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:
BSDSUMCKSUMMD5SHA512SYSVSUMThe SHA512 digest is the safest checksum, followed by the MD5 digest, and finally the POSIX checksum. The other two checksums are provided only to ensure that the widest possible range of systems can check the integrity of the release files.
acorn32
subdirectory of the distribution:
.../NetBSD-4.0/acorn32/.
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-GENERIC.gznetbsd-NC.gzsets/installation/misc/acorn32/binary/sets
subdirectory
of the
NetBSD
4.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.
/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.
GENERIC
kernel, named
/netbsd.
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.5.0. Binary sets for the X Window System are distributed with NetBSD. The sets are:
The acorn32 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/acorn32 4.0 runs on Acorn systems with ARM6 or later processors, with or without FPU coprocessor. The minimal configuration is said to require 8 MB of RAM and 50 MB of disk space, though we do not know of anyone running with a system quite this minimal today. To install the entire system requires much more disk space (the unpacked binary distribution, without sources, requires at least 65 MB without counting space needed for swap space, etc), and to run X or compile the system, more RAM is recommended. (8 MB of RAM will actually allow you to run X and/or compile, but it won't be speedy. Note that until you have around 16 MB of RAM, getting more RAM is more important than getting a faster CPU.)
Drivers for hardware marked with ``[*]'' are not present in installation kernels.
Support for some devices is limited to particular kernels. eg there is no SA110 support in A7000 kernels.
Drivers are planned for some of the above devices.
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
acorn32/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
acorn32/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.190.13
and the IPv6 address is
2001:4f8:4:7:230:48ff:fe31:43f2
(as of December, 2007).
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 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
kern-GENERIC, base, and etc
distributions on tape (in
order to do the absolute minimum installation to a new disk),
you would do the following:
# cd .../NetBSD-4.0
# cd acorn32/binary
# tar -cf tape_device kern-GENERIC base etc
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.
First and foremost, before beginning the installation process, make sure you have a reliable backup of any data on your hard disk that you wish to keep. Repartitioning your hard disk is an excellent way to destroy important data.
installation/misc/splug.bas
or at David Pilling's W3 site:
http://pilling.users.netlink.co.uk/free.html
RiscPC/A7000(+)/NC's : INSTALL kernel
BtNetBSD.spk
as found in the
installation/misc
directory.
(This should be pre-extracted if you're installing from CD-ROM).
You will have to decide which device you wish to install NetBSD on. You will also have to decide whether you want to split the device between one or more RiscOS Discs and NetBSD or dedicate a whole Device for NetBSD.
In making this decision you should consider the possibility that if NetBSD is incorrectly configured on a shared device then your shared data is at risk.
It is still recommended that if you decide to dedicate a device to NetBSD that you set aside a small RISC OS partition at the beginning of the device. This is a useful place to store the RISC OS side of NetBSD, and will make the use of UnixFS easier to configure. If you do decide to create a minimal RISC OS partition at the beginning of the device, a size of 10-20 MB is recommended (some partitioning software has problems with partitions smaller than this).
The point is that you will have to repartition your device to make room for a separate partition after the RISC OS one for NetBSD. This means backing up your device, re-partitioning it and then copying all the data back afterwards. We recommend that you only copy the needed data back and put off installing the rest until you have NetBSD up and running. This way you will save yourself a lot of work if something goes wrong and you have to start all over again.
Use !HForm for this interface.
This is a program that is delivered with your computer and is located in the
Utilities
directory on your
hard disk.
With this software you only have the possibility of using one partition for RISC OS, so you have to set the rest aside for NetBSD.
Use this procedure to set up your device:
2.1.2 Cumana SCSI-2 card
It is recommended that you use a newer version of !SCSIMgr (newer than v1.55) since this will be easier to use when you want to leave part of the device unused by RISC OS. You should check for the latest version of this software at the following URL: http://www.cumana.demon.co.uk
You need to create one or more RISC OS partitions, and you do it in in the following way:
2.1.3 Alsystems Power-tec SCSI-2 card
You must use the !PowerMgr program to partition the device.
The RISC OS partitions should be called `RiscOs:', and the NetBSD one should be called `Empty:'.
Here is the procedure you should use:
2.1.4 Acorn SCSI card
You can only have one RISC OS partition with this card.
The rest has to be set aside for
NetBSD.
This card does not have a friendly WIMP-based interface on the SCSI
management program, but the command line version is very good.
You should run this in a task window (press
CTRL-F12):
You will get the following prompt:*dirlocation_of_scsidm
*scsidm
scsidm>
Include RISCiX partitions?
Do you really want to section deviceno?
Go to the section on running bb_riscbsd.
2.1.5 Other interfaces
It may not be possible to partition devices on other interface. If you are using a different interface you have 2 options:
As a safety precaution NetBSD/acorn32 looks for a filecore bootblock at the beginning of any device it labels. If it finds one and it looks as though it is in use then NetBSD/acorn32 will not touch it.
Because of this, if you've ever used your device for RiscOS, you will need to invalidate this bootblock.
To do this you need to:
Ensure that this device is now not configured for RiscOS.
You are now ready to boot NetBSD and continue the installation.
When you run this program, you will first be asked whether you are installing to an ADFS drive or a SCSI drive. You can just press `A' or `S' respectively. (The bb_riscbsd program assumes that you are using a non-Acorn SCSI card, so if you are using an Acorn card, then you may have to edit this program and replace `SCSI_DiscOp' with `SCSIFS_DiscOp'.)
Then you will be asked which Disc you want to install NetBSD on. This must be the first Disc on the device. bb_riscbsd will now scrutinize the device and see how it has been laid out.
It will then tell you how much of the device is occupied by RiscOS in cylinders, and you will then be asked for the NetBSD starting cylinder. Normally you should just enter the number given to you since the RISC OS starting cylinder is 0 and therefore the last cylinder in use is one less than the figure given. If no figure is displayed, then your partitioning software failed to fill in the bootblock completely (it doesn't have to do this for you but most do) or you selected the wrong device. If you are convinced that this is the correct device then you must calculate a cylinder offset using the numbers noted down during partitioning (if it is not a whole number always round up, you might waste a little of the device but it'll be safer).
Make a note of this number.
bb_riscbsd will make a backup of the original bootblock, but it can be non-trivial to put it back.
Now that your device is ready for the installation you need to
unpack the bootloader archive,
BtNetBSD.spk,
(If you're installing from CD-ROM then this should be unpacked already) and
copy the directory to your hard disk.
In the archive you'll find the tools
mentioned in this document as well as the bootloader
!BtNetBSD
itself.
!BtNetBSD
application and edit the
fastboot
file.
You can set details like tweaking with the amount of memory in the WimpSlot of the bootloader when this is too much. Remember however that this shouldn't be set too low for it can crash the bootloader.
When you think you've filled in the proper details save the file again and proceed.
Double click on the InstKern icon to start it up.
NetBSD should now start to boot, install NetBSD as per the NetBSD installation notes.
When you finish the installation you can restarted the computer as instructed.
Open the
!BtNetBSD
application again and edit the
fastboot
file to fill in the normal kernel name.
Specify the device
NetBSD
should be looking for its kernel in.
This is the
`Run
Set the kernel as
Save the file and run !BtNetBSD again (see above).
Finally, when you are happy with your
NetBSD
installation, do whatever
is necessary to restore order to the partition you took space away from.
This will most likely involve restoring files, but might involve some
other
``house-work''.
Your hard disk is now prepared to have
NetBSD
installed on it, and you should proceed with the installation instructions.
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.
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
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.
Boot your machine.
The boot loader will start, and will print a countdown and begin booting.
If the boot loader messages do not appear in a reasonable
amount of time, you either have a bad boot floppy or a
hardware problem.
Try writing the install floppy image to
a different disk, and using that.
It will take a while to load the kernel
from the floppy,
probably around a minute or so, then, the kernel boot messages
will be displayed.
This may take a little while also, as
NetBSD
will be probing your system to discover which hardware devices are
installed.
The most important thing to know is that
Note that once the system has finished booting, you need not
leave the floppy in the disk drive.
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
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.
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
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
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
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
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
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.
Alternatively, you will be asked if you wish to have a progress bar.
This is the preferred option as it shows progress without significantly
slowing down the installation process.
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 then set a password for the "root" account, to prevent
the machine coming up without access restrictions.
Congratulations, you have successfully installed
NetBSD
4.0.
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.
If you or the installation software haven't done any configuration of
and with the root file system
(
If your
If you have
Other values that need to be set in
or, if you have
myname.my.dom
in
To enable proper hostname resolution, you will also want to add an
Other files in
After reboot, you can log in as
Unless you have connected an unusual terminal device as the console
you can just press
Use the
If you have installed the X Window System, look at the files in
Don't forget to add
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.
If you are using
The above commands will install the Tenex-csh and Bourne Again shell,
the Perl programming language, Apache web server, KDE desktop
environment and the Firefox web browser
as well as all the packages they depend on.
After extracting, see the
is likely to give you more information on these files.
The upgrade to
NetBSD4.0
is a binary upgrade; it can be quite difficult to update the system
from an earlier version by recompiling from source, primarily due to
interdependencies in the various components.
To do the upgrade, you must have the boot floppy
available.
You must also have at least the
base
and
kern
binary distribution sets available, so that you can upgrade with them,
using one of the upgrade methods described above.
Finally, you must have sufficient disk space available to install the
new binaries.
Since files already installed on the system are overwritten in place,
you only need additional free space for files which weren't previously
installed or to account for growth of the sets between releases.
If you have a few megabytes free on each of your root
(
Since upgrading involves replacing the kernel, the boot blocks on your
NetBSD
partition, and most of the system binaries, it has the
potential to cause data loss.
You are strongly advised to
back up
any important data on the
NetBSD
partition or on
another operating system's partition on your disk
before beginning the upgrade process.
The upgrade procedure using the
sysinst
tool is similar to an installation, but without the hard disk partitioning.
sysinst
will attempt to merge the settings stored in your
After a new kernel has been copied to your hard disk, your
machine is a complete
NetBSD4.0
system.
However, that doesn't mean that you're finished with the upgrade process.
You will probably want to update the set of device
nodes you have in
Finally, you will want to delete old binaries that were part
of the version of
NetBSD
that you upgraded from and have since been removed from the
NetBSD
distribution.
Users upgrading from previous versions of
NetBSD
may wish to bear the
following problems and compatibility issues in mind when upgrading to
NetBSD
4.0 .
N.B. when using
sysinst
for upgrading, it will automatically invoke
It is
very important
that you populate the directory
The following issues can generally be resolved by running
postinstall
with the
etc
set :
Issues fixed by
postinstall:
The following issues need to be resolved manually:
The following issues can generally be resolved by running
postinstall
with the
etc
set :
Issues fixed by
postinstall:
The following issues need to be resolved manually:
Note that if you have a customized
Sendmail setup, you need to set up Postfix in an equivalent way; there
is no tool for automatic conversion of Sendmail configuration to a
Postfix one.
Postfix will be started up automatically when the system boots.
You may see messages like "$sendmail is not set properly" at boot.
You can suppress them by removing
Both issues have been addressed on the wrstuden-fixsa branch, but did not
make it into the
NetBSD
release. Both will be fixed in the next patch release.
Documentation is available if you first install the manual
distribution set.
Traditionally, the
``man pages''
(documentation) are denoted by
`
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
to read the documentation for
instead.
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
Use of
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.
for their ongoing work on
BSD
systems, support, and encouragement.
(in alphabetical order)
NetBSD
4.0 is dedicated to the memory of Jun-Ichiro "itojun" Hagino,
who died in October 2007.
Itojun was a member of the KAME project,
which provided IPv6 and IPsec support; he was also a member
of the
NetBSD
core team (the technical management for the project), and
one of the Security Officers.
Due to Itojun's efforts,
NetBSD
was the
first open source operating system with a production ready IPv6
networking stack, which was included in the base system before many
people knew what IPv6 was.
We are grateful to have known and worked
with Itojun, and we know that he will be missed.
This release is
therefore dedicated, with thanks, to his memory.
All product names mentioned herein are trademarks or registered
trademarks of their respective owners.
The following notices are required to satisfy the license terms of
the software that we have mentioned in this document:
NetBSD is a registered trademark of The NetBSD Foundation, Inc.
In the following statement, the phrase ``this text'' refers to portions
of the system documentation.
Portions of this text are reprinted and reproduced in electronic form in
NetBSD, from IEEE Std 1003.1, 2004 Edition, Standard for
Information Technology -- Portable Operating System Interface (POSIX),
The Open Group Base Specifications Issue 6, Copyright (C) 2001-2004 by the
Institute of Electrical and Electronics Engineers, Inc and The Open Group.
In the event of any discrepancy between these versions and the original
IEEE and The Open Group Standard, the original IEEE and The Open Group
Standard is the referee document.
The original Standard can be obtained online at
http://www.opengroup.org/unix/online.html.
This notice shall appear on any product containing this material
UnixFS:$.netbsd.
Installing the NetBSD System
Running the sysinst installation program
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.
.***********************************************.
* NetBSD-4.0 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/.
wd0
is
NetBSD's
name for your first IDE disk,
wd1
the second, etc.
sd0
is your first SCSI disk,
sd1
the second, etc.
sd0
or
sd1.
a/)
bcd-he
is the partition mounted on
/usr,
but this is historical practice and not a fixed value.
yes
at the prompt.
RETURN
in answer to these questions, and DNS will not be used.
RETURN
in answer to these questions, and DNS will not be used.
cd0),
and the directory name on the CD-ROM where the distribution files are.
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.
Post installation steps
/etc/rc.conf
/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.
/)
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).
/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
/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.
/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"
/etc/hosts:
ifconfig_de0="inet myname.my.dom netmask 255.255.255.0"
/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.
/etc
that may require modification or setting up include
/etc/mailer.conf,
/etc/nsswitch.conf,
and
/etc/wscons.conf.
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.
RETURN
when it prompts for
Terminal type? [...].
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.
/usr/X11R6/lib/X11/doc
for information.
/usr/X11R6/bin
to your path in your shell's dot file so that you have access to the X binaries.
4.0/acorn32/All
subdir.
You can install them with the following commands under
sh(1):
# PKG_PATH=ftp://ftp.NetBSD.org/pub/NetBSD/packages/4.0/acorn32/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 firefox
...
csh(1)
then replace the first two lines with the following:
# setenv PKG_PATH ftp://ftp.NetBSD.org/pub/NetBSD/packages/4.0/acorn32/All
...
/usr/pkgsrc
(though other locations work fine), with the commands:
# mkdir /usr/pkgsrc
# cd /usr/pkgsrc
# tar -zxpf pkgsrc.tar.gz
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/postfix/main.cf
file will almost definitely need to be adjusted.
If you prefer a different MTA, then install it using the
NetBSD
package system or by hand and 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
Upgrading a previously-installed NetBSD System
/)
and
/usr
partitions, you should have enough space.
/etc
directory with the new version of
NetBSD.
Getting the binary
sets is done in the same manner as the installation procedure;
refer to the installation part of the document
for how to do this.
Also, some sanity checks are done, i.e.
file systems are checked before unpacking the sets.
/dev.
If you've changed the contents of
/dev
by hand, you will need to be careful about this, but if
not, you can just cd into
/dev,
and run the command:
# sh MAKEDEV all
Compatibility Issues With Previous NetBSD Releases
and thus all issues that are fixed by
postinstall
by default (see below) will be handled.
postinstall fix
Issues affecting an upgrade from NetBSD 2.1 and older releases.
See the section below on upgrading from NetBSD 3.x as well.
/etc/pam.d
with appropriate configuration files for 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/docs/guide/en/chap-pam.html
for documentation about PAM.
postinstall -s /path/to/etc.tgz check
postinstall -s /path/to/etc.tgz fix
/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/*
Issues affecting an upgrade from NetBSD 3.x releases.
postinstall -s /path/to/etc.tgz check
postinstall -s /path/to/etc.tgz fix
/etc
need upgrading.
These include:
/etc/defaults/*
/etc/mtree/*
/etc/daily
/etc/weekly
/etc/monthly
/etc/security
/etc/rc.subr
/etc/rc
/etc/rc.shutdown
/etc/rc.d/*
/etc/envsys.conf
will update your
postinstall -s /path/to/etc.tgz fix mailerconf
/etc/mailer.conf
file to use Postfix as the MTA. When using
sysinst
to upgrade the system, it will ask if you want this to be done.
/etc/rc.d/sendmail
and
/etc/rc.d/smmsp.
Those files and other parts of sendmail configuration like files under
/usr/share/sendmail
are not removed by default
while upgrading for those who want to continue using sendmail from
outside the base system.
If you want to delete them,
postinstall
can be used:
postinstall -s /path/to/etc.tgz fix sendmail
Issues with GDB 6.5
Some architectures (arm, i386, powerpc and sparc64) have switched to a newer
gdb version (6.5) in this release.
Unfortunately support for debugging programs using the SA (scheduler
activation) based thread library, is incomplete in this gdb version.
Furthermore kernel crashdumps can not be debugged due to a missing
identification in the kernel binaries.
Using online NetBSD documentation
name(section)'.
Some examples of this are
intro(1),
man(1),
apropros(1),
passwd(1),
and
passwd(5).
# man passwd
passwd(1).
To view the documentation for
passwd(5),
enter
# man 5 passwd
# apropos subject-word
Administrivia
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.
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.
Thanks go to
Keith Bostic
Ralph Campbell
Mike Karels
Marshall Kirk McKusick
We are...
The NetBSD core group:
Alistair Crooks agc@NetBSD.org
Quentin Garnier cube@NetBSD.org
YAMAMOTO Takashi yamt@NetBSD.org
Matt Thomas matt@NetBSD.org
Christos Zoulas christos@NetBSD.org
The portmasters (and their ports):
Anders Magnusson ragge vax
Andrew Doran ad amd64
Andrew Doran ad i386
Andrey Petrov petrov sparc64
Ben Harris bjh21 acorn26
Cherry G. Mathew cherry ia64
Chris Gilbert chris cats
Darrin Jewell dbj next68k
Erik Berls cyber cobalt
Gavan Fantom gavan iyonix
IWAMOTO Toshihiro toshii hpcarm
Ichiro FUKUHARA ichiro hpcarm
Ignatios Souvatzis is amiga
Izumi Tsutsui tsutsui ews4800mips
Izumi Tsutsui tsutsui hp300
Izumi Tsutsui tsutsui news68k
Jaime A Fournier ober bebox
Jaime A Fournier ober zaurus
Jason Thorpe thorpej algor
Jason Thorpe thorpej evbarm
Jason Thorpe thorpej shark
Jonathan Stone jonathan pmax
Julian Coleman jdc atari
Manuel Bouyer bouyer xen
Marcus Comstedt marcus dreamcast
Martin Husemann martin sparc64
Matt Fredette fredette sun2
Matt Thomas matt alpha
Matt Thomas matt netwinder
Matthias Drochner drochner cesfic
Michael Lorenz macallan macppc
NISHIMURA Takeshi nsmrtks x68k
Nathan Williams nathanw sun3
Nick Hudson skrll hp700
Noriyuki Soda soda arc
Paul Kranenburg pk sparc
Phil Nelson phil pc532
Reinoud Zandijk reinoud acorn32
Ross Harvey ross alpha
Søren Jørvang soren sgimips
Scott Reynolds scottr mac68k
Shin Takemura takemura hpcmips
Simon Burge simonb evbmips
Simon Burge simonb pmax
Simon Burge simonb sbmips
Steve Woodford scw evbppc
Steve Woodford scw mvme68k
Steve Woodford scw mvmeppc
Takayoshi Kochi kochi ia64
Tim Rightnour garbled prep
Tohru Nishimura nisimura luna68k
Tohru Nishimura nisimura sandpoint
Wayne Knowles wdk mipsco
Wolfgang Solfrank ws ofppc
The NetBSD 4.0 Release Engineering team:
Grant Beattie grant@NetBSD.org
Manuel Bouyer bouyer@NetBSD.org
David Brownlee abs@NetBSD.org
Pavel Cahyna pavel@NetBSD.org
James Chacon jmc@NetBSD.org
Julian Coleman jdc@NetBSD.org
Håvard Eidnes he@NetBSD.org
Liam J. Foy liamjfoy@NetBSD.org
John Heasley heas@NetBSD.org
Geert Hendrickx ghen@NetBSD.org
Soren Jacobsen snj@NetBSD.org
Daniel de Kok daniel@NetBSD.org
Phil Nelson phil@NetBSD.org
Jeff Rizzo riz@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
Stephen Borrill sborrill@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
Pavel Cahyna pavel@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
Arnaud Degroote degroote@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
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
Hauke Fath hauke@NetBSD.org
Hubert Feyrer hubertf@NetBSD.org
Jason R. Fink jrf@NetBSD.org
Matt J. Fleming mjf@NetBSD.org
Marty Fouts marty@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
Michael Graff explorer@NetBSD.org
Brian C. Grayson bgrayson@NetBSD.org
Matthew Green mrg@NetBSD.org
Andreas Gustafsson gson@NetBSD.org
Ulrich Habel rhaen@NetBSD.org
Jun-ichiro itojun Hagino itojun@NetBSD.org
Adam Hamsik haad@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
Nicolas Joly njoly@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
Lubomir Kundrak lkundrak@NetBSD.org
Martti Kuparinen martti@NetBSD.org
Kentaro A. Kurahone kurahone@NetBSD.org
Kevin Lahey kml@NetBSD.org
David Laight dsl@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
Tobias Nygren tnn@NetBSD.org
OBATA Akio obache@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
Mindaugas Rasiukevicius rmind@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
Daniel Sieger dsieger@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
T K Spindler dogcow@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
Frank Wille phx@NetBSD.org
Nathan Williams nathanw@NetBSD.org
Rob Windsor windsor@NetBSD.org
Dan Winship danw@NetBSD.org
Arnaud Lacombe alc@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
Dedication
Legal Mumbo-Jumbo
The End