INSTALL(8) NetBSD System Manager's Manual INSTALL(8)
NNAAMMEE
IINNSSTTAALLLL - Installation procedure for NetBSD/acorn32.
CCOONNTTEENNTTSS
About this Document............................................1
What is NetBSD?................................................2
Upgrade path to NetBSD 1.5.1...................................2
Major Changes Between 1.5 and 1.5.1............................2
Changes Between The NetBSD 1.4 and 1.5 Releases................4
Kernel......................................................4
Networking..................................................4
File system.................................................5
Security....................................................5
System administration and user tools........................5
Miscellaneous...............................................6
The Future of NetBSD...........................................6
Sources of NetBSD..............................................7
NetBSD 1.5ZC Release Contents..................................7
NetBSD/acorn32 subdirectory structure.......................9
Binary distribution sets....................................9
NetBSD/acorn32 System Requirements and Supported Devices......10
Supported devices..........................................10
Unsupported devices........................................11
Getting the NetBSD System on to Useful Media..................12
Preparing your System for NetBSD installation.................14
Installing the NetBSD System..................................14
To install from floppy.....................................16
To install from tape.......................................17
To install via FTP or NFS..................................18
To install from CD-ROM.....................................19
Completing your installation...............................19
Post installation steps.......................................19
Upgrading a previously-installed NetBSD System................22
Compatibility Issues With Previous NetBSD Releases............22
General issues.............................................23
Issues affecting an upgrade from NetBSD 1.4 or prior.......23
Using online NetBSD documentation.............................23
Administrivia.................................................24
Thanks go to..................................................24
We are........................................................27
Legal Mumbo-Jumbo.............................................30
The End.......................................................32
DDEESSCCRRIIPPTTIIOONN
AAbboouutt tthhiiss DDooccuummeenntt
This document describes the installation procedure for NetBSD 1.5ZC on
the _a_c_o_r_n_3_2 platform. It is available in four different formats titled
_I_N_S_T_A_L_L_._e_x_t, where _._e_x_t is one of _._p_s, _._h_t_m_l, _._m_o_r_e, or _._t_x_t:
_._p_s PostScript.
_._h_t_m_l Standard Internet HTML.
_._m_o_r_e The enhanced text format used on UNIX-like systems by the
more(1) and less(1) pager utility programs. This is the
format in which the on-line _m_a_n pages are generally pre-
sented.
_._t_x_t Plain old ASCII.
You are reading the _m_o_r_e version.
WWhhaatt iiss NNeettBBSSDD??
The NetBSD Operating System is a fully functional Open Source UNIX-like
operating system derived from the University of California, Berkeley Net-
working Release 2 (Net/2), 4.4BSD-Lite, and 4.4BSD-Lite2 sources. NetBSD
runs on thirty-one different system architectures featuring twelve dis-
tinct families of CPUs, and is being ported to more. The NetBSD 1.5ZC re-
lease contains complete binary releases for fifteen different machine
types. (The sixteen remaining are not fully supported at this time and
are thus not part of the binary distribution. For information on them,
please see the NetBSD web site at hhttttpp::////wwwwww..nneettbbssdd..oorrgg//.)
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.
UUppggrraaddee ppaatthh ttoo NNeettBBSSDD 11..55..11
If you are not installing your system ``from scratch'' but instead are
going to upgrade an existing system already running NetBSD you need to
know which versions you can upgrade with NetBSD 1.5.1.
NetBSD 1.5.1 is an upgrade of NetBSD 1.5 and earlier major and patch
releases of NetBSD.
The intermediate development versions of code available on the main trunk
in our CVS repository (also known as ``NetBSD-current'') from _a_f_t_e_r the
point where the release cycle for 1.5 was started are designated by ver-
sion identifiers such as 1.5A, 1.5B, etc. These identifiers do not des-
ignate releases, but indicate major changes in internal kernel APIs.
Note that the kernel from NetBSD 1.5.1 can _n_o_t be used to upgrade a sys-
tem running one of those intermediate development versions. Trying to
use the NetBSD 1.5.1 kernel on such a system _w_i_l_l probably result in
problems.
Please also note that it is not possible to do a direct ``version'' com-
parison between any of the intermediate development versions mentioned
above and 1.5.1 to determine if a given feature is present or absent in
1.5.1. The development of 1.5 and the subsequent ``point'' releases is
done on a separate branch in the CVS repository. The branch was created
when the release cycle for 1.5 was started, and during the release cycle
of 1.5 and its patch releases, selected fixes and enhancements have been
imported from the main development trunk. So, there are features in
1.5.1 which were not in, e.g. 1.5B, and vice versa.
MMaajjoorr CChhaannggeess BBeettwweeeenn 11..55 aanndd 11..55..11
The complete list of changes between NetBSD 1.5 and 1.5.1 can be found in
the file CHANGES-1.5.1 in the top directory of the source tree. The fol-
lowing are highlights only:
++oo A driver for the Aironet/Cisco wireless PCMCIA cards has been added;
see an(4).
++oo NFS client performance has been improved, typically by 40% for writes
but possibly up to 100% in certain setups.
++oo The siop(4) driver has improved in performance and robustness.
++oo Support for cloning pseudo-interfaces has been added. See
ifconfig(8).
++oo Support for 802.1Q virtual LANs has been added. See vlan(4).
++oo The isp(4) driver has been upgraded to (among other things) work on
MacPPC.
++oo BIND has been upgraded to version 8.2.3 (SA2001-001).
++oo Support for booting from RAIDframe RAID1 mirrors on i386 added.
++oo The lfs(4) file system has again been substantially updated, but is
still experimental.
++oo Ultra/66 support has been added for capable VIA chipsets, and Ul-
tra/100 support has been added for the HPT370, Promise and Intel ICH2
controllers in the pciide(4) driver. Support for Intel 82801BAM con-
trollers has also been added, and handling of Ali controllers has
been improved.
++oo OpenSSH has been updated to deal with a security issue (SA2001-003).
++oo Sendmail has been upgraded to version 8.11.3.
++oo The ex(4) driver has added support for 3Com 3c555, 3c556 and 3c556B
MiniPCI Ethernet cards.
++oo A driver for the on-board audio hardware found on many Apple PowerMa-
cs has been added; see awacs(4).
++oo The sip(4) driver has been fixed to properly support the dp83815, as
found in current Netgear FA311 10/100 cards.
++oo ftpd(8) has been updated to deal with two security issues (SA2000-018
and SA2001-005).
++oo ntpd(8) has been updated to deal with a security issue (SA2001-004).
++oo telnetd(8) has been updated to deal with a security issue
(SA2000-017).
++oo A vulnerability on i386 related to USER_LDT has been fixed
(SA2001-002).
++oo The Linux emulation has been enhanced to prepare for the support of
using the Linux version of VMware.
++oo IP checksumming speed has been improved on i386 compared to
NetBSD 1.5 by about 10%.
++oo Support for the Socket Communications LP-E Type II PCMCIA NE2000
clone card has been added to ne(4).
++oo The DHCP software has been upgraded to ISC version 3, Beta 2, patch-
level 23, to fix core dumps in dhclient(8), among other things.
Please note that the new dhcpd(8) forces you to configure a "ddns-up-
date-style" of either "ad-hoc", "interim" or "none".
++oo Various fixes and enhancements to INET6 and IPSEC code; among them
improved interaction between IPF/Nat and IPSEC.
++oo The Heimdal kerberos(8) implementation has been upgraded to version
0.3e.
++oo Support for Accton EN2242 and other AmdTek AN985 cards added to the
tlp(4) driver.
++oo Several country-specific keyboard mappings have been added for USB
keyboards.
++oo A driver for Yamaha YMF724/740/744/745-based sound cards has been
added, see yds(4).
++oo The maximum number of BSD disklabel partitions on the i386 port has
been increased from 8 to 16.
++oo Drivers for the AC'97 based audio sound chips ESS Technology Maestro
1, 2, and 2E (see esm(4)), NeoMagic 256 (see neo(4)), and Cirrus Log-
ic CrystalClear PCI Audio CS4281 (see clct(4)) have been added.
In addition, many bugs have been fixed--more than 95 problems reported
through our problem tracking system have been fixed, and some other non-
reported problems have also been found and fixed. See the CHANGES-1.5.1
file for the complete list.
CChhaannggeess BBeettwweeeenn TThhee NNeettBBSSDD 11..44 aanndd 11..55 RReelleeaasseess
The NetBSD 1.5 release provides numerous significant functional enhance-
ments, including support for many new devices, integration of hundreds of
bug fixes, new and updated kernel subsystems, and many userland enhance-
ments. The result of these improvements is a stable operating system fit
for production use that rivals most commercially available systems.
It is impossible to completely summarize over one year of development
that went into the NetBSD 1.5ZC release. Some highlights include:
_K_e_r_n_e_l
++oo Ports to new platforms including: arc, cobalt, hpcmips, news68k,
sgimips, and sparc64.
++oo Improved performance and stability of the UVM virtual memory subsys-
tem.
++oo Implementation of generic kernel locking code, as well as a restruc-
ture and re-tuning of the scheduler, to be used by the future symmet-
ric multi-processing (SMP) implementation.
++oo Improved compatibility support for Linux, OSF1, and SVR4 programs.
++oo New compatibility support for Win32 programs.
++oo Support for dynamically loaded ELF kernel modules.
++oo Kernel process tracing using ktruss(1).
++oo Deletion of swap devices using swapctl(8).
++oo Easier hot-pluggability of keyboards and mice using a new wscons de-
vice--wsmux.
++oo Improved PCMCIA and CardBus support, including support for detaching
of devices and cards, resulting in better support for notebooks and
PDA devices.
++oo Numerous hardware improvements, including areas such as: audio, UD-
MA/66 support for ATA drives, USB, and wireless networking.
_N_e_t_w_o_r_k_i_n_g
++oo Addition of IP version 6 (IPv6) and IPsec to the networking stack,
from the KAME project. This includes addition of kernel code for
IPv6/IPsec, IPv4/v6 dual-stack user applications and supporting li-
braries. Due to this, the shlib major version for pcap(3) is incre-
mented and you may need to recompile userland tools. The KAME IPv6
part includes results from the unified-IPv6 effort.
_F_i_l_e _s_y_s_t_e_m
++oo Significant Fast file system (FFS) performance enhancements via inte-
gration of Kirk McKusick's soft updates and trickle sync code.
++oo Support for the Windows NT `NTFS' file system (read-only at this
stage).
++oo Support for revision 1 of the Linux `ext2fs' file system.
++oo Enhanced stability and usability of LFS (the BSD log-structured file
system).
++oo Various RAIDframe enhancements including: auto-detection of RAID com-
ponents and auto-configuration of RAID sets, and the ability to con-
figure the root file system (_/) on a RAID set.
++oo Support for Microsoft Joliet extensions to the ISO9660 CD file sys-
tem.
++oo Improved file system vnode locking mechanisms, thus resolving a
source of several panics in the past.
++oo Support for NFS and RPC over IPv6.
++oo The server part of NFS locking (implemented by rpc.lockd(8)) now
works.
_S_e_c_u_r_i_t_y
++oo Strong cryptographic libraries and applications integrated, including
the AES cipher Rijndael, the OpenSSL library, more complete Kerberos
IV and Kerberos V support, and an SSH server and client.
++oo sysctl(3) interfaces to various elements of process and system infor-
mation, allowing programs such as ps(1), dmesg(1) and the like to op-
erate without recompilation after kernel upgrades, and remove the ne-
cessity to run setgid kmem (thus improving system security).
++oo Disable various services by default, and set the default options for
disabled daemons to a higher level of logging.
++oo Several code audits were performed. One audit replaced string rou-
tines that were used without bounds checking, and another one identi-
fied and disabled places where format strings were used in unsafe
ways, allowing arbitrary data to be entered by (possibly) malicious
users to overwrite application code, and leading from Denial of Ser-
vice attacks to compromised systems.
++oo sshd(8) and ssh(1) now require rnd(4) kernel random number devices.
_S_y_s_t_e_m _a_d_m_i_n_i_s_t_r_a_t_i_o_n _a_n_d _u_s_e_r _t_o_o_l_s
++oo Conversion of the rc(8) system startup and shutdown scripts to an
`rc.d' mechanism, with separate control scripts for each service, and
appropriate dependency ordering provided by rcorder(8).
++oo postfix(1) provided as alternative mail transport agent to
sendmail(8).
++oo User management tools useradd(8), usermod(8), userdel(8),
groupadd(8), groupmod(8), and groupdel(8) added to the system.
++oo Incorporation of a login class capability database (_/_e_t_c_/_l_o_g_i_n_._c_o_n_f)
from BSD/OS.
++oo Improved support for usernames longer than eight characters in pro-
grams such as at(1) and w(1).
++oo Many enhancements to ftpd(8) providing features found in larger and
less secure FTP daemons, such as user classes, connection limits, im-
proved support for virtual hosting, transfer statistics, transfer
rate throttling, and support for various IETF ftpext working group
extensions.
++oo The ftp(1) client has been improved even further, including transfer
rate throttling, improved URL support, command line uploads. See the
man page for details.
_M_i_s_c_e_l_l_a_n_e_o_u_s
++oo Updates to the NetBSD source code style code (located in
_/_u_s_r_/_s_h_a_r_e_/_m_i_s_c_/_s_t_y_l_e) to use ANSI C only (instead of K&R) and re-
flect current (best) practice, and begin migrating the NetBSD source
code to follow it.
++oo Implementation of many SUSv2 features to the curses(3) library, in-
cluding support for color.
++oo Updates of most third party packages that are shipped in the base
system, including file(1), ipfilter(4), ppp(4), and sendmail(8) to
the latest stable release.
++oo Many new packages in the _p_k_g_s_r_c system, including standard desktops
like KDE and GNOME as well as latest Tcl/Tk and perl and many of the
components of the Java Enterprise platform. The package framework
itself now has full wildcard dependency support.
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.
NetBSD 1.5ZC on acorn32 is, as usual, also fully backward compatible with
old NetBSD acorn32 binaries, so you don't need to recompile all your lo-
cal programs provided you set the appropriate binary compatibility op-
tions in your kernel configuration.
New port-specific features include:
++oo Addition of Xarm32VIDC Xserver for RiscPC and ARM7500 based systems.
TThhee FFuuttuurree ooff NNeettBBSSDD
The NetBSD Foundation has been incorporated as a non-profit organization.
Its purpose is to encourage, foster and promote the free exchange of com-
puter 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:
++oo providing better organization to keep track of development efforts,
including co-ordination with groups working in related fields.
++oo providing a framework to receive donations of goods and services and
to own the resources necessary to run the NetBSD Project.
++oo providing a better position from which to undertake promotional ac-
tivities.
++oo periodically organizing workshops for developers and other interested
people to discuss ongoing work.
We intend to begin narrowing the time delay between releases. Our ambi-
tion is to provide a full release every six to eight months.
We hope to support even _m_o_r_e 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 sub-
mit them, providing that they are well thought-out and increase the us-
ability 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.
SSoouurrcceess ooff NNeettBBSSDD
Refer to
hhttttpp::////wwwwww..nneettbbssdd..oorrgg//SSiitteess//nneett..hhttmmll.
NNeettBBSSDD 11..55ZZCC RReelleeaassee CCoonntteennttss
The root directory of the NetBSD 1.5ZC release is organized as follows:
_._._._/_N_e_t_B_S_D_-_1_._5_Z_C_/
CHANGES Changes since earlier NetBSD releases.
LAST_MINUTE Last minute changes.
MIRRORS A list of sites that mirror the NetBSD 1.5ZC distribution.
README.files README describing the distribution's contents.
TODO NetBSD 's todo list (also somewhat incomplete and out of
date).
_p_a_t_c_h_e_s_/ Post-release source code patches.
_s_o_u_r_c_e_/ Source distribution sets; see below.
In addition to the files and directories listed above, there is one di-
rectory per architecture, for each of the architectures for which
NetBSD 1.5ZC has a binary distribution. There are also _R_E_A_D_M_E_._e_x_p_o_r_t_-
_c_o_n_t_r_o_l files sprinkled liberally throughout the distribution tree, which
point out that there are some portions of the distribution that may be
subject to export regulations of the United States, e.g. code under
_s_r_c_/_c_r_y_p_t_o and _s_r_c_/_s_y_s_/_c_r_y_p_t_o. It is your responsibility to determine
whether or not it is legal for you to export these portions and to act
accordingly.
The source distribution sets can be found in subdirectories of the _s_o_u_r_c_e
subdirectory of the distribution tree. They contain the complete sources
to the system. The source distribution sets are as follows:
ggnnuussrrcc This set contains the ``gnu'' sources, including the source for
the compiler, assembler, groff, and the other GNU utilities in
the binary distribution sets.
_2_2_._3 _M_B _g_z_i_p_p_e_d_, _9_8_._8 _M_B _u_n_c_o_m_p_r_e_s_s_e_d
ppkkggssrrcc This set contains the ``pkgsrc'' sources, which contain the in-
frastructure to build third-party packages.
_7_._4 _M_B _g_z_i_p_p_e_d_, _7_3_._0 _M_B _u_n_c_o_m_p_r_e_s_s_e_d
sshhaarreessrrcc This set contains the ``share'' sources, which include the
sources for the man pages not associated with any particular
program; the sources for the typesettable document set; the
dictionaries; and more.
_3_._3 _M_B _g_z_i_p_p_e_d_, _1_3_._2 _M_B _u_n_c_o_m_p_r_e_s_s_e_d
ssrrcc This set contains all of the base NetBSD 1.5ZC sources which
are not in ggnnuussrrcc, sshhaarreessrrcc, or ssyyssssrrcc.
_2_4_._8 _M_B _g_z_i_p_p_e_d_, _1_2_3_._1 _M_B _u_n_c_o_m_p_r_e_s_s_e_d
ssyyssssrrcc This set contains the sources to the NetBSD 1.5ZC kernel for
all architectures; config(8); and dbsym(8).
_1_8_._0 _M_B _g_z_i_p_p_e_d_, _9_0_._9 _M_B _u_n_c_o_m_p_r_e_s_s_e_d
xxssrrcc This set contains the sources to the X Window System.
_7_8_._1 _M_B _g_z_i_p_p_e_d_, _3_9_3_._6 _M_B _u_n_c_o_m_p_r_e_s_s_e_d
All the above source sets are located in the _s_o_u_r_c_e_/_s_e_t_s subdirectory of
the distribution tree.
The source sets are distributed as compressed tar files. They may be un-
packed into _/_u_s_r_/_s_r_c with the command:
# (( ccdd // ;; ttaarr --zzxxppff -- )) << sseett__nnaammee..ttggzz
The _s_e_t_s_/_S_p_l_i_t_/ subdirectory contains split versions of the source sets
for those users who need to load the source sets from floppy or otherwise
need a split distribution. The split sets are named _s_e_t___n_a_m_e_._x_x where
_s_e_t___n_a_m_e is the distribution set name, and _x_x is the sequence number of
the file, starting with ``aa'' for the first file in the distribution
set, then ``ab'' for the next, and so on. All of these files except the
last one of each set should be exactly 240,640 bytes long. (The last file
is just long enough to contain the remainder of the data for that distri-
bution set.)
The split distributions may be reassembled and extracted with ccaatt as fol-
lows:
# ccaatt sseett__nnaammee..???? || (( ccdd // ;; ttaarr --zzxxppff -- ))
In each of the source distribution set directories, there are files which
contain the checksums of the files in the directory:
BSDSUM Historic BSD checksums for the various files in that di-
rectory, in the format produced by the command: cckkssuumm --oo 11
_f_i_l_e.
CKSUM POSIX checksums for the various files in that directory,
in the format produced by the command: cckkssuumm _f_i_l_e.
MD5 MD5 digests for the various files in that directory, in
the format produced by the command: cckkssuumm --mm _f_i_l_e.
SYSVSUM Historic AT&T System V UNIX checksums for the various
files in that directory, in the format produced by the
command: cckkssuumm --oo --22 _f_i_l_e.
The MD5 digest is the safest checksum, followed by the POSIX checksum.
The other two checksums are provided only to ensure that the widest pos-
sible range of system can check the integrity of the release files.
_N_e_t_B_S_D_/_a_c_o_r_n_3_2 _s_u_b_d_i_r_e_c_t_o_r_y _s_t_r_u_c_t_u_r_e
The acorn32-specific portion of the NetBSD 1.5ZC release is found in the
_a_c_o_r_n_3_2 subdirectory of the distribution: _._._._/_N_e_t_B_S_D_-_1_._5_Z_C_/_a_c_o_r_n_3_2_/
_I_N_S_T_A_L_L_._h_t_m_l
_I_N_S_T_A_L_L_._p_s
_I_N_S_T_A_L_L_._t_x_t
_I_N_S_T_A_L_L_._m_o_r_e Installation notes in various file formats, including this
file. The _._m_o_r_e file contains underlined text using the
more(1) conventions for indicating italic and bold display.
_b_i_n_a_r_y_/
_k_e_r_n_e_l_/
_n_e_t_b_s_d_._G_E_N_E_R_I_C_._g_z A gzipped NetBSD
kernel containing
code for everything
supported in this
release.
_s_e_t_s_/ acorn32 binary distribution sets; see below.
_i_n_s_t_a_l_l_a_t_i_o_n_/
_f_l_o_p_p_y_/ acorn32 boot and installation floppies; see
below.
_m_i_s_c_/ Miscellaneous acorn32 installation utilities;
see installation section, below.
_B_i_n_a_r_y _d_i_s_t_r_i_b_u_t_i_o_n _s_e_t_s
The NetBSD acorn32 binary distribution sets contain the binaries which
comprise the NetBSD 1.5ZC release for the acorn32. There are eight binary
distribution sets. The binary distribution sets can be found in the
_a_c_o_r_n_3_2_/_b_i_n_a_r_y_/_s_e_t_s subdirectory of the NetBSD 1.5ZC distribution tree,
and are as follows:
bbaassee The NetBSD 1.5ZC acorn32 bbaassee binary distribution. You _m_u_s_t in-
stall this distribution set. It contains the base NetBSD utili-
ties that are necessary for the system to run and be minimally
functional. It includes shared library support, and excludes
everything described below.
ccoommpp Things needed for compiling programs. This set includes the
system include files (_/_u_s_r_/_i_n_c_l_u_d_e) and the various system li-
braries (except the shared libraries, which are included as
part of the bbaassee 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.
eettcc This distribution set contains the system configuration files
that reside in _/_e_t_c and in several other places. This set _m_u_s_t
be installed if you are installing the system from scratch, but
should _n_o_t be used if you are upgrading.
_0_._1 _M_B _g_z_i_p_p_e_d_, _0_._6 _M_B _u_n_c_o_m_p_r_e_s_s_e_d
ggaammeess This set includes the games and their manual pages.
kkeerrnn This set contains a NetBSD/acorn32 1.5ZC GENERIC kernel, named
_/_n_e_t_b_s_d. You _m_u_s_t install this distribution set.
mmaann This set includes all of the manual pages for the binaries and
other software contained in the bbaassee set. Note that it does
not include any of the manual pages that are included in the
other sets.
_6_._3 _M_B _g_z_i_p_p_e_d_, _2_5_._4 _M_B _u_n_c_o_m_p_r_e_s_s_e_d
mmiisscc This set includes the (rather large) system dictionaries, the
typesettable document set, and other files from _/_u_s_r_/_s_h_a_r_e.
_2_._6 _M_B _g_z_i_p_p_e_d_, _1_0_._1 _M_B _u_n_c_o_m_p_r_e_s_s_e_d
tteexxtt This set includes NetBSD's text processing tools, including
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 3.3.6. Binary sets for the X Window System are
distributed with NetBSD. The sets are:
xxbbaassee The basic files needed for a complete X client environment.
This does not include the X servers.
xxccoommpp The extra libraries and include files needed to compile X
source code.
xxccoonnttrriibb Programs that were contributed to X.
xxffoonntt Fonts needed by X.
_6_._2 _M_B _g_z_i_p_p_e_d_, _7_._5 _M_B _u_n_c_o_m_p_r_e_s_s_e_d
xxmmiisscc Miscellaneous X programs.
The acorn32 binary distribution sets are distributed as gzipped tar files
named with the extension ..ttggzz, e.g. _b_a_s_e_._t_g_z.
The instructions given for extracting the source sets work equally well
for the binary sets, but it is worth noting that if you use that method,
the files are _/-relative and therefore are extracted _b_e_l_o_w the current
directory. That is, if you want to extract the binaries into your system,
i.e. replace the system binaries with them, you have to run the ttaarr --xxppff
command from _/.
_N_o_t_e_: Each directory in the acorn32 binary distribution also has its own
checksum files, just as the source distribution does.
NNeettBBSSDD//aaccoorrnn3322 SSyysstteemm RReeqquuiirreemmeennttss aanndd SSuuppppoorrtteedd DDeevviicceess
NetBSD/acorn32 1.5ZC runs on Acorn systems with ARM6 or later processors,
with or without FPU coprocessor. The minimal configuration is said to re-
quire 8 MB of RAM and 50 MB of disk space, though we do not know of any-
one 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 com-
pile, 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.)
_S_u_p_p_o_r_t_e_d _d_e_v_i_c_e_s
++oo RiscPC/A7000(+) floppy controller
++oo IDE controllers
-- Acorn motherboard IDE
-- Simtec IDE controller
-- RapIDE Issue 2 IDE controller
-- ICS V5 & V6 IDE controller
++oo SCSI host adapters
-- Cumana SCSI 2
-- PowerTec SCSI 2
-- MCS Connect32 SCSI 2
-- Acorn SCSI
-- Oak SCSI I
-- Morley SCSI I (uncached only)
++oo VIDC20 video
++oo RiscPC Motherboard serial port
++oo RiscPC Motherboard parallel port
++oo Ethernet adapters
-- Acorn Ether1
-- Atomwide Ether3
-- ANT Ether3
-- ANT Ether5
-- Atomwide EtherA
-- ANT EtherB
-- Acorn EtherH
-- I-cubed EtherH
-- ANT EtherM
++oo Most SCSI disk drives
++oo Most SCSI tape drives
++oo CD-ROM drives
-- Most SCSI CD-ROM drives
-- Most ATAPI CD-ROM drives
_N_o_t_e_: Some low-priced IDE CD-ROM drives are known for be-
ing not or not fully ATAPI compliant, and thus re-
quires some hack (generally an entry to a quirk
table) to work with NetBSD.
++oo Mice
-- RiscPC quadrature mouse
-- A7000 PS/2 mouse
++oo Processors
-- ARM 610
-- ARM 700
-- ARM 700 + FPA11
-- ARM 710
-- ARM 7500
-- ARM 7500FE
-- ARM 810. [*]
-- SA110
++oo Motherboards
-- Acorn RiscPC
-- Acorn A7000
-- Acorn A7000+
++oo Other devices
-- RiscPC keyboard
-- A7000 keyboard
-- RiscPC realtime clock
Drivers for hardware marked with ``[*]'' are _n_o_t present in installation
kernels.
Support for some devices is limited to particular kernels. eg there is no
SA110 support in A7000 kernels.
_U_n_s_u_p_p_o_r_t_e_d _d_e_v_i_c_e_s
++oo Acorn/Aleph1 PC cards
++oo Any SCSI card using a PowerROM
++oo Podule based serial ports
++oo Castle SCSI/Ethernet cards
Drivers are planned for some of the above devices.
GGeettttiinngg tthhee NNeettBBSSDD SSyysstteemm oonn ttoo UUsseeffuull MMeeddiiaa
Installation is supported from several media types, including:
++oo CD-ROM
++oo MS-DOS floppy
++oo FTP
++oo Remote NFS partition
++oo Tape
++oo Existing NetBSD partitions, if performing an upgrade
The steps necessary to prepare the distribution sets for installation de-
pend upon which installation medium you choose. The steps for the vari-
ous media are outlined below.
_C_D_-_R_O_M Find out where the distribution set files are on the CD-
ROM.
Proceed to the instruction on installation.
_M_S_-_D_O_S _f_l_o_p_p_y Count the number of _s_e_t___n_a_m_e_._x_x 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 _n_o_t 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 _s_e_t___n_a_m_e_._x_x 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 sec-
tion on preparing your hard disk, below. If you're up-
grading an existing installation, go directly to the sec-
tion on upgrading.
_F_T_P The preparations for this installation/upgrade method are
easy; all you need to do is make sure that there's an FTP
site from which you can retrieve the NetBSD distribution
when you're about to install or upgrade. You need to know
the numeric IP address of that site, and, if it's not on a
network directly connected to the machine on which you're
installing or upgrading NetBSD, you need to know the nu-
meric IP address of the router closest to the NetBSD ma-
chine. Finally, you need to know the numeric IP address
of the NetBSD machine itself. If you don't have access to
a functioning nameserver during installation, the IP ad-
dress of ffttpp..nneettbbssdd..oorrgg is 204.152.184.75 (as of April,
2001).
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.
_N_o_t_e_: This method of installation is recommended only for
those already familiar with using BSD network con-
figuration and management commands. If you aren't,
this documentation should help, but is not intended
to be all-encompassing.
_N_F_S Place the NetBSD distribution sets you wish to install in-
to a directory on an NFS server, and make that directory
mountable by the machine on which you are installing or
upgrading NetBSD. This will probably require modifying
the _/_e_t_c_/_e_x_p_o_r_t_s file on of the NFS server and resetting
its mount daemon (mountd). (Both of these actions will
probably require superuser privileges on the server.)
You need to know the numeric IP address of the NFS server,
and, if the server is not on a network directly connected
to the machine on which you're installing or upgrading
NetBSD, you need to know the numeric IP address of the
router closest to the NetBSD machine. Finally, you need
to know the numeric IP address of the NetBSD machine it-
self.
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 up-
grading.
_N_o_t_e_: This method of installation is recommended only for
those already familiar with using BSD network con-
figuration and management commands. If you aren't,
this documentation should help, but is not intended
to be all-encompassing.
_T_a_p_e To install NetBSD from a tape, you need to make a tape
that contains the distribution set files, in `tar' format.
If you're making the tape on a UNIX-like system, the easi-
est way to do so is probably something like:
# ttaarr --ccff _t_a_p_e___d_e_v_i_c_e _d_i_s_t___d_i_r_e_c_t_o_r_i_e_s
where _t_a_p_e___d_e_v_i_c_e is the name of the tape device that de-
scribes the tape drive you're using; possibly _/_d_e_v_/_r_s_t_0,
or something similar, but it will vary from system to sys-
tem. (If you can't figure it out, ask your system admin-
istrator.) In the above example, _d_i_s_t___d_i_r_e_c_t_o_r_i_e_s are the
distribution sets' directories, for the distribution sets
you wish to place on the tape. For instance, to put the
mmiisscc,, bbaassee,, and eettcc distributions on tape (in order to do
the absolute minimum installation to a new disk), you
would do the following:
# ccdd ......//NNeettBBSSDD--11..55ZZCC
# ccdd aaccoorrnn3322//bbiinnaarryy
# ttaarr --ccff _t_a_p_e___d_e_v_i_c_e mmiisscc eettcc kkeerrnn
_N_o_t_e_: You still need to fill in _t_a_p_e___d_e_v_i_c_e in the
example.
Once you have the files on the tape, you can proceed to
the next step in the installation or upgrade process. If
you're installing NetBSD from scratch, go to the section
on preparing your hard disk, below. If you're upgrading
an existing installation, go directly to the section on
upgrading.
_U_p_g_r_a_d_e If you are upgrading NetBSD, you also have the option of
installing NetBSD by putting the new distribution sets
somewhere in your existing file system, and using them
from there. To do that, you must do the following:
Place the distribution sets you wish to upgrade somewhere
in your current file system tree. Please note that the
_/_d_e_v on the floppy used for upgrades only knows about wd0,
wd1, sd0, sd1, and sd2. If you have more than two IDE
drives or more than three SCSI drives, you should take
care not to place the sets on the high-numbered drives.
At a bare minimum, you must upgrade the bbaassee and kkeerrnn bi-
nary distributions, and so must put the bbaassee and kkeerrnn sets
somewhere in your file system. If you wish, you can do
the other sets, as well, but you should _n_o_t upgrade the
eettcc distribution; it contains contains system configura-
tion files that you should review and update by hand.
Once you have done this, you can proceed to the next step
in the upgrade process, actually upgrading your system.
PPrreeppaarriinngg yyoouurr SSyysstteemm ffoorr NNeettBBSSDD iinnssttaallllaattiioonn
First and foremost, before beginning the installation process, _m_a_k_e _s_u_r_e
_y_o_u _h_a_v_e _a _r_e_l_i_a_b_l_e _b_a_c_k_u_p of any data on your hard disk that you wish to
keep. Repartitioning your hard disk is an excellent way to destroy impor-
tant data.
Second, read and perform the instructions in _a_c_o_r_n_3_2_/_p_l_a_t_f_o_r_m_/_p_r_e_p that
are specific to your platform for partitioning and booting (even if
you're dedicating a device to NetBSD).
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.
IInnssttaalllliinngg tthhee NNeettBBSSDD SSyysstteemm
Installing NetBSD is a relatively complex process, but if you have this
document in hand and are careful to read and remember the information
which is presented to you by the install program, it shouldn't be too
much trouble.
Before you begin, you should know the geometry of your hard disk, i.e.
the sector size (note that sector sizes other than 512 bytes are not cur-
rently supported), the number of sectors per track, the number of tracks
per cylinder (also known as the number of heads), and the number of
cylinders on the disk. The NetBSD kernel will try to discover these pa-
rameters on its own, and if it can it will print them at boot time. If
possible, you should use the parameters it prints. (You might not be
able to because you're sharing your disk with another operating system,
or because your disk is old enough that the kernel can't figure out its
geometry.)
If NetBSD will be sharing the disk with RiscOS or another operating sys-
tem, you should have already completed the section of these notes that
instructed you on how to prepare your hard disk. You should know the size
of the NetBSD area of the disk and its offset from the beginning of the
disk. You will need this information when setting up your NetBSD parti-
tions.
You should now be ready to install NetBSD. It might be handy for you to
have a pencil, some paper, and a calculator handy.
The following is a walk-through of the steps you will take while getting
NetBSD installed on your hard disk. If any question has a default answer,
it 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.
Boot your machine using the installation kernel for your platform. (In-
structions for doing this on your platform can be found in the prepara-
tion section of this document.)
If this doesn't work, ensure that you're using the correct kernel for
your hardware.
Depending upon your platform and the method of loading the, it may take a
while to load the kernel.
You will then be presented with the NetBSD kernel boot messages. You will
want to read them, to determine your disk's name and geometry. 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 will need your
disk's geometry when creating NetBSD 's partitions. You will also need to
know the name, to tell the install tools what disk to install on.
While booting, you will probably see several warnings. You should be
warned that no swap space is present, and that init(8) cannot find
_/_e_t_c_/_r_c_. Do not be alarmed, these are completely normal. When you reach
the prompt asking you for a shell name, just press RETURN.
You will be asked if you wish to install or upgrade your system or go to
a shell prompt. Enter iinnssttaallll.
You will be presented with a welcome message and a prompt, asking if you
wish to proceed with the installation process. If you wish to proceed,
enter `yy' and press RETURN.
You will be asked what type of disk driver you have. The valid options
are listed by the install program, to make sure you get it right.
The install program will then tell you which disks of that type it can
install on, and ask you which it should use. Reply with the name of your
disk. (The first disk of the type you selected, either wd0 for IDE disks,
or sd0 for SCSI disks, is the default.)
You will then be asked to name your disk's disklabel. The default re-
sponse is `mmyywwdd' or `mmyyssdd' depending on the type of your disk, and for
most purposes it will be OK. If you choose to name it something differ-
ent, make sure the name is a single word and contains no special charac-
ters. You don't need to remember this name.
You will be prompted for your disk's geometry information, i.e. the num-
ber of bytes per sector, cylinders on the disk, tracks per cylinder
(heads), and sectors per track. Enter them when they are requested. If
you make a mistake, press CONTROL-C and when you get to the shell prompt,
restart the install process by running the iinnssttaallll command. Once you have
entered this data, the install program will tell you the total size of
your disk, in both sectors, and cylinders. Remember this number; if
you're installing on the whole disk, you'll need it again soon.
When describing your partitions, you will have the option of entering da-
ta about them in units of disk sectors or cylinders. If you choose to en-
ter the information in units of sectors, remember that, for optimal per-
formance, partitions should begin and end on cylinder boundaries. You
will be asked about which units you wish to use, and you should reply
with `cc' for cylinders, or `ss' for sectors.
You will be asked for the size of the NetBSD portion of the disk. If
you're installing on the whole disk, reply with the size of the disk, as
printed earlier by the install program. If you're using only part of the
disk, reply with the size that you specified in the partition editor.
(Don't forget to enter the size in the units you specified in the last
step!)
If you are not installing on the whole disk, you will be asked for the
offset of the NetBSD partition from the beginning of the disk. Reply with
the appropriate offset (again, in whichever units you specified), as de-
termined by how you set up your disk using the partition editor.
You will be asked to enter the size of your NetBSD root partition (_/).
It should be at least 13 MB, but if you are going to be doing develop-
ment, 14-16 MB is a more desirable size. This size should be expressed in
units of sectors or cylinders, depending on which you said you wanted to
use.
Next, you will be asked for the size of your swap partition. You should
probably allocate twice as much swap space as you have real memory. Sys-
tems that will be heavily used should have more swap space allocated, and
systems that will be lightly used can get by with less. If you want the
system to be able to save crash dumps when it panics, you will need at
least as much swap space as you have RAM. Again, this number should be
expressed in units of sectors or cylinders, as appropriate.
The install program will then ask you for information about the rest of
the partitions you want on your disk. For most purposes, you will want
only one more partition, _/_u_s_r. (Machines used as servers will probably
also want _/_v_a_r as a separate partition. That can be done with these in-
stallation tools, but is not covered here.) The install program will tell
you how much space there is left to be allocated in the NetBSD area of
the disk, and, if you only want one more partition (_/_u_s_r), you should en-
ter it at the prompt when the installer asks you how large the next par-
tition should be. It will then ask you for the name of the mount point
for that partition. If you're doing a basic installation, that is _/_u_s_r.
_Y_o_u _a_r_e _n_o_w _a_t _t_h_e _p_o_i_n_t _o_f _n_o _r_e_t_u_r_n_. Nothing has been written to your
disk yet, but if you confirm that you want to install NetBSD, your hard
drive will be modified, and its contents may be scrambled at the whim of
the install program. This is especially likely if you have given the in-
stall program incorrect information. If you are sure you want to proceed,
enter yyeess 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. It will also create an
_/_e_t_c_/_f_s_t_a_b for your system, and mount all of the file systems under _/_m_n_t.
(In other words, your _/ (root) partition will be mounted on _/_m_n_t, your
_/_u_s_r partition on _/_m_n_t_/_u_s_r, and so on.) There should be no errors in this
section of the installation. If there are, restart from the beginning of
the installation process.
You will be placed at a shell prompt ( `#'). The task is to install the
distribution sets. The flow of installation differs depending on your
hardware resources, and on what media the distribution sets reside.
_T_o _i_n_s_t_a_l_l _f_r_o_m _f_l_o_p_p_y
The first thing you should do is pick a temporary directory where the
distribution files can be stored. To do this, enter the command
SSeett__ttmmpp__ddiirr, and enter the name of the temporary directory. (Don't forget
that if your disk is still mounted under _/_m_n_t; you should probably pick a
directory under _/_m_n_t_/_u_s_r.)
After you have picked a temporary directory, enter the LLooaadd__ffdd command,
to load the distribution sets from your floppies.
You will be asked which floppy drive to use. Enter `00' (zero) if you're
using the first floppy drive, or enter `11' if you're using the second.
You will be prompted to insert a floppy into the drive, to have its con-
tents copied to your hard disk. Do so, and press RETURN to begin copying.
When that is done, read the remainder of the floppies that contain the
distribution sets that you want to install, one by one. When the last is
read, and you are being prompted for another, press CONTROL-C.
Run the EExxttrraacctt command once for each distribution set you wish to in-
stall. For instance, if you wish to install the bbaassee distribution set,
followed by the tteexxtt distribution set, and finally the eettcc distribution
set, use the commands:
# EExxttrraacctt bbaassee
# EExxttrraacctt tteexxtt
# EExxttrraacctt eettcc
For each extraction, it will ask you if the extraction should be verbose.
If you reply affirmatively, it will print out the name of each file
that's being extracted.
_N_o_t_e_: If you know that you will be running low on disk space when in-
stalling NetBSD, you can load and extract one distribution set at
a time. To do this, load only the floppies which contain the files
for the first distribution set, extract them, and then change to
the temporary directory and remove them with the command rrmm
sseett__nnaammee..????
Once you are finished extracting all of the sets that you wish to in-
stall, you should proceed to the instructions below (after the last in-
stall medium type-specific instructions), that explain how you should
configure your system.
_T_o _i_n_s_t_a_l_l _f_r_o_m _t_a_p_e
The first thing you should do is pick a temporary directory where the
distribution files can be stored. To do this, enter the command
SSeett__ttmmpp__ddiirr, and enter the name of the temporary directory. (Don't forget
that your disk is mounted under _/_m_n_t; you should probably pick a directo-
ry under _/_m_n_t_/_u_s_r.) The default is _/_m_n_t_/_u_s_r_/_d_i_s_t_r_i_b.
After you have picked a temporary directory, enter the LLooaadd__ttaappee command,
to load the distribution sets from tape.
You will be asked which tape drive to use. The default is rst0, which is
correct if you're using the SCSI tape drive with the lowest SCSI-ID num-
ber. (For the SCSI tape drive with the next lowest SCSI-ID number, you
should use rst1, and so on.)
You will be prompted to press RETURN when you have inserted the tape into
the tape drive. When you do, the contents of the tape will be extracted
into the temporary directory, and the names of the files being extracted
will be printed.
After the tape has been extracted, to go the directory containing the
first distribution set you wish to install. (Depending on how you made
the tape, it's probably a subdirectory of the temporary directory you
specified above.) Once there, run the SSeett__ttmmpp__ddiirr command again, and ac-
cept its default answer by pressing return at the prompt.
Use the EExxttrraacctt command to extract the distribution set. For instance, if
you're extracting the bbaassee set, use the command:
# EExxttrraacctt bbaassee
You will be asked if you wish the extraction to be verbose. If you reply
affirmatively, the name of each file being extracted will be printed.
Repeat the previous two steps for each distribution set you wish to in-
stall. Change to the set's directory, run SSeett__ttmmpp__ddiirr, and then run
EExxttrraacctt _s_e_t___n_a_m_e to extract the set.
Once you are finished extracting all of the sets that you wish to in-
stall, you should proceed to the instructions below (after the last in-
stall medium type-specific instructions), that explain how you should
configure your system.
_T_o _i_n_s_t_a_l_l _v_i_a _F_T_P _o_r _N_F_S
The first thing you should do is pick a temporary directory where the
distribution files can be stored. To do this, enter the command
SSeett__ttmmpp__ddiirr, and enter the name of the temporary directory. (Don't forget
that your disk is mounted under _/_m_n_t; you should probably pick a directo-
ry under _/_m_n_t_/_u_s_r.) The default is _/_m_n_t_/_u_s_r_/_d_i_s_t_r_i_b.
Configure the appropriate ethernet interface (e.g. ea0, eb0, etc.) up,
with a command like:
iiffccoonnffiigg _i_f_n_a_m_e _i_p_a_d_d_r [nneettmmaasskk _n_e_t_m_a_s_k]
where _i_f_n_a_m_e is the interface name, like those listed above, and _i_p_a_d_d_r
is the numeric IP address of the interface. If the interface has a spe-
cial netmask, supply the word nneettmmaasskk and that netmask at the end of the
command line. (The brackets indicate that those arguments are optional.)
For instance, to configure interface _e_a_0 with IP address 129.133.10.10,
use the command:
# iiffccoonnffiigg eeaa00 112299..113333..1100..1100
and to configure interface _e_b_0 with IP address 128.32.240.167 and a spe-
cial netmask, 0xffffff00, use the command:
# iiffccoonnffiigg eebb00 112288..3322..224400..116677 nneettmmaasskk 00xxffffffffffff0000
If the NFS server or FTP server is not on a directly- connected network,
you need to set up a route to it using a command like:
rroouuttee aadddd ddeeffaauulltt _g_a_t_e___i_p_a_d_d_r
where _g_a_t_e___i_p_a_d_d_r is your gateway's numeric IP address.
If you are NFS-mounting the distribution sets, mount them on the tempo-
rary directory with a command like:
mmoouunntt --tt nnffss _s_e_r_v___i_p_a_d_d_r_:_d_i_s_t___d_i_r _t_m_p___d_i_r
where _s_e_r_v___i_p_a_d_d_r is the server's numeric IP address, _d_i_s_t___d_i_r is the
path to the distribution files on the server, and _t_m_p___d_i_r is the name of
the local temporary directory.
Once this is done, proceed as if you had loaded the files from tape,
changing to the appropriate directories, running SSeett__ttmmpp__ddiirr, and running
EExxttrraacctt as appropriate.
If you are retrieving the distribution sets using ftp, change into the
temporary directory, and execute the command:
ffttpp _s_e_r_v___i_p_a_d_d_r
where _s_e_r_v___i_p_a_d_d_r is once again the server's numeric IP address. Get the
files with FTP, taking care to use binary mode when transferring the
files.
Once you have all of the files for the distribution sets that you wish to
install, you can proceed using the instructions above, as if you had in-
stalled from a floppy. (Note that as with the floppy install, if you're
short on disk space, you can transfer only one set at a time, extract it,
then delete it, to save space.)
_T_o _i_n_s_t_a_l_l _f_r_o_m _C_D_-_R_O_M
First create a mount point so that you can mount the CD-ROM:
# mmkkddiirr //mmnntt//ccddrroomm
If you get an error here of ``mkdir: /mnt/cdrom'', don't worry it just
means that you didn't need to create the directory.
Then all you need to do is mount the CD-ROM. For the first CD-ROM drive
use:
# mmoouunntt --rrtt ccdd99666600 //ddeevv//ccdd00aa //mmnntt//ccddrroomm
Or, for the second use:
# mmoouunntt --rrtt ccdd99666600 //ddeevv//ccdd11aa //mmnntt//ccddrroomm
Once this is done, extract the required sets as described in the _T_o
_i_n_s_t_a_l_l _f_r_o_m _f_l_o_p_p_y section, but ensure that you set the temporary direc-
tory to the location of the sets on the CD-ROM (usually _/_c_d_r_o_m_/_d_i_s_t_r_i_b,
but check the release notes that came with the CD).
_C_o_m_p_l_e_t_i_n_g _y_o_u_r _i_n_s_t_a_l_l_a_t_i_o_n
Once you have finished extracting all of the distribution sets that you
wish to install, and are back at the `#' prompt, you are ready to config-
ure your system. The configuration utility expects that you have in-
stalled the bbaassee and eettcc distribution sets. If you have not, you will not
be able to run it successfully (nor will you have a functional system, in
any case). To configure your newly-installed NetBSD system, run the com-
mand CCoonnffiigguurree. It will ask you for the system's host name, domain name,
and other network configuration information. It will set up your configu-
ration files and make the device nodes for the newly-installed system.
_C_o_n_g_r_a_t_u_l_a_t_i_o_n_s_, _y_o_u _h_a_v_e _s_u_c_c_e_s_s_f_u_l_l_y _i_n_s_t_a_l_l_e_d NetBSD 1.5ZC.
PPoosstt iinnssttaallllaattiioonn sstteeppss
Once you've got the operating system running, there are a few things you
need to do in order to bring the system into a properly configured state,
with the most important ones described below.
1. Configuring _/_e_t_c_/_r_c_._c_o_n_f
If you or the installation software haven't done any configuration
of _/_e_t_c_/_r_c_._c_o_n_f (ssyyssiinnsstt usually will), the system will drop you in-
to single user mode on first reboot with the message
/etc/rc.conf is not configured. Multiuser boot aborted.
and with the root file system (_/) mounted read-write. When the sys-
tem asks you to choose a shell, simply press RETURN to get to a
_/_b_i_n_/_s_h prompt. If you are asked for a terminal type, respond with
vvtt222200 (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:
# ssttttyy eerraassee ''^^hh''
# ssttttyy eerraassee ''^^??''
At this point, you need to configure at least one file in the _/_e_t_c
directory. You will need to mount your root filesystem read/write
with:
# //ssbbiinn//mmoouunntt --uu --ww //
Change to the _/_e_t_c directory and take a look at the _/_e_t_c_/_r_c_._c_o_n_f
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 _/_e_t_c_/_d_e_f_a_u_l_t_s_/_r_c_._c_o_n_f, where some in-line documentation
may be found. More complete documentation can be found in
rc.conf(5).
If your _/_u_s_r directory is on a separate partition and you do not
know how to use eedd, you will have to mount your _/_u_s_r partition to
gain access to eexx or vvii. Do the following:
# mmoouunntt //uussrr
# eexxppoorrtt TTEERRMM==vvtt222200
If you have _/_v_a_r on a separate partition, you need to repeat that
step for it. After that, you can edit _/_e_t_c_/_r_c_._c_o_n_f with vi(1). When
you have finished, type eexxiitt at the prompt to leave the single-user
shell and continue with the multi-user boot.
Other values that need to be set in _/_e_t_c_/_r_c_._c_o_n_f for a networked en-
vironment are _h_o_s_t_n_a_m_e and possibly _d_e_f_a_u_l_t_r_o_u_t_e, furthermore add an
_i_f_c_o_n_f_i_g___i_n_t 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 _m_y_n_a_m_e_._m_y_._d_o_m in _/_e_t_c_/_h_o_s_t_s:
ifconfig_de0="inet myname.my.dom netmask 255.255.255.0"
To enable proper hostname resolution, you will also want to add an
_/_e_t_c_/_r_e_s_o_l_v_._c_o_n_f file or (if you are feeling a little more adventur-
ous) run named(8). See resolv.conf(5) or named(8) for more informa-
tion.
Other files in _/_e_t_c that may require modification or setting up in-
clude _/_e_t_c_/_m_a_i_l_e_r_._c_o_n_f, _/_e_t_c_/_n_s_s_w_i_t_c_h_._c_o_n_f, and _/_e_t_c_/_w_s_c_o_n_s_._c_o_n_f.
2. Logging in
After reboot, you can log in as root at the login prompt. Unless
you've set a password in ssyyssiinnsstt, there is no initial password. If
you're using the machine in a networked environment, you should cre-
ate an account for yourself (see below) and protect it and the
``root'' account with good passwords. Unless you have connected an
unusual terminal device as the console you can just press RETURN
when it prompts for Terminal type? [...].
3. Adding accounts
Use the useradd(8) command to add accounts to your system, _d_o _n_o_t
edit _/_e_t_c_/_p_a_s_s_w_d directly. See useradd(8) for more information on
how to add a new user to the system.
4. The X Window System
If you have installed the X Window System, look at the files in
_/_u_s_r_/_X_1_1_R_6_/_l_i_b_/_X_1_1_/_d_o_c for information.
Don't forget to add _/_u_s_r_/_X_1_1_R_6_/_b_i_n to your path in your shell's dot
file so that you have access to the X binaries.
5. Installing third party packages
If you wish to install any of the software freely available for
UNIX-like systems you are strongly advised to first check the NetBSD
package system. This automatically handles any changes necessary to
make the software run on NetBSD, retrieval and installation of any
other packages on which the software may depend, and simplifies in-
stallation (and deinstallation), both from source and precompiled
binaries.
++oo More information on the package system is at
hhttttpp::////wwwwww..nneettbbssdd..oorrgg//DDooccuummeennttaattiioonn//ssooffttwwaarree//ppaacckkaaggeess..hhttmmll
++oo A browsable listing of available packages is at
ffttpp::////ffttpp..nneettbbssdd..oorrgg//ppuubb//NNeettBBSSDD//ppaacckkaaggeess//ppkkggssrrcc//RREEAADDMMEE..hhttmmll
++oo Precompiled binaries can be found at
ffttpp::////ffttpp..nneettbbssdd..oorrgg//ppuubb//NNeettBBSSDD//ppaacckkaaggeess,
usually in the _1_._5_Z_C_/_a_c_o_r_n_3_2_/_A_l_l subdir. You can install them
with the following commands:
## PPKKGG__PPAATTHH==ffttpp::////ffttpp..nneettbbssdd..oorrgg//ppuubb//NNeettBBSSDD//ppaacckkaaggeess//11..55ZZCC//aaccoorrnn3322//AAllll
## eexxppoorrtt PPKKGG__PPAATTHH
## ppkkgg__aadddd --vv ttccsshh
## ppkkgg__aadddd --vv aappaacchhee
## ppkkgg__aadddd --vv ppeerrll
...
The above commands will install the tcsh shell, the Apache web
server and the perl programming language as well as all the
packages they depend on.
++oo Package sources for compiling packages on your own can be ob-
tained by retrieving the file
ffttpp::////ffttpp..nneettbbssdd..oorrgg//ppuubb//NNeettBBSSDD//NNeettBBSSDD--
ccuurrrreenntt//ttaarr__ffiilleess//ppkkggssrrcc..ttaarr..ggzz
They are typically extracted into _/_u_s_r_/_p_k_g_s_r_c (though other lo-
cations work fine), with the commands:
# mmkkddiirr //uussrr//ppkkggssrrcc
# (( ccdd //uussrr//ppkkggssrrcc ;; ttaarr --zzxxppff -- )) << ppkkggssrrcc..ttaarr..ggzz
After extracting, then see the _R_E_A_D_M_E file in the extraction di-
rectory (e.g. _/_u_s_r_/_p_k_g_s_r_c_/_R_E_A_D_M_E) for more information.
6. Misc
++oo Edit _/_e_t_c_/_m_a_i_l_/_a_l_i_a_s_e_s to forward root mail to the right place.
Don't forget to run newaliases(1) afterwards.
++oo The _/_e_t_c_/_m_a_i_l_/_s_e_n_d_m_a_i_l_._c_f file will almost definitely need to be
adjusted; files aiding in this can be found in
_/_u_s_r_/_s_h_a_r_e_/_s_e_n_d_m_a_i_l. See the README file there for more infor-
mation.
++oo Edit _/_e_t_c_/_r_c_._l_o_c_a_l to run any local daemons you use.
++oo Many of the _/_e_t_c files are documented in section 5 of the manu-
al; so just invoking
# mmaann 55 _f_i_l_e_n_a_m_e
is likely to give you more information on these files.
UUppggrraaddiinngg aa pprreevviioouussllyy--iinnssttaalllleedd NNeettBBSSDD SSyysstteemm
The upgrade to NetBSD 1.5ZC is a binary upgrade; it can be quite diffi-
cult to advance to a later version by recompiling from source due primar-
ily to interdependencies in the various components.
To do the upgrade, you must have the boot floppy available. You must al-
so have at least the bbaassee and kkeerrnn binary distribution sets available, so
that you can upgrade with them, using one of the upgrade methods de-
scribed above. Finally, you must have sufficient disk space available to
install the new binaries. Since the old binaries are being overwritten
in place, you only need space for the new binaries, which weren't previ-
ously on the system. If you have a few megabytes free on each of your
root (_/) and _/_u_s_r partitions, you should have enough space.
Since upgrading involves replacing the boot blocks on your NetBSD parti-
tion, the kernel, and most of the system binaries, it has the potential
to cause data loss. You are strongly advised to _b_a_c_k _u_p _a_n_y _i_m_p_o_r_t_a_n_t
_d_a_t_a _o_n _y_o_u_r _d_i_s_k, whether on the NetBSD partition or on another operat-
ing system's partition, before beginning the upgrade process.
The upgrade procedure using the ssyyssiinnsstt tool is similar to an installa-
tion, but without the hard disk partitioning. The original _/_e_t_c directo-
ry is renamed to _/_e_t_c_._o_l_d, and no attempt is made to merge any of the
previous configuration into the new system except that the previous
_/_e_t_c_/_f_s_t_a_b file is copied into the new configuration. 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 san-
ity checks are done, i.e. file systems are checked before unpacking the
sets.
After a new kernel has been copied to your hard disk, your machine is a
complete NetBSD 1.5ZC system. However, that doesn't mean that you're fin-
ished with the upgrade process. You will probably want to update the set
of device nodes you have in _/_d_e_v. If you've changed the contents of _/_d_e_v
by hand, you will need to be careful about this, but if not, you can just
cd into _/_d_e_v, and run the command:
# sshh MMAAKKEEDDEEVV aallll
You must also deal with certain changes in the formats of some of the
configuration files. The most notable change is that the options given to
many of the file systems in _/_e_t_c_/_f_s_t_a_b have changed, and some of the file
systems have changed names. To find out what the new options are, it's
suggested that you read the manual page for the file system's mount com-
mands, for example mount_nfs(8) for NFS.
Finally, you will want to delete old binaries that were part of the ver-
sion of NetBSD that you upgraded from and have since been removed from
the NetBSD distribution.
CCoommppaattiibbiilliittyy IIssssuueess WWiitthh PPrreevviioouuss NNeettBBSSDD RReelleeaasseess
Users upgrading from previous versions of NetBSD may wish to bear the
following problems and compatibility issues in mind when upgrading to
NetBSD 1.5ZC.
_G_e_n_e_r_a_l _i_s_s_u_e_s
++oo _/_e_t_c_/_r_c modified to use _/_e_t_c_/_r_c_._d_/_*
Prior to NetBSD 1.5, _/_e_t_c_/_r_c was a traditional BSD style monolithic
file; each discrete program or substem from _/_e_t_c_/_r_c and _/_e_t_c_/_n_e_t_s_t_a_r_t
has been moved into separate scripts in _/_e_t_c_/_r_c_._d_/.
At system startup, _/_e_t_c_/_r_c uses rcorder(8) to build a dependency list
of the files in _/_e_t_c_/_r_c_._d and then executes each script in turn with
an argument of `start'. Many _r_c_._d scripts won't start unless the ap-
propriate rc.conf(5) entry in _/_e_t_c_/_r_c_._c_o_n_f is set to `YES.'
At system shutdown, _/_e_t_c_/_r_c_._s_h_u_t_d_o_w_n uses rcorder(8) to build a de-
pendency list of the files in _/_e_t_c_/_r_c_._d that have a ``KEYWORD:
shutdown'' line, reverses the resulting list, and then executes each
script in turn with an argument of `stop'. The following scripts
support a specific shutdown method: _c_r_o_n, _i_n_e_t_d, _l_o_c_a_l, and _x_d_m.
Local and third-party scripts may be installed into _/_e_t_c_/_r_c_._d as nec-
essary. Refer to the other scripts in that directory and rc(8) for
more information on implementing _r_c_._d scripts.
_I_s_s_u_e_s _a_f_f_e_c_t_i_n_g _a_n _u_p_g_r_a_d_e _f_r_o_m _N_e_t_B_S_D _1_._4 _o_r _p_r_i_o_r
++oo named(8) leaks version information
Previous releases of NetBSD disabled a feature of named(8) where the
version number of the server could be determined by remote clients.
This feature has not been disabled in NetBSD 1.5, because there is a
named.conf(5) option to change the version string:
option {
version "newstring";
};
++oo sysctl(8) pathname changed
sysctl(8) is moved from _/_u_s_r_/_s_b_i_n_/_s_y_s_c_t_l to _/_s_b_i_n_/_s_y_s_c_t_l. If you
have hardcoded references to the full pathname (in shell scripts, for
example) please be sure to update those.
++oo sendmail(8) configuration file pathname changed
Due to sendmail(8) upgrade from 8.9.x to 8.10.x, _/_e_t_c_/_s_e_n_d_m_a_i_l_._c_f is
moved to _/_e_t_c_/_m_a_i_l_/_s_e_n_d_m_a_i_l_._c_f. Also, the default sendmail.cf(5)
refers different pathnames than before. For example, _/_e_t_c_/_a_l_i_a_s_e_s is
now located at _/_e_t_c_/_m_a_i_l_/_a_l_i_a_s_e_s, _/_e_t_c_/_s_e_n_d_m_a_i_l_._c_w is now called
_/_e_t_c_/_m_a_i_l_/_l_o_c_a_l_-_h_o_s_t_-_n_a_m_e_s, and so forth. If you have customized
sendmail.cf(5) and friends, you will need to move the files to the
new locations. See _/_u_s_r_/_s_h_a_r_e_/_s_e_n_d_m_a_i_l_/_R_E_A_D_M_E for more information.
++oo sshd(8) configuration file pathname changed
Configuration files for ssh(1) and sshd(8) are moved from _/_e_t_c to
_/_e_t_c_/_s_s_h.
UUssiinngg oonnlliinnee NNeettBBSSDD ddooccuummeennttaattiioonn
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
++oo intro(1),
++oo man(1),
++oo apropros(1),
++oo passwd(1), and
++oo 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 _m_a_n command is used to view the documentation on a topic, and is
started by entering mmaann [_s_e_c_t_i_o_n] _t_o_p_i_c. The brackets [] around the sec-
tion should not be entered, but rather indicate that the section is op-
tional. If you don't ask for a particular section, the topic with the
lowest numbered section name will be displayed. For instance, after log-
ging in, enter
# mmaann ppaasssswwdd
to read the documentation for passwd(1). To view the documentation for
passwd(5), enter
# mmaann 55 ppaasssswwdd
instead.
If you are unsure of what man page you are looking for, enter aapprrooppooss
_s_u_b_j_e_c_t_-_w_o_r_d
where _s_u_b_j_e_c_t_-_w_o_r_d is your topic of interest; a list of possibly related
man pages will be displayed.
AAddmmiinniissttrriivviiaa
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
_m_a_j_o_r_d_o_m_o_@_n_e_t_b_s_d_._o_r_g. To get help on using the mailing list server, send
mail to that address with an empty body, and it will reply with instruc-
tions.
There are various mailing lists set up to deal with comments and ques-
tions about this release. Please send comments to: _n_e_t_b_s_d_-
_c_o_m_m_e_n_t_s_@_n_e_t_b_s_d_._o_r_g.
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 in-
clude lots of details. Additionally, bug reports can be sent by mail to:
_n_e_t_b_s_d_-_b_u_g_s_@_n_e_t_b_s_d_._o_r_g.
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
hhttttpp::////wwwwww..nneettbbssdd..oorrgg//MMaaiilliinnggLLiissttss//.
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 be-
low).
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: _n_e_t_b_s_d_-_h_e_l_p_@_n_e_t_b_s_d_._o_r_g.
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.
TThhaannkkss ggoo ttoo
++oo The former members of UCB's Computer Systems Research Group, includ-
ing (but not limited to):
Keith Bostic
Ralph Campbell
Mike Karels
Marshall Kirk McKusick
for their ongoing work on BSD systems, support, and encouragement.
++oo Also, our thanks go to:
Mike Hibler
Rick Macklem
Jan-Simon Pendry
Chris Torek
for answering lots of questions, fixing bugs, and doing the various
work they've done.
++oo UC Berkeley's Experimental Computing Facility provided a home for
sun-lamp in the past, people to look after it, and a sense of humor.
Rob Robertson, too, has added his unique sense of humor to things,
and for a long time provided the primary FTP site for NetBSD.
++oo Vixie Enterprises for hosting the NetBSD FTP, SUP, and WWW servers.
++oo Redback Networks, Inc. for hosting the NetBSD mail and GNATS server.
++oo The Helsinki University of Technology in Finland for hosting the
NetBSD CVS server.
++oo The Internet Research Institute in Japan for hosting the server which
runs the CVSweb interface to the NetBSD source tree.
++oo The many organisations that provide NetBSD mirror sites.
++oo Without CVS, this project would be impossible to manage, so our hats
go off to Brian Berliner, Jeff Polk, and the various other people
who've had a hand in making CVS a useful tool.
++oo Dave Burgess _b_u_r_g_e_s_s_@_c_y_n_j_u_t_._i_n_f_o_n_e_t_._n_e_t has been maintaining the
386BSD/NetBSD/FreeBSD FAQ for quite some time, and deserves to be
recognized for it.
++oo The following individuals and organizations (each in alphabetical or-
der) have made donations or loans of hardware and/or money, to sup-
port NetBSD development, and deserve credit for it:
Steve Allen
Jason Birnschein
Mason Loring Bliss
Jason Brazile
Mark Brinicombe
David Brownlee
Simon Burge
Dave Burgess
Ralph Campbell
Brian Carlstrom
James Chacon
Bill Coldwell
Charles Conn
Tom Coulter
Charles D. Cranor
Christopher G. Demetriou
Scott Ellis
Hubert Feyrer
Castor Fu
Greg Gingerich
William Gnadt
Michael Graff
Guenther Grau
Ross Harvey
Charles M. Hannum
Michael L. Hitch
Kenneth Alan Hornstein
Jordan K. Hubbard
S/oren J/orvang
Scott Kaplan
Noah M. Keiserman
Harald Koerfgen
John Kohl
Chris Legrow
Ted Lemon
Norman R. McBride
Neil J. McRae
Perry E. Metzger
Toru Nishimura
Herb Peyerl
Mike Price
Dave Rand
Michael Richardson
Heiko W. Rupp
Brad Salai
Chuck Silvers
Thor Lancelot Simon
Bill Sommerfeld
Paul Southworth
Eric and Rosemary Spahr
Ted Spradley
Kimmo Suominen
Jason R. Thorpe
Steve Wadlow
Krister Walfridsson
Jim Wise
Reinoud Zandijk
Christos Zoulas
AboveNet Communications, Inc.
Advanced System Products, Inc.
Avalon Computer Systems
Bay Area Internet Solutions
Brains Corporation, Japan
Canada Connect Corporation
Co-operative Research Centre for Enterprise Distributed Systems Technology
Demon Internet, UK
Digital Equipment Corporation
Distributed Processing Technology
Easynet, UK
Free Hardware Foundation
Innovation Development Enterprises of America
Internet Software Consortium
MS Macro System GmbH, Germany
Numerical Aerospace Simulation Facility, NASA Ames Research Center
Piermont Information Systems Inc.
Precedence Technologies Ltd
Salient Systems Inc.
VMC Harald Frank, Germany
Warped Communications, Inc.
Whitecross Database Systems Ltd.
(If you're not on that list and should be, tell us! We probably were
not able to get in touch with you, to verify that you wanted to be
listed.)
++oo Finally, we thank all of the people who've put sweat and tears into
developing NetBSD since its inception in January, 1993. (Obviously,
there are a lot more people who deserve thanks here. If you're one of
them, and would like to mentioned, tell us!)
WWee aarree......
(in alphabetical order)
_T_h_e _N_e_t_B_S_D _c_o_r_e _g_r_o_u_p_:
Alistair Crooks _a_g_c_@_n_e_t_b_s_d_._o_r_g
Jun-ichiro itojun Hagino _i_t_o_j_u_n_@_n_e_t_b_s_d_._o_r_g
Frank van der Linden _f_v_d_l_@_n_e_t_b_s_d_._o_r_g
Luke Mewburn _l_u_k_e_m_@_n_e_t_b_s_d_._o_r_g
Christos Zoulas _c_h_r_i_s_t_o_s_@_n_e_t_b_s_d_._o_r_g
_T_h_e _p_o_r_t_m_a_s_t_e_r_s _(_a_n_d _t_h_e_i_r _p_o_r_t_s_)_:
Mark Brinicombe _m_a_r_k_@_n_e_t_b_s_d_._o_r_g aarrmm3322
Simon Burge _s_i_m_o_n_b_@_n_e_t_b_s_d_._o_r_g ppmmaaxx
Simon Burge _s_i_m_o_n_b_@_n_e_t_b_s_d_._o_r_g ssbbmmiippss
Jeremy Cooper _j_e_r_e_m_y_@_n_e_t_b_s_d_._o_r_g ssuunn33xx
Matt Fredette _f_r_e_d_e_t_t_e_@_n_e_t_b_s_d_._o_r_g ssuunn22
Chris Gilbert _c_h_r_i_s_@_n_e_t_b_s_d_._o_r_g ccaattss
Ross Harvey _r_o_s_s_@_n_e_t_b_s_d_._o_r_g aallpphhaa
Jun-ichiro itojun Hagino _i_t_o_j_u_n_@_n_e_t_b_s_d_._o_r_g sshh33
Ben Harris _b_j_h_2_1_@_n_e_t_b_s_d_._o_r_g aaccoorrnn2266
Eduardo Horvath _e_e_h_@_n_e_t_b_s_d_._o_r_g ssppaarrcc6644
Darrin Jewell _d_b_j_@_n_e_t_b_s_d_._o_r_g nneexxtt6688kk
S/oren J/orvang _s_o_r_e_n_@_n_e_t_b_s_d_._o_r_g ccoobbaalltt
S/oren J/orvang _s_o_r_e_n_@_n_e_t_b_s_d_._o_r_g ssggiimmiippss
Wayne Knowles _w_d_k_@_n_e_t_b_s_d_._o_r_g mmiippssccoo
Paul Kranenburg _p_k_@_n_e_t_b_s_d_._o_r_g ssppaarrcc
Anders Magnusson _r_a_g_g_e_@_n_e_t_b_s_d_._o_r_g vvaaxx
Minoura Makoto _m_i_n_o_u_r_a_@_n_e_t_b_s_d_._o_r_g xx6688kk
Phil Nelson _p_h_i_l_@_n_e_t_b_s_d_._o_r_g ppcc553322
Tohru Nishimura _n_i_s_i_m_u_r_a_@_n_e_t_b_s_d_._o_r_g lluunnaa6688kk
NONAKA Kimihiro _n_o_n_a_k_a_@_n_e_t_b_s_d_._o_r_g pprreepp
Scott Reynolds _s_c_o_t_t_r_@_n_e_t_b_s_d_._o_r_g mmaacc6688kk
Kazuki Sakamoto _s_a_k_a_m_o_t_o_@_n_e_t_b_s_d_._o_r_g bbeebbooxx
Noriyuki Soda _s_o_d_a_@_n_e_t_b_s_d_._o_r_g aarrcc
Wolfgang Solfrank _w_s_@_n_e_t_b_s_d_._o_r_g ooffppppcc
Ignatios Souvatzis _i_s_@_n_e_t_b_s_d_._o_r_g aammiiggaa
Jonathan Stone _j_o_n_a_t_h_a_n_@_n_e_t_b_s_d_._o_r_g ppmmaaxx
Shin Takemura _t_a_k_e_m_u_r_a_@_n_e_t_b_s_d_._o_r_g hhppccmmiippss
Jason Thorpe _t_h_o_r_p_e_j_@_n_e_t_b_s_d_._o_r_g aallpphhaa
Jason Thorpe _t_h_o_r_p_e_j_@_n_e_t_b_s_d_._o_r_g hhpp330000
Tsubai Masanari _t_s_u_b_a_i_@_n_e_t_b_s_d_._o_r_g mmaaccppppcc
Tsubai Masanari _t_s_u_b_a_i_@_n_e_t_b_s_d_._o_r_g nneewwssmmiippss
Izumi Tsutsui _t_s_u_t_s_u_i_@_n_e_t_b_s_d_._o_r_g nneewwss6688kk
Frank van der Linden _f_v_d_l_@_n_e_t_b_s_d_._o_r_g ii338866
Leo Weppelman _l_e_o_@_n_e_t_b_s_d_._o_r_g aattaarrii
Nathan Williams _n_a_t_h_a_n_w_@_n_e_t_b_s_d_._o_r_g ssuunn33
Steve Woodford _s_c_w_@_n_e_t_b_s_d_._o_r_g mmvvmmee6688kk
Steve Woodford _s_c_w_@_n_e_t_b_s_d_._o_r_g mmvvmmeeppppcc
Reinoud Zandijk _r_e_i_n_o_u_d_@_n_e_t_b_s_d_._o_r_g aaccoorrnn3322
_T_h_e _N_e_t_B_S_D _1_._5_Z_C _R_e_l_e_a_s_e _E_n_g_i_n_e_e_r_i_n_g _t_e_a_m_:
Chris G. Demetriou _c_g_d_@_n_e_t_b_s_d_._o_r_g
Hoavard Eidnes _h_e_@_n_e_t_b_s_d_._o_r_g
Ted Lemon _m_e_l_l_o_n_@_n_e_t_b_s_d_._o_r_g
Perry Metzger _p_e_r_r_y_@_n_e_t_b_s_d_._o_r_g
Curt Sampson _c_j_s_@_n_e_t_b_s_d_._o_r_g
Jason Thorpe _t_h_o_r_p_e_j_@_n_e_t_b_s_d_._o_r_g
Todd Vierling _t_v_@_n_e_t_b_s_d_._o_r_g
_D_e_v_e_l_o_p_e_r_s _a_n_d _o_t_h_e_r _c_o_n_t_r_i_b_u_t_o_r_s_:
Nathan Ahlstrom _n_r_a_@_N_e_t_B_S_D_._o_r_g
Steve Allen _w_o_r_m_e_y_@_n_e_t_b_s_d_._o_r_g
Julian Assange _p_r_o_f_f_@_n_e_t_b_s_d_._o_r_g
Lennart Augustsson _a_u_g_u_s_t_s_s_@_n_e_t_b_s_d_._o_r_g
Christoph Badura _b_a_d_@_n_e_t_b_s_d_._o_r_g
Bang Jun-Young _j_u_n_y_o_u_n_g_@_n_e_t_b_s_d_._o_r_g
Dieter Baron _d_i_l_l_o_@_n_e_t_b_s_d_._o_r_g
Robert V. Baron _r_v_b_@_n_e_t_b_s_d_._o_r_g
Jason Beegan _j_t_b_@_n_e_t_b_s_d_._o_r_g
Erik Berls _c_y_b_e_r_@_n_e_t_b_s_d_._o_r_g
John Birrell _j_b_@_n_e_t_b_s_d_._o_r_g
Mason Loring Bliss _m_a_s_o_n_@_n_e_t_b_s_d_._o_r_g
Rafal Boni _r_a_f_a_l_@_n_e_t_b_s_d_._o_r_g
Manuel Bouyer _b_o_u_y_e_r_@_n_e_t_b_s_d_._o_r_g
John Brezak _b_r_e_z_a_k_@_n_e_t_b_s_d_._o_r_g
Allen Briggs _b_r_i_g_g_s_@_n_e_t_b_s_d_._o_r_g
Aaron Brown _a_b_r_o_w_n_@_n_e_t_b_s_d_._o_r_g
Andrew Brown _a_t_a_t_a_t_@_n_e_t_b_s_d_._o_r_g
David Brownlee _a_b_s_@_n_e_t_b_s_d_._o_r_g
Frederick Bruckman _f_r_e_d_b_@_n_e_t_b_s_d_._o_r_g
Jon Buller _j_o_n_b_@_n_e_t_b_s_d_._o_r_g
Dave Burgess _b_u_r_g_e_s_s_@_c_y_n_j_u_t_._i_n_f_o_n_e_t_._n_e_t
Robert Byrnes _b_y_r_n_e_s_@_n_e_t_b_s_d_._o_r_g
D'Arcy J.M. Cain _d_a_r_c_y_@_n_e_t_b_s_d_._o_r_g
Dave Carrel _c_a_r_r_e_l_@_n_e_t_b_s_d_._o_r_g
James Chacon _j_m_c_@_n_e_t_b_s_d_._o_r_g
Bill Coldwell _b_i_l_l_c_@_n_e_t_b_s_d_._o_r_g
Julian Coleman _j_d_c_@_n_e_t_b_s_d_._o_r_g
Chuck Cranor _c_h_u_c_k_@_n_e_t_b_s_d_._o_r_g
Aidan Cully _a_i_d_a_n_@_n_e_t_b_s_d_._o_r_g
Johan Danielsson _j_o_d_a_@_n_e_t_b_s_d_._o_r_g
Matt DeBergalis _d_e_b_e_r_g_@_n_e_t_b_s_d_._o_r_g
Rob Deker _d_e_k_e_r_@_n_e_t_b_s_d_._o_r_g
Chris G. Demetriou _c_g_d_@_n_e_t_b_s_d_._o_r_g
Tracy Di Marco White _g_e_n_d_a_l_i_a_@_n_e_t_b_s_d_._o_r_g
Jarom'ir Dolecek _j_d_o_l_e_c_e_k_@_n_e_t_b_s_d_._o_r_g
Andy Doran _a_d_@_n_e_t_b_s_d_._o_r_g
Roland Dowdeswell _e_l_r_i_c_@_n_e_t_b_s_d_._o_r_g
Emmanuel Dreyfus _m_a_n_u_@_n_e_t_b_s_d_._o_r_g
Matthias Drochner _d_r_o_c_h_n_e_r_@_n_e_t_b_s_d_._o_r_g
Jun Ebihara _j_u_n_@_n_e_t_b_s_d_._o_r_g
Hoavard Eidnes _h_e_@_n_e_t_b_s_d_._o_r_g
Stoned Elipot _s_e_b_@_n_e_t_b_s_d_._o_r_g
Enami Tsugutomo _e_n_a_m_i_@_n_e_t_b_s_d_._o_r_g
Bernd Ernesti _v_e_e_g_o_@_n_e_t_b_s_d_._o_r_g
Erik Fair _f_a_i_r_@_n_e_t_b_s_d_._o_r_g
Gavan Fantom _g_a_v_a_n_@_n_e_t_b_s_d_._o_r_g
Hubert Feyrer _h_u_b_e_r_t_f_@_n_e_t_b_s_d_._o_r_g
Jason R. Fink _j_r_f_@_n_e_t_b_s_d_._o_r_g
Thorsten Frueauf _f_r_u_e_a_u_f_@_n_e_t_b_s_d_._o_r_g
Castor Fu _c_a_s_t_o_r_@_n_e_t_b_s_d_._o_r_g
Ichiro Fukuhara _i_c_h_i_r_o_@_n_e_t_b_s_d_._o_r_g
Brian R. Gaeke _b_r_g_@_d_g_a_t_e_._o_r_g
Thomas Gerner _t_h_o_m_a_s_@_n_e_t_b_s_d_._o_r_g
Simon J. Gerraty _s_j_g_@_n_e_t_b_s_d_._o_r_g
Justin Gibbs _g_i_b_b_s_@_n_e_t_b_s_d_._o_r_g
Adam Glass _g_l_a_s_s_@_n_e_t_b_s_d_._o_r_g
Michael Graff _e_x_p_l_o_r_e_r_@_n_e_t_b_s_d_._o_r_g
Brad Grantham _g_r_a_n_t_h_a_m_@_t_e_n_o_n_._c_o_m
Brian C. Grayson _b_g_r_a_y_s_o_n_@_n_e_t_b_s_d_._o_r_g
Matthew Green _m_r_g_@_n_e_t_b_s_d_._o_r_g
Juergen Hannken-Illjes _h_a_n_n_k_e_n_@_n_e_t_b_s_d_._o_r_g
Charles M. Hannum _m_y_c_r_o_f_t_@_n_e_t_b_s_d_._o_r_g
Eric Haszlakiewicz _e_r_h_@_n_e_t_b_s_d_._o_r_g
John Hawkinson _j_h_a_w_k_@_n_e_t_b_s_d_._o_r_g
HAYAKAWA Koichi _h_a_y_a_@_n_e_t_b_s_d_._o_r_g
Ren'e Hexel _r_h_@_n_e_t_b_s_d_._o_r_g
Michael L. Hitch _m_h_i_t_c_h_@_n_e_t_b_s_d_._o_r_g
Christian E. Hopps _c_h_o_p_p_s_@_n_e_t_b_s_d_._o_r_g
Ken Hornstein _k_e_n_h_@_n_e_t_b_s_d_._o_r_g
Marc Horowitz _m_a_r_c_@_n_e_t_b_s_d_._o_r_g
Nick Hudson _s_k_r_l_l_@_n_e_t_b_s_d_._o_r_g
Martin Husemann _m_a_r_t_i_n_@_n_e_t_b_s_d_._o_r_g
Dean Huxley _d_e_a_n_@_n_e_t_b_s_d_._o_r_g
Bernardo Innocenti _b_e_r_n_i_e_@_n_e_t_b_s_d_._o_r_g
Tetsuya Isaki _i_s_a_k_i_@_n_e_t_b_s_d_._o_r_g
ITOH Yasufumi _i_t_o_h_y_@_n_e_t_b_s_d_._o_r_g
IWAMOTO Toshihiro _t_o_s_h_i_i_@_n_e_t_b_s_d_._o_r_g
Matthew Jacob _m_j_a_c_o_b_@_n_e_t_b_s_d_._o_r_g
Lonhyn T. Jasinskyj _l_o_n_h_y_n_@_n_e_t_b_s_d_._o_r_g
Chris Jones _c_j_o_n_e_s_@_n_e_t_b_s_d_._o_r_g
Takahiro Kambe _t_a_c_a_@_n_e_t_b_s_d_._o_r_g
Antti Kantee _p_o_o_k_a_@_n_e_t_b_s_d_._o_r_g
Masanori Kanaoka _k_a_n_a_o_k_a_@_n_e_t_b_s_d_._o_r_g
KAWAMOTO Yosihisa _k_a_w_a_m_o_t_o_@_n_e_t_b_s_d_._o_r_g
Mario Kemper _m_a_g_i_c_k_@_n_e_t_b_s_d_._o_r_g
Lawrence Kesteloot _k_e_s_t_e_l_o_o_@_c_s_._u_n_c_._e_d_u
Thomas Klausner _w_i_z_@_n_e_t_b_s_d_._o_r_g
Klaus Klein _k_l_e_i_n_k_@_n_e_t_b_s_d_._o_r_g
Wayne Knowles _w_d_k_@_n_e_t_b_s_d_._o_r_g
John Kohl _j_t_k_@_n_e_t_b_s_d_._o_r_g
Martti Kuparinen _m_a_r_t_t_i_@_n_e_t_b_s_d_._o_r_g
Kevin Lahey _k_m_l_@_n_e_t_b_s_d_._o_r_g
Johnny C. Lam _j_l_a_m_@_n_e_t_b_s_d_._o_r_g
Martin J. Laubach _m_j_l_@_n_e_t_b_s_d_._o_r_g
Ted Lemon _m_e_l_l_o_n_@_n_e_t_b_s_d_._o_r_g
Joel Lindholm _j_o_e_l_@_n_e_t_b_s_d_._o_r_g
Mike Long _m_i_k_e_l_@_n_e_t_b_s_d_._o_r_g
Warner Losh _i_m_p_@_n_e_t_b_s_d_._o_r_g
Tomasz Luchowski _z_u_n_t_u_m_@_n_e_t_b_s_d_._o_r_g
Federico Lupi _f_e_d_e_r_i_c_o_@_n_e_t_b_s_d_._o_r_g
Brett Lymn _b_l_y_m_n_@_n_e_t_b_s_d_._o_r_g
Paul Mackerras _p_a_u_l_u_s_@_n_e_t_b_s_d_._o_r_g
MAEKAWA Masahide _g_e_h_e_n_n_a_@_n_e_t_b_s_d_._o_r_g
David Maxwell _d_a_v_i_d_@_n_e_t_b_s_d_._o_r_g
Dan McMahill _d_m_c_m_a_h_i_l_l_@_n_e_t_b_s_d_._o_r_g
Gregory McGarry _g_m_c_g_a_r_r_y_@_n_e_t_b_s_d_._o_r_g
Jared D. McNeill _j_m_c_n_e_i_l_l_@_n_e_t_b_s_d_._o_r_g
Neil J. McRae _n_e_i_l_@_n_e_t_b_s_d_._o_r_g
Perry Metzger _p_e_r_r_y_@_n_e_t_b_s_d_._o_r_g
der Mouse _m_o_u_s_e_@_n_e_t_b_s_d_._o_r_g
Joseph Myers _j_s_m_@_n_e_t_b_s_d_._o_r_g
Ken Nakata _k_e_n_n_@_n_e_t_b_s_d_._o_r_g
Bob Nestor _r_n_e_s_t_o_r_@_n_e_t_b_s_d_._o_r_g
NISHIMURA Takeshi _n_s_m_r_t_k_s_@_n_e_t_b_s_d_._o_r_g
NONAKA Kimihiro _n_o_n_a_k_a_@_n_e_t_b_s_d_._o_r_g
Jesse Off _j_o_f_f_@_n_e_t_b_s_d_._o_r_g
Tatoku Ogaito _t_a_c_h_a_@_n_e_t_b_s_d_._o_r_g
Masaru Oki _o_k_i_@_n_e_t_b_s_d_._o_r_g
Atsushi Onoe _o_n_o_e_@_n_e_t_b_s_d_._o_r_g
Greg Oster _o_s_t_e_r_@_n_e_t_b_s_d_._o_r_g
Herb Peyerl _h_p_e_y_e_r_l_@_n_e_t_b_s_d_._o_r_g
Matthias Pfaller _m_a_t_t_h_i_a_s_@_n_e_t_b_s_d_._o_r_g
Chris Pinnock _c_j_e_p_@_n_e_t_b_s_d_._o_r_g
Dante Profeta _d_a_n_t_e_@_n_e_t_b_s_d_._o_r_g
Chris Provenzano _p_r_o_v_e_n_@_n_e_t_b_s_d_._o_r_g
Michael Rauch _m_r_a_u_c_h_@_n_e_t_b_s_d_._o_r_g
Waldi Ravens _w_a_l_d_i_@_m_o_a_c_s_._i_n_d_i_v_._n_l_._n_e_t
Darren Reed _d_a_r_r_e_n_r_@_n_e_t_b_s_d_._o_r_g
Michael Richardson _m_c_r_@_n_e_t_b_s_d_._o_r_g
Tim Rightnour _g_a_r_b_l_e_d_@_n_e_t_b_s_d_._o_r_g
Gordon Ross _g_w_r_@_n_e_t_b_s_d_._o_r_g
Heiko W. Rupp _h_w_r_@_n_e_t_b_s_d_._o_r_g
David Sainty _d_s_a_i_n_t_y_@_n_e_t_b_s_d_._o_r_g
SAITOH Masanobu _m_s_a_i_t_o_h_@_n_e_t_b_s_d_._o_r_g
Curt Sampson _c_j_s_@_n_e_t_b_s_d_._o_r_g
Wilfredo Sanchez _w_s_a_n_c_h_e_z_@_n_e_t_b_s_d_._o_r_g
Ty Sarna _t_s_a_r_n_a_@_n_e_t_b_s_d_._o_r_g
SATO Kazumi _s_a_t_o_@_n_e_t_b_s_d_._o_r_g
Matthias Scheler _t_r_o_n_@_n_e_t_b_s_d_._o_r_g
Karl Schilke (rAT) _r_a_t_@_n_e_t_b_s_d_._o_r_g
Konrad Schroder _p_e_r_s_e_a_n_t_@_n_e_t_b_s_d_._o_r_g
Reed Shadgett _d_e_n_t_@_n_e_t_b_s_d_._o_r_g
Tim Shepard _s_h_e_p_@_n_e_t_b_s_d_._o_r_g
Takeshi Shibagaki _s_h_i_b_a_@_n_e_t_b_s_d_._o_r_g
Takao Shinohara _s_h_i_n_@_n_e_t_b_s_d_._o_r_g
Takuya SHIOZAKI _t_s_h_i_o_z_a_k_@_n_e_t_b_s_d_._o_r_g
Chuck Silvers _c_h_s_@_n_e_t_b_s_d_._o_r_g
Thor Lancelot Simon _t_l_s_@_n_e_t_b_s_d_._o_r_g
Jeff Smith _j_e_f_f_s_@_n_e_t_b_s_d_._o_r_g
SOMEYA Yoshihiko _s_o_m_e_y_a_@_n_e_t_b_s_d_._o_r_g
Bill Sommerfeld _s_o_m_m_e_r_f_e_l_d_@_n_e_t_b_s_d_._o_r_g
Bill Squier _g_r_o_o_@_n_e_t_b_s_d_._o_r_g
Bill Studenmund _w_r_s_t_u_d_e_n_@_n_e_t_b_s_d_._o_r_g
Kevin Sullivan _s_u_l_l_i_v_a_n_@_n_e_t_b_s_d_._o_r_g
SUNAGAWA Keiki _k_e_i_@_n_e_t_b_s_d_._o_r_g
Kimmo Suominen _k_i_m_@_n_e_t_b_s_d_._o_r_g
TAMURA Kent _k_e_n_t_@_n_e_t_b_s_d_._o_r_g
Shin'ichiro TAYA _t_a_y_a_@_n_e_t_b_s_d_._o_r_g
Matt Thomas _m_a_t_t_@_n_e_t_b_s_d_._o_r_g
Christoph Toshok _t_o_s_h_o_k_@_n_e_t_b_s_d_._o_r_g
UCHIYAMA Yasushi _u_c_h_@_n_e_t_b_s_d_._o_r_g
Masao Uebayashi _u_e_b_a_y_a_s_i_@_n_e_t_b_s_d_._o_r_g
Shuichiro URATA _u_r_@_n_e_t_b_s_d_._o_r_g
Todd Vierling _t_v_@_n_e_t_b_s_d_._o_r_g
Aymeric Vincent _a_y_m_e_r_i_c_@_n_e_t_b_s_d_._o_r_g
Paul Vixie _v_i_x_i_e_@_n_e_t_b_s_d_._o_r_g
Krister Walfridsson _k_r_i_s_t_e_r_w_@_n_e_t_b_s_d_._o_r_g
Lex Wennmacher _w_e_n_n_m_a_c_h_@_n_e_t_b_s_d_._o_r_g
Assar Westerlund _a_s_s_a_r_@_n_e_t_b_s_d_._o_r_g
Todd Whitesel _t_o_d_d_p_w_@_n_e_t_b_s_d_._o_r_g
Rob Windsor _w_i_n_d_s_o_r_@_n_e_t_b_s_d_._o_r_g
Dan Winship _d_a_n_w_@_n_e_t_b_s_d_._o_r_g
Jim Wise _j_w_i_s_e_@_n_e_t_b_s_d_._o_r_g
Michael Wolfson _m_b_w_@_n_e_t_b_s_d_._o_r_g
Colin Wood _e_n_d_e_r_@_n_e_t_b_s_d_._o_r_g
YAMAMOTO Takashi _y_a_m_t_@_n_e_t_b_s_d_._o_r_g
Yuji Yamano _y_y_a_m_a_n_o_@_n_e_t_b_s_d_._o_r_g
Maria Zevenhoven _m_a_r_i_a_7_@_n_e_t_b_s_d_._o_r_g
LLeeggaall MMuummbboo--JJuummbboo
All product names mentioned herein are trademarks or registered trade-
marks of their respective owners.
The following notices are required to satisfy the license terms of the
software that we have mentioned in this document:
This product includes software developed by the University of California,
Berkeley and its contributors. This product includes software developed
by The NetBSD Foundation, Inc. This product includes software developed
by the NetBSD Foundation, Inc. and its contributors. This product in-
cludes software developed by the Computer Systems Engineering Group at
Lawrence Berkeley Laboratory. This product includes software developed
by Adam Glass and Charles Hannum. This product includes software devel-
oped by Adam Glass and Charles M. Hannum. This product includes software
developed by Adam Glass. This product includes software developed by Al-
istair G. Crooks. This product includes software developed by Amancio
Hasty and Roger Hardiman. This product includes software developed by
Berkeley Software Design, Inc. This product includes software developed
by Bill Paul. This product includes software developed by Charles D.
Cranor and Washington University. This product includes software devel-
oped by Charles D. Cranor. This product includes software developed by
Charles Hannum, by the University of Vermont and State Agricultural Col-
lege and Garrett A. Wollman, by William F. Jolitz, and by the University
of California, Berkeley, Lawrence Berkeley Laboratory, and its contribu-
tors. This product includes software developed by Charles Hannum. This
product includes software developed by Charles M. Hannum. This product
includes software developed by Chris Provenzano. This product includes
software developed by Christian E. Hopps. This product includes software
developed by Christopher G. Demetriou for the NetBSD Project. This prod-
uct includes software developed by Christopher G. Demetriou. This prod-
uct includes software developed by Christos Zoulas. This product in-
cludes software developed by David Jones and Gordon Ross. This product
includes software developed by Dean Huxley. This product includes soft-
ware developed by Eric S. Hvozda. This product includes software devel-
oped by Ezra Story. This product includes software developed by Gardner
Buchanan. This product includes software developed by Gordon Ross. This
product includes software developed by Gordon W. Ross and Leo Weppelman.
This product includes software developed by Gordon W. Ross. This product
includes software developed by Hauke Fath. This product includes soft-
ware developed by HAYAKAWA Koichi. This product includes software devel-
oped by Hellmuth Michaelis and Joerg Wunsch. This product includes soft-
ware developed by Herb Peyerl. This product includes software developed
by Holger Veit and Brian Moore for use with "386BSD" and similar operat-
ing systems. This product includes software developed by Hubert Feyrer
for the NetBSD Project. This product includes software developed by Iain
Hibbert. This product includes software developed by Ian W. Dall. This
product includes software developed by Ignatios Souvatzis for the NetBSD
Project. This product includes software developed by Jason R. Thorpe for
And Communications,
http://www.and.com/. This product includes software
developed by Joachim Koenig-Baltes. This product includes software de-
veloped by Jochen Pohl for The NetBSD Project. This product includes
software developed by John Polstra. This product includes software de-
veloped by Jonathan Stone and Jason R. Thorpe for the NetBSD Project.
This product includes software developed by Jonathan Stone for the NetBSD
Project. This product includes software developed by Jonathan Stone.
This product includes software developed by Julian Highfield. This prod-
uct includes software developed by Kenneth Stailey. This product in-
cludes software developed by Leo Weppelman. This product includes soft-
ware developed by Lloyd Parkes. This product includes software developed
by Manuel Bouyer. This product includes software developed by Marc
Horowitz. This product includes software developed by Mark Brinicombe
for the NetBSD Project. This product includes software developed by Mark
Brinicombe. This product includes software developed by Mark Tinguely
and Jim Lowe. This product includes software developed by Markus Wild.
This product includes software developed by Martin Husemann and Wolfgang
Solfrank. This product includes software developed by Mats O Jansson and
Charles D. Cranor. This product includes software developed by Mats O
Jansson. This product includes software developed by Matthias Pfaller.
This product includes software developed by Michael L. Hitch. This prod-
uct includes software developed by Niels Provos. This product includes
software developed by Paul Kranenburg. This product includes software
developed by Paul Mackerras. This product includes software developed by
Peter Galbavy. This product includes software developed by Philip A.
Nelson. This product includes software developed by Rodney W. Grimes.
This product includes software developed by Roland C. Dowdeswell. This
product includes software developed by Rolf Grossmann. This product in-
cludes software developed by Scott Bartram. This product includes soft-
ware developed by SigmaSoft, Th. Lockert. This product includes software
developed by Tatoku Ogaito for the NetBSD Project. This product includes
software developed by Terrence R. Lambert. This product includes soft-
ware developed by Theo de Raadt and John Brezak. This product includes
software developed by Theo de Raadt. This product includes software de-
veloped by Tohru Nishimura for the NetBSD Project. This product includes
software developed by TooLs GmbH. This product includes software de-
signed by William Allen Simpson. This product includes software devel-
oped by Winning Strategies, Inc. This product includes software devel-
oped by Zembu Labs, Inc. This product includes software developed by the
Center for Software Science at the University of Utah. This product in-
cludes software developed by the Computer Systems Laboratory at the Uni-
versity of Utah. This product includes software developed by the Univer-
sity of Calgary Department of Computer Science and its contributors.
This product includes software developed by the University of Vermont and
State Agricultural College and Garrett A. Wollman. This product includes
software developed for the FreeBSD project. This product includes soft-
ware developed for the Internet Software Consortium by Ted Lemon. This
product includes software developed for the NetBSD Project by Frank van
der Linden. This product includes software developed for the NetBSD Pro-
ject by Jason R. Thorpe. This product includes software developed for
the NetBSD Project by John M. Vinopal. This product includes software
developed for the NetBSD Project by Matthias Drochner. This product in-
cludes software developed for the NetBSD Project by Matthieu Herrb. This
product includes software developed for the NetBSD Project by Perry E.
Metzger. This product includes software developed for the NetBSD Project
by Piermont Information Systems Inc. This product includes software de-
veloped for the NetBSD Project by Ted Lemon. This product includes soft-
ware developed for the NetBSD Project by Wasabi Systems, Inc. This prod-
uct includes software developed by LAN Media Corporation and its contrib-
utors. This product includes software developed by Michael Graff for the
NetBSD Project. This product includes software developed by Niklas Hal-
lqvist, C Stone and Job de Haas. This product includes software devel-
oped by Eric Young (
[email protected]). This product includes software
developed by the OpenSSL Project for use in the OpenSSL Toolkit
(
http://www.openssl.org/). This product includes software developed by
the University of Oregon. This product includes software developed by
the University of Southern California and/or Information Sciences Insti-
tute. This product includes software developed by Internet Initiative
Japan Inc. This product includes software developed by Reinoud Zandijk.
This product includes software developed at the Information Technology
Division, US Naval Research Laboratory.
This product includes software developed by Advanced Risc Machines Ltd.
This product includes software developed by Neil Carson.
This product includes software developed by the RiscBSD kernel team.
This product includes software developed by Scott Stevens.
TThhee EEnndd
NetBSD May 21, 2001 32
