About this Document............................................2
What is NetBSD?................................................2
Changes Between The NetBSD 2.0 and 2.1 Releases................3
Kernel......................................................3
Networking..................................................4
File system.................................................4
Security....................................................4
System administration and user tools........................4
Miscellaneous...............................................5
alpha specific..............................................5
Changes Between The NetBSD 1.6 and 2.0 Releases................5
Kernel......................................................5
Networking..................................................6
File system.................................................6
Security....................................................6
System administration and user tools........................7
Miscellaneous...............................................7
Important notes about NetBSD 2.1...............................7
The Future of NetBSD...........................................8
Sources of NetBSD..............................................8
NetBSD 2.1 Release Contents....................................8
NetBSD/alpha subdirectory structure........................10
Bootable installation/upgrade floppies.....................10
Binary distribution sets...................................11
NetBSD/alpha System Requirements and Supported Devices........12
Supported PCI bus devices..................................12
Supported ISA bus devices..................................13
Supported EISA bus devices.................................13
Supported Turbochannel bus devices.........................13
Getting the NetBSD System on to Useful Media..................15
Preparing your System for NetBSD installation.................17
Installing the NetBSD System..................................17
Running the sysinst installation program...................21
Introduction............................................21
Possible PCMCIA issues..................................21
General.................................................21
Quick install...........................................21
Booting NetBSD..........................................23
Network configuration...................................23
Installation drive selection and parameters.............23
Partitioning the disk...................................24
Preparing your hard disk................................24
Getting the distribution sets...........................25
Installation using ftp..................................25
Installation using NFS..................................25
Installation from CD-ROM................................25
Installation from an unmounted file system..............26
Installation from a local directory.....................26
Extracting the distribution sets........................26
Finalizing your installation............................26
Manual and script-assisted installation....................26
Post installation steps.......................................30
Upgrading a previously-installed NetBSD System................33
Compatibility Issues With Previous NetBSD Releases............33
Issues affecting an upgrade from NetBSD 1.6................33
Using online NetBSD documentation.............................34
Administrivia.................................................34
Thanks go to..................................................35
We are........................................................37
Legal Mumbo-Jumbo.............................................43
The End.......................................................48
This document describes the installation procedure for
NetBSD2.1
on the
alpha
platform.
It is available in four different formats titled
INSTALL.ext,
where
.ext
is one of
.ps, .html, .more,
or .txt:
.ps.html.moremore(1)
and
less(1)
pager utility programs.
This is the format in which the on-line
man
pages are generally presented.
.txtYou are reading the HTML version.
The NetBSD Operating System is a fully functional Open Source UNIX-like operating system derived from the University of California, Berkeley Networking Release 2 (Net/2), 4.4BSD-Lite, and 4.4BSD-Lite2 sources. NetBSD runs on fifty four different system architectures (ports), featuring seventeen machine architectures across fifteen distinct CPU families, and is being ported to more. The NetBSD2.1 release contains complete binary releases for many different system architectures. (A few ports are not fully supported at this time and are thus not part of the binary distribution. For information on them, please see the NetBSD web site at http://www.NetBSD.org/.)
NetBSD is a completely integrated system. In addition to its highly portable, high performance kernel, NetBSD features a complete set of user utilities, compilers for several languages, the X Window System, firewall software and numerous other tools, all accompanied by full source code.
NetBSD is a creation of the members of the Internet community. Without the unique cooperation and coordination the net makes possible, it's likely that NetBSD wouldn't exist.
The NetBSD2.1 release is the first functional update release of the NetBSD2 release branch. This provides numerous functional enhancements, including support for many new devices, hundreds of bug fixes, patches and updates to kernel subsystems, and many enhancements to the user environment. In addition, all of the security fixes and critical bug fixes from the NetBSD2.0.3 update are included as well. 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 all the changes that have gone in over the over nine months since the release of NetBSD2.0. Some highlights include:
ata(4)
and
wdc(4)
drives now only downgrade modes due to actual CRC errors, and UDMA modes
are downgraded more slowly.
pdcsata(4)
driver was added, with support for the Promise SATA150 series of
controllers, including RAID support.
esiop(4)
driver.
aac(4)
driver.
ahd(4)
driver.
ehci(4)
driver.
ukyopon(4)
: Kyocera AIR-EDGE phone driver.
wdc(4)
driver has been fixed for commands with opaque data structures.
atactl smart status
now works on big-endian hosts.
wm(4)
fixed major performance issues with the i82547 Gig-E chip.
sk(4)
improved chip identification and improved performance, and added support
for the Belkin Gigabit Desktop Network PCI card.
vlan(4)
interfaces.
rtk(4)
and
tl(4)
interfaces as
rnd(4)
sources.
tl(4)
driver.
stf(4)
interface.
gre(4)
interfaces.
hme(4)
driver now supports Sun QFE boards on non-sparc hardware.
stge(4)
Fix some bigendian issues, and some other issues. Now works on sparc64
with hardware checksums.
krb5(3)
Support changing passwords in a Windows 2000 (or later) domain.
cgd(4)
key destruction on unconfigure
ntpd(8)
coredump if local system and NTP server did not have overlapping protocol
family support (IPv4 vs. IPv6, for example) fixed.
pax(1)
has a number of bugfixes and new features.
ifwatchd(8)
has been fixed to call the CARRIER script if a link is already up
during the initial interface scan.
grep(1)
on empty or very large files.
gzip(1)
umass(4)
devices after boot.
There have been many alpha-specific enhancements since the NetBSD1.5 release. These include:
NetBSD 2.1 on alpha is, as usual, also fully backward compatible with old NetBSD/alpha binaries, so you don't need to recompile all your local programs.
The NetBSD2.0 release provides numerous significant functional enhancements, including support for many new devices, integration of hundreds of bug fixes, new and updated kernel subsystems, and many user-land enhancements. The result of these improvements is a stable operating system fit for production use that rivals most commercially available systems.
It is impossible to completely summarize over two years of development that went into the NetBSD2.1 release. Some highlights include:
sysctl(9)
was switched from a static binding to a dynamic implementation.
satalink(4)
and move SATA support from other controllers into this along with adding support
for new controllers.
ipf(8)
has been upgraded to version 4.1.3.
tcp(4)
now implements path MTU discovery blackhole detection (i.e. it will turn off
path MTU discovery if the connection is losing).
wi(4)
has support for Host-AP mode, allowing Intersil Prism2/2.5/3-based boards to
be used to make an 802.11 Access Point.
ipf(8)
has been added to
bridge(4)
and
brconfig(8)
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.
In order to retain the functionality that a newly installed system can send mail ``out of the box'', the default has changed so that sendmail will now start by default, and listen for host-local connections.
If this behaviour is not desired, you can either
/etc/rc.conf,
/etc/mail/submit.cf
to point to another host,
/etc/mailer.conf
to point to something else than sendmail, or
/etc/mail/submit.cf,
and set the sendmail_suid variable to ``YES'' in
/etc/rc.conf.
The NetBSD Foundation has been incorporated as a non-profit organization. Its purpose is to encourage, foster and promote the free exchange of computer software, namely the NetBSD Operating System. The foundation will allow for many things to be handled more smoothly than could be done with our previous informal organization. In particular, it provides the framework to deal with other parties that wish to become involved in the NetBSD Project.
The NetBSD Foundation will help improve the quality of NetBSD by:
We intend to begin narrowing the time delay between releases. Our ambition is to provide a full release every six to eight months.
We hope to support even more hardware in the future, and we have a rather large number of other ideas about what can be done to improve NetBSD.
We intend to continue our current practice of making the NetBSD-current development source available on a daily basis.
We intend to integrate free, positive changes from whatever sources submit them, providing that they are well thought-out and increase the usability of the system.
Above all, we hope to create a stable and accessible system, and to be
responsive to the needs and desires of
NetBSD
users, because it is for
and because of them that
NetBSD
exists.
Refer to
http://www.NetBSD.org/mirrors/.
The root directory of the NetBSD2.1 release is organized as follows:
.../NetBSD-2.1/
CHANGESLAST_MINUTEMIRRORSREADME.filesTODOpatches/source/In addition to the files and directories listed above, there is one directory per architecture, for each of the architectures for which NetBSD2.1 has a binary distribution.
The source distribution sets can be found in subdirectories of the
source
subdirectory of the distribution tree.
They contain the complete sources to the system.
The source distribution sets are as follows:
config(8);
and
dbsym(8).
All the above source sets are located in the
source/sets
subdirectory of the distribution tree.
The source sets are distributed as compressed tar files.
Except for the
pkgsrc
set, which is traditionally unpacked into
/usr/pkgsrc,
all sets may be unpacked into
/usr/src
with the command:
#( cd / ; tar -zxpf - ) < set_name.tgz
In each of the source distribution set directories, there are files which contain the checksums of the files in the directory:
BSDSUMCKSUMMD5SYSVSUMThe MD5 digest is the safest checksum, followed by the POSIX checksum. The other two checksums are provided only to ensure that the widest possible range of system can check the integrity of the release files.
alpha
subdirectory of the distribution:
.../NetBSD-2.1/alpha/.
It contains the following files and directories:
INSTALL.htmlINSTALL.psINSTALL.txtINSTALL.more.more
file contains underlined text using the
more(1)
conventions for indicating italic and bold display.
binary/kernel/netbsd-GENERIC.gzsets/installation/floppy/diskimage/tapeimage/cdhdtape
is included for the case where the installer is written to
a CD, hard drive, or tape.
This image file is the same for the CD, HD, and tape cases, but a separate
tapeimage/
directory exists to hold a copy of the
README
file and to meet the
NetBSD
release(7)
standard.
instkernel/netbsd.gz
installation kernel; this is the same installer kernel as in all the
other install
images, but without the various boot program and file system wrappers.
It can be netbooted or diskbooted from a previous installation.
no need to
gunzip
this image.
misc/GENERIC.fs,
a
GENERIC
kernel in a bootable file system image.
This is used in some unusual installations as described in the next section.
There are three bootable images in the
NetBSD
alpha distribution.
One is for a dual-floppy boot and is split into two separate files.
The other is a single-file image containing the same install kernel,
but intended to be written to a CD, tape, or hard drive.
The third image is a
GENERIC
kernel intended for production use in unusual cases.
This can be useful at some sites when:
siop(4)
or
isp(4)
SCSI devices, and on most platforms will not
boot from an IDE drive.
NetBSD
will happily operate
with almost any SCSI root or an IDE root; the solution here is to netboot
a kernel or always boot from floppy.
alpha/binary/sets
subdirectory
of the
NetBSD2.1
distribution tree, and are as follows:
/usr/include)
and the various system libraries (except the shared
libraries, which are included as part of the
base
set).
This set also includes the manual pages for
all of the utilities it contains, as well as the
system call and library manual pages.
/etc
and in several other places.
This set
must
be installed if you are installing the system from scratch, but should
not
be used if you are upgrading.
GENERIC
kernel, named
/netbsd.
You
must
install this distribution set.
/usr/share.
groff(1),
all related programs, and their manual pages.
NetBSD maintains its own set of sources for the X Window System in order to assure tight integration and compatibility. These sources are based on XFree86, and tightly track XFree86 releases. They are currently equivalent to XFree86 4.4.0. Binary sets for the X Window System are distributed with NetBSD. The sets are:
The alpha binary distribution sets are distributed as gzipped tar files
named with the extension
.tgz,
e.g.
base.tgz.
The instructions given for extracting the source sets work equally
well for the binary sets, but it is worth noting that if you use that
method, the filenames stored in the sets are relative and therefore
the files are extracted
below the current directory.
Therefore, if you want to extract the binaries into your system, i.e.
replace the system binaries with them, you have to run the
tar -xpf
command from the root directory (
/
) of your system.
This utility is used only in a Traditional method installation.
NetBSD/alpha 2.1 runs on most of the DEC Alpha PCI platforms, on all of the TURBOChannel models, on the high end 8200 and 8400 systems, and on the 4100 series.
The SRM console is required.
This
console can be distinguished from the ARC console (which is used to
boot
Windows NT)
by the fact that it has a command line interface,
rather than a menu-driven interface.
The SRM prompt is
`>>>'.
Some platforms have both the SRM console and the ARC console, and can switch between them, and other platforms have only one type of console loaded at any one time. If your system comes up with the ARC firmware, it may be possible to switch it to SRM with a menu or to download SRM from ftp://gatekeeper.dec.com/pub/Digital/Alpha/firmware/index.html. You may want to buy a firmware update CD from Compaq Computer Corporation.
More information on supported platforms and devices can be found on the alpha port web pages at http://www.NetBSD.org/.
A basic system will fit on a 200 MB disk (including swap) without too much difficulty, but you will probably want at least 500 MB of disk to have any level of comfort.
Although it is actually possible to boot and install NetBSD/alpha in only 16 MB of RAM, you will want to have at least 32 MB. We support add-in devices on the PCI, ISA, EISA and TurboChannel buses. Because NetBSD has an extremely machine-independent device driver system, many device drivers are the same as used in other ports that use the same bus. For example, the de network card driver is shared by the i386 and alpha ports. Some drivers on inspection appear as if they will work on the alpha but have not been tested because that hardware was not available to NetBSD testers; these are marked as UNTESTED below. If you have one of these devices, and it does work, please get in touch with port-alpha-maintainer@NetBSD.org and let us know that it works. If it doesn't work, do the same thing and we can probably fix it pretty easily.
Note that some devices, especially ISA-based devices, have to have
certain settings set properly for the install and
Parallel ports lpt0 0x378 7 [interrupt-driven or polling]
lpt1 0x278 [polling only]
lpt2 0x3bc [polling only]
AHA-174x SCSI host adapters (in enhanced mode)
ahb0 any any any
AHA-2X4X or AIC-7xxx-based SCSI host adapters
ahc0 any any any
Bus Logic BT445, BT74x, or BT9xx SCSI host adapters
bha0 0x330 any any
bha1 0x334 any any
MFM/ESDI/IDE/RLL hard disk controllers
wdc0 0x1f0 14 [supports two devices]
wdc1 0x170 15 [supports two devices]
ATA disks wd0, wd1, ...
SCSI disks sd0, sd1, ...
SCSI tapes st0, st1, ...
SCSI and ATAPI CD-ROMs cd0, cd1, ...
For each SCSI and IDE controller found, the SCSI or ATA(PI) devices
present on the bus are probed in increasing ID order for SCSI and
master/slave order for ATA(PI).
So the first SCSI drive found will be called sd0, the second sd1,
and so on ...
3COM 3x59X or 3COM 3x90X PCI Ethernet boards
ep0 any any [you must assign an interrupt in your
PCI BIOS, or let it do so for you]
Intel EtherExpress 100 Fast Ethernet adapters
fxp0 any any [you must assign an interrupt in your
PCI BIOS, or let it do so for you]
DEC DE200,201,202 EtherWORKS II/Turbo ISA Ethernet boards
le? 0x3005memory at D0000-DFFFF
le? 0x20010memory at D8000-DFFFF
You should enter the following SRM console command to enable the
le device:
>>> isacfg -mk -slot ? -dev 0 -handle DE200-LE -irq0 5
-membase0 d0000 -memlen0 10000 -iobase0 300 -etyp 1 -enadev 1
DEC DE203,204,205 EtherWORKS III ISA Ethernet boards
lc0 0x300any
lc1 0x320any
You should enter the following SRM console command to enable
the device:
>>> add_de205
GENERIC
kernels to detect them.
(Once installed, you can always rebuild your own kernel
to detect them anywhere you wish, of course.)
Here is a list of such devices and the necessary settings:
Device Name Port IRQ DRQ Misc
------ ---- ---- --- --- ----
Serial ports com0 0x3f8 4 [8250/16450/16550/clones]
com1 0x2f8 3 [8250/16450/16550/clones]
com2 0x3e8 5 [8250/16450/16550/clones]
Note that if you are installing or upgrading from a writable media, the media can be write-protected if you wish. These systems mount a root image from inside the kernel, and will not need to write to the media. If you booted from a floppy, the floppy disk may be removed from the drive after the system has booted.
Installation is supported from several media types, including:
The steps necessary to prepare the distribution sets for installation depend upon which installation medium you choose. The steps for the various media are outlined below.
binary/sets
and
alpha/binary/sets.
Proceed to the instruction on installation.
split(1)
command, running e.g.
split -b 235k base.tgz base.
to split the
base.tgz
file from
alpha/binary/sets
into files named
base.aa,
base.ab,
and so on. Repeat this for all
set_name.tgz
files, splitting them into
set_name.xx
files.
Count the number of
set_name.xx
files that make up the
distribution sets you want to install or upgrade.
You will need one sixth that number of 1.44 MB floppies.
Format all of the floppies with
MS-DOS.
Do
not
make any of them bootable
MS-DOS
floppies, i.e. don't use
format /s
to format them.
(If the floppies are bootable, then the
MS-DOS
system files that make them bootable will take up some space, and you
won't be able to fit the distribution set parts on the disks.)
If you're using floppies that are formatted for
MS-DOS
by their manufacturers, they probably aren't bootable, and you can use
them out of the box.
Place all of the
set_name.xx
files on the
MS-DOS
disks.
Once you have the files on MS-DOS disks, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading.
204.152.184.75
and the IPv6 address is
2001:4f8:4:7:2e0:81ff:fe21:6563
(as of June, 2004).
Once you have this information, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading.
/etc/exports
file on of the NFS server and resetting its mount daemon (mountd).
(Both of these actions will probably require superuser
privileges on the server.)
You need to know the numeric IP address of the NFS server, and, if you don't have DHCP available on your network and the server is not on a network directly connected to the machine on which you're installing or upgrading NetBSD, you need to know the numeric IP address of the router closest to the NetBSD machine. Finally, you need to know the numeric IP address of the NetBSD machine itself.
Once the NFS server is set up properly and you have the information mentioned above, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading.
If you're making the tape on a UNIX-like system, the easiest way to do so is probably something like:
# tar -cf tape_device dist_directories
where
tape_device
is the name of the tape device that
describes the tape drive you're using; possibly
/dev/rst0,
or something similar, but it will vary from system to system.
(If you can't figure it out, ask your system administrator.)
In the above example,
dist_directories
are the
distribution sets' directories, for the distribution sets you
wish to place on the tape.
For instance, to put the
misc, base, and etc
distributions on tape (in
order to do the absolute minimum installation to a new disk),
you would do the following:
# cd .../NetBSD-2.1
# cd alpha/binary
# tar -cf tape_device misc etc kern
Once you have the files on the tape, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading.
If you have any data on your disks that you want to keep,
back it up
before starting.
Note that
NetBSD/alpha
does not support booting more than
one operating system from a single disk, although it's fine to have
multiple operating systems on your machine if you have a separate
disk for
NetBSD,
or if one of them uses a network boot.
Installation of NetBSD/alpha is now easier than ever! For the latest news, problem reports, and discussion, join the port-alpha mailing list by mailing a line saying
subscribe port-alpha
to majordomo@NetBSD.org. Also, see http://www.NetBSD.org/ for more information.
If you encounter any problems, please report them via the mailing list or the
send-pr(1)
program so that they can be fixed for the next release.
To install or upgrade NetBSD, you need to first boot an installation program and then interact with the screen-menu program sysinst. The installation program actually consists of the NetBSD kernel plus an in-memory file system of utility programs.
The usual procedure is to write the installation system to a floppy disk set and then boot from the floppies, however, there are now six ways to boot the NetBSD/alpha installation system! Each approach loads the exact same installation bits. The six paths are:
In all cases, you need to transfer a
bootable image of the installation system
from the
NetBSD
CD or from an ftp site to the chosen media type.
Although booting from floppy is the usual path, the
hard drive boot is useful if you have another operating system (and a spare
drive) already installed, or if you don't mind swapping hard drives from
box to box.
CD and tape boots are nice and fast if you have a CD writer
or a tape format in common with another previously installed
UNIX-like
system.
Finally, most versions of SRM can locate the
NetBSD
boot program
netboot
via bootp and download it via tftp,
netboot
then mounts the root file system
(/)
via NFS and loads the kernel.
Note that if you are installing or upgrading from a writable media, the media can be write-protected if you wish. These systems mount a root image from inside the kernel, and will not need to write to the media. If you booted from a floppy, the floppy disk may be removed from the drive after the system has booted.
The 3.5", 1.44 MB boot floppy set is found under the
NetBSD/alpha
2.1 distribution directory in
alpha/installation/floppy/
as two files called
disk1of2
and
disk2of2,
or as three files called
disk1of3,
disk2of3,
and
disk3of3.
You need to put these disk images on two or three floppy disks.
If you have a UNIX-like system handy, you can do this with commands like the following:
# dd if=disk1of3 of=/dev/rfd0a bs=18k
# dd if=disk2of3 of=/dev/rfd0a bs=18k
# dd if=disk3of3 of=/dev/rfd0a bs=18k
If the
UNIX-like
system you are using is not a
NetBSD
system, you will probably need to replace
/dev/rfd0a
with the name of the floppy device on your particular system.
If you have an
MS-DOS
or
Windows
system available, you can use
the
rawrite.exe
utility to transfer the image to a floppy
disk.
This utility is provided with the
NetBSD/i386
install tools, under
i386/installation/misc;
a documentation file,
rawrite.doc
is available there as well.
Once the floppy has been made, you simply need to put it in the drive and type
>>> B DVA0
All three of these media types use the same initial image:
.../installation/diskimage/cdhdtape
The image can be written to a hard drive partition with a command
like:
# dd if=cdhdtape bs=16k of=/dev/rsd0c
To boot from a magnetic tape device such as DAT or DLT, it is important to create the tape image with 512-byte records. Use a command like:
# dd if=cdhdtape bs=512 of=/dev/rst0
If the host system is not NetBSD, the names of the destination devices are likely to be different. Be sure to use a ``raw partition'' device that doesn't skip over labels!
The use of CD-R devices varies greatly depending on the host OS and host software; it isn't possible to give typical instructions here.
The installation subdirectory
instkernel/
contains
netbsd.gz;
this is the same install kernel but without a bootable file system
image wrapped around it.
You can perform an complete reinstall by beginning it as an upgrade,
and booting this kernel in the normal way off the root file system
(/)
of a previous installation.
The gzipped image can be booted directly; it is not necessary to uncompress it first.
Booting NetBSD/alpha 2.1 over a network requires a BOOTP or DHCP server, a TFTP server and an NFS server. (These are usually all run on the same machine.) There are three basic stages to the boot:
/netbsd.
/)
via NFS and continues.
You will need to set up servers for BOOTP, TFTP and NFS.
If you want to run a full system
from the network, untar the
NetBSD
snapshot or distribution
into a directory on your server and NFS export that directory
to the client.
Make sure you put a kernel there as well, and create the device nodes in
/dev
with
sh ./MAKEDEV all.
Detailed instructions on netbooting can be found by visiting the
NetBSD
alpha platform page:
http://www.NetBSD.org/Ports/alpha
At the time of this release, the URL for the netbooting instructions is: http://www.NetBSD.org/Documentation/network/netboot/
You'll want to map root to
root
(rather than the default
nobody)
when you export your root file system
(/).
A typical
/etc/exports
line on a
NetBSD
system would be:
/usr/export/alpha -maproot=0 myclient.mydom.com
One option is to load just the install kernel over the network but then proceed to a normal disk-based install and disk-based operation. (Perhaps the alpha doesn't have a floppy drive, or you just don't want to use a Windows system to make the floppy; we understand.)
For this case, you still need to export an NFS root, but
the only thing it needs to have in it is the
instkernel
image from the distribution.
The gzipped image can be booted directly; it is not necessary to uncompress it first.
The console will be using TFTP to load the
NetBSD
boot program,
so for the TFTP setup, you need to copy the second stage bootstrap,
netboot,
into an appropriately named file such as
boot.netbsd.alpha
in the directory used by your TFTP server.
If you extracted a full snapshot, you can get the netboot program from
/usr/mdec/netboot;
if not, you can get this from the
installation/netboot
directory where you found the alpha distribution.
For the BOOTP server you need to specify the:
Here's an example for a UNIX-like system running bootpd:
myhost.mydom.com: :ht=ethernet:ha=0000c0391ae4:\
:ip=192.168.1.2:sm=255.255.255.0:\
:sa=192.168.1.1:bf=boot.netbsd.alpha:rp=/usr/export/alpha:
And here's an example for a UNIX-like system running the ISC dhcpd:
host axp {
hardware ethernet 0:0:c0:39:1a:e4;
fixed-address 192.168.1.2;
option host-name "myhost.mydom.com";
filename "boot.netbsd.alpha";
option root-path "/usr/export/alpha";
option domain-name-servers 192.168.1.1;
option broadcast-address 255.255.255.0;
option domain-name "my.domain";
}
The only Ethernet device the console on most alpha systems knows how to boot from is the onboard Ethernet interface or a DEC Tulip (21040, 21041, 21140) PCI Ethernet card. Some older SMC 100 Mbps cards that use this chip have been known to work as well. Many older systems will not be able to use the newer 2.0 stepping of the 21140, however. If your system appears not to be receiving packets, this may be the problem. (You may or may not be able to update your firmware to fix this; see the alpha port pages on http://www.NetBSD.org/ for more information on this.) In general, 10 Mb cards from manufacturers other than DEC will work, and 100 Mb cards not from DEC will not.
Once you're set up, you should be able to boot with:
>>> boot -proto bootp ewa0
You should permanently set your protocol to BOOTP with:
>>> set ewa0_protocols bootp
The 3000 series of Turbochannel systems and certain other models use old SRM, do not have a -proto option and use different device names. They also tend to not netboot very well so you probably don't need to worry about this section. However, if you want to give it a try, note the following differences:
setnetbootinfo(8)
program will probably also be necessary, as it is unlikely that an SRM
from that era will properly communicate the ethernet HW address to the
boot program.
>>> boot ez0
Using sysinst, installing NetBSD is a relatively easy process. You still should read this document and have it in hand when doing the installation process. This document tries to be a good guideline for the installation and as such covers many details for the sake of completeness. Do not let this discourage you; the install program is not hard to use.
Machines with PCMCIA slots may have problems during installation. If you do not have PCMCIA on your machine (PCMCIA is only really used on laptop machines), you can skip this section, and ignore the ``[PCMCIA]'' notes. If you do have PCMCIA in your machine, you can safely ignore this section and the ``[PCMCIA]'' the first time, as you are likely to not have problems. Should troubles occur during floppy boot, they may be PCMCIA specific. You should then re-read this section and try again, following the instructions in the ``[PCMCIA]'' notes.
This section explains how to work around the installation problem.
The kernel keeps careful track of what interrupts
and I/O ports are in use during autoconfiguration.
It then allows the
PCMCIA
devices to pick unused interrupts and I/O ports.
Unfortunately, the
INSTALL
kernel may not detect all devices in your system.
This may be because the
INSTALL
kernel only supports the minimum set of devices to install
NetBSD
on your system, or it may be that
NetBSD
does not have support for the device causing the conflict.
For example, suppose your laptop has a
soundblaster device built in; the
INSTALL
kernel has no sound support.
The
PCMCIA
code might allocate your soundblaster's
IRQ
and I/O ports to
PCMCIA
devices, causing them not to work, or to lock up the system.
This is especially bad if one of the devices in question is your ethernet card.
The kernel attempts to probe for available interrupts that are usable by the PCIC (PCMCIA interrupt controller), which should alleviate interrupt conflicts; however, I/O port conflicts are still possible.
This problem will impact some, but not all, users of PCMCIA. If this problem is affecting you, watch the ``[PCMCIA]'' notes that will appear in this document.
The following is a walk-through of the steps you will take while
getting
NetBSD
installed on your hard disk.
sysinst
is a menu driven
installation system that allows for some freedom in doing the
installation.
Sometimes, questions will be asked and in many cases
the default answer will be displayed in brackets
(``[ ]'')
after the question.
If you wish to stop the installation, you may press
CONTROL-C
at any time, but if you do, you'll have to begin the installation
process again from scratch by running the
/sysinst
program from the command prompt.
It is not necessary to reboot.
First, let's describe a quick install. The other sections of this document go into the installation procedure in more detail, but you may find that you do not need this. If you want detailed instructions, skip to the next section. This section describes a basic installation, using a CD-ROM install as an example.
e:
cd \NetBSD-2.1\i386\installation\misc
rawrite
When asked for a source filename, answer
(...alpha installation root)\floppy\disk1of2
When asked for a destination drive answer `a'.
# dd if=.../boot1.fs bs=18k of=/dev/rfd0a
>>> B DVA0
After language selection, the main menu will be displayed.
.***********************************************.
* NetBSD-2.0 Install System *
* *
*>a: Install NetBSD to hard disk *
* b: Upgrade NetBSD on a hard disk *
* c: Re-install sets or install additional sets *
* d: Reboot the computer *
* e: Utility menu *
* x: Exit Install System *
.***********************************************.
root,
and set a password for that account.
You are also advised to edit the file
/etc/rc.conf
to match your system needs.
/usr/X11R6/lib/X11/doc.
Further information can be found on
http://www.xfree86.org/.
Boot your machine. The boot loader will start, and will print a countdown and begin booting.
If the boot loader messages do not appear in a reasonable amount of time, you either have a bad boot floppy or a hardware problem. Try writing the install floppy image to a different disk, and using that.
It will take a while to load the kernel
from the floppy,
probably around a minute or so, then, the kernel boot messages
will be displayed.
This may take a little while also, as
NetBSD
will be probing your system to discover which hardware devices are
installed.
The most important thing to know is that
wd0
is
NetBSD's
name for your first IDE disk,
wd1
the second, etc.
sd0
is your first SCSI disk,
sd1
the second, etc.
Note that once the system has finished booting, you need not leave the floppy in the disk drive.
Once NetBSD has booted and printed all the boot messages, you will be presented with a welcome message and a main menu. It will also include instructions for using the menus.
If you will not use network operation during the installation, but you do want your machine to be configured for networking once it is installed, you should first go to the Utility menu, and select the Configure network option. If you only want to temporarily use networking during the installation, you can specify these parameters later. If you are not using the Domain Name System (DNS), you can give an empty response in reply to answers relating to this.
To start the installation, select Install NetBSD to hard disk from the main menu.
The first thing is to identify the disk on which you want to
install
NetBSD.
sysinst
will report a list of disks it finds
and ask you for your selection.
Depending on how many disks are found, you may get a different message.
You should see disk names like
wd0,
wd1,
sd0
or
sd1.
You will be asked if you want to use the entire disk or only part of the disk. If you decide to use the entire disk for NetBSD, it will be checked if there are already other systems present on the disk, and you will be asked to confirm whether you want to overwrite these.
The partition table of the NetBSD part of a disk is called a disklabel. There are 4 layouts for the NetBSD part of the disk that you can pick from: Standard, Standard with X, Custom and Use Existing. The first two use a set of default values (that you can change) suitable for a normal installation, possibly including X. With the Custom option you can specify everything yourself. The last option uses the partition info already present on the disk.
You will be presented with the current layout of the NetBSD disklabel, and given a chance to change it. For each partition, you can set the type, offset and size, block and fragment size, and the mount point. The type that NetBSD uses for normal file storage is called 4.2BSD. A swap partition has a special type called swap. Some partitions in the disklabel have a fixed purpose.
a/)
bcd-hd
is the partition mounted on
/usr,
but this is historical practice and not a fixed value.
You will then be asked to name your disk's disklabel. The default response will be ok for most purposes. If you choose to name it something different, make sure the name is a single word and contains no special characters. You don't need to remember this name.
You are now at the point of no return.
Nothing has been
written to your disk yet, but if you confirm that you want to
install
NetBSD,
your hard drive will be modified.
If you are sure you want to proceed, enter
yes
at the prompt.
The install program will now label your disk and make the file systems you specified. The file systems will be initialized to contain NetBSD bootstrapping binaries and configuration files. You will see messages on your screen from the various NetBSD disk preparation tools that are running. There should be no errors in this section of the installation. If there are, restart from the beginning of the installation process. Otherwise, you can continue the installation program after pressing the return key.
The NetBSD distribution consists of a number of sets, that come in the form of gzipped tarfiles. A few sets must be installed for a working system, others are optional. At this point of the installation, you will be presented with a menu which enables you to choose from one of the following methods of installing the sets. Some of these methods will first load the sets on your hard disk, others will extract the sets directly.
For all these methods, the first step is making the sets available for extraction, and then do the actual installation. The sets can be made available in a few different ways. The following sections describe each of those methods. After reading the one about the method you will be using, you can continue to the section labeled `Extracting the distribution sets'.
To be able to install using ftp, you first need to configure
your network setup, if you haven't already at the start of
the install procedure.
sysinst
will do this for you, asking you
if you want to use DHCP, and if not
to provide data like IP address, hostname, etc.
If you do not have name service set up for the machine that you
are installing on, you can just press
RETURN
in answer to these questions, and DNS will not be used.
You will also be asked to specify the host that you want to transfer the sets from, the directory on that host, the account name and password used to log into that host using ftp, and optionally a proxy server to use. If you did not set up DNS when answering the questions to configure networking, you will need to specify an IP address instead of a hostname for the ftp server.
sysinst will proceed to transfer all the default set files from the remote site to your hard disk.
To be able to install using NFS, you first need to configure
your network setup, if you haven't already at the start of
the install procedure.
sysinst
will do this for you, asking you
if you want to use DHCP, and if not
to provide data like IP address, hostname, etc.
If you do not have name service set up for the machine that you
are installing on, you can just press
RETURN
in answer to these questions, and DNS will not be used.
You will also be asked to specify the host that you want to transfer the sets from, and the directory on that host that the files are in. This directory should be mountable by the machine you are installing on, i.e. correctly exported to your machine.
If you did not set up DNS when answering the questions to configure networking, you will need to specify an IP address instead of a hostname for the NFS server.
When installing from a CD-ROM, you will be asked to specify
the device name for your CD-ROM player
(usually cd0),
and the directory name on the CD-ROM where the distribution files are.
sysinst will then check if the files are indeed available in the specified location, and proceed to the actual extraction of the sets.
In order to install from a local file system, you will
need to specify the device that the file system resides
on
(for example sd1e)
the type of the file system,
and the directory on the specified file system where the sets are located.
sysinst
will then check if it
can indeed access the sets at that location.
This option assumes that you have already done some preparation yourself. The sets should be located in a directory on a file system that is already accessible. sysinst will ask you for the name of this directory.
After the install sets containing the NetBSD distribution have been made available, you can either extract all the sets (a full installation), or only extract sets that you have selected. In the latter case, you will be shown the currently selected sets, and given the opportunity to select the sets you want. Some sets always need to be installed (kern, base) and etc they will not be shown in this selection menu.
Before extraction begins, you can elect to watch the files being extracted; the name of each file that is extracted will be shown. This can slow down the installation process considerably, especially on machines with slow graphics consoles or serial consoles.
After all the files have been extracted, all the necessary device node files will be created. If you have already configured networking, you will be asked if you want to use this configuration for normal operation. If so, these values will be installed in the network configuration files. The next menu will allow you to select the time zone that you're in, to make sure your clock has the right offset from UTC. Finally you will be asked to select a password encryption algorithm and can than set a password for the "root" account, to prevent the machine coming up without access restrictions.
Congratulations, you have successfully installed NetBSD2.1. You can now reboot the machine, and boot NetBSD from hard disk.
The normal installation involves running the install shell script and interactively configuring the file systems, and then simply unpacking the tar files into these followed by running MAKEDEV.
However, as stated above it is also possible to do the installation yourself from the shell, and in any case it is helpful to understand what the install script does. The procedure is:
/etc/disktab,
see
disktab(5)
disklabel(8),
newfs(8)
mount(8)
the new root on
/mnt
/usr/mdec
and run
installboot(8)
If you are reviewing man pages on
NetBSD
platforms other than alpha, be sure that when reading
installboot(8)
you read the alpha version by typing:
# man 8 alpha/installboot
At this point you need only unpack the distribution sets by running
tar(1)
as described below.
/install
and
/upgrade
traditional installation scripts
The
install
and
upgrade
scripts are still there, so by exiting the
sysinst
program you can type
install
or
upgrade
at the shell prompt and run them as you did in the good old days.
You may install
on either a SCSI or an IDE disk; you will be prompted for
the disk to install on.
The disks in your system will be numbered starting at
xd0
(where
x
is an
`s'
for SCSI disks,
`w'
for IDE disks) based on the SCSI-ID or IDE drive order; if you have
more than one disk, watch the boot messages carefully to see
which ones are probed as which numbers.
Once you've selected a disk to install on, you'll be prompted for the geometry. This is also displayed in the boot messages, and you'll be given a chance to review the boot messages again to get the exact figures for the number of cylinders, heads and sectors.
After this you must specify the size of your partitions. Generally you'll be giving the sizes in cylinders; the install program will tell you how many bytes there are in each cylinder.
The swap partition is the second thing you specify, after the
/
(root) partition.
Regardless of the size of your disk, you'll
want to specify a swap partition that's at least as large as
the amount of RAM you have, and probably not less than 64 MB
in any case.
If you have a small disk (under 500 MB), it's probably best to
devote all of the disk (excepting 64 MB or more for the swap)
to the
/
(root) partition.
If you have more space, we recommend devoting at least 32 MB,
and preferably 48 MB, to the
/
(root) partition.
/usr
will need 150 MB or so if you're not installing X, 200 MB or so if you are.
A typical organization is 50 MB for
/
(root), 150-250 MB for
swap, and the remaining space for
/usr.
With enough swap space configured, you can make
/tmp
a nice, fast mfs.
See
mount_mfs(8),
and note that the mfs will require swap space for
the largest planned amount of
/tmp
storage.
It doesn't return space when files are deleted,
but just keeps it its own freelist so the swap space required is
equal to the highwater mark of
/tmp
use, plus space required to back up main memory and store inactive images.
Once you've specified this information, the install script will
write the disklabel, install boot blocks to make the disk
bootable, initialise the file systems, and mount them all under
/mnt.
You are now ready to go on to the next step.
After doing the disk and file system setup with either
shell commands or the script assist, you then need only
unpack the distribution sets with the
tar(1)
command.
To do this you will need access from the target host to the tar files
that contain the operating system in order to extract them to your disk.
This is done via an NFS or FTP transfer over a network,
via a CD-ROM archive, a tape archive, or by preloading an accessible hard
drive with the necessary tar files.
All you need to do is mount the CD-ROM, which will generally be device cd0. (The initial boot messages will tell you what the CD-ROM drive is probed as.) This would be done with:
# mount -r -t cd9660 /dev/cd0a /mnt2
The first thing you need to do is configure the loopback network interface, which is done with the command
# ifconfig lo0 127.0.0.1
Then you will have to configure your Ethernet card. The command
# ifconfig -l
will give you a list of the network interfaces on your system. It will show you your ethernet cards first, followed by lo0 (the loopback interface that we configured above), ppp0 (the PPP interface) and sl0 (the SLIP interface).
To configure your ethernet card, type
ifconfig if inet
addr
[netmask]
[media media]
where
if
is the network card (interface), almost always
de0,
addr
is the IP address, the optional
netmask
parameter is the network mask,
and the optional
media
parameter is one of:
| 10base2 | BNC connector | 10 Mbps |
| AUI | AUI connector | 10 Mbps |
| 10baseT/UTP | Twisted pair connector | 10 Mbps |
| 100baseTX | Twisted pair connector | 100 Mbps |
| 100baseFX | Fibre-optic connector | 100 Mbps |
| 100baseT4 | T4 twisted pair interface | 100 Mbps |
If the host you are getting the data files from is not on the local network, you will also have to configure a gateway into your system. Do this with
# route add default <gateway-IP-address>
One improvement over the good old days is that the resolver is now
present; by configuring
/etc/resolv.conf
you can get name resolution during any install NFS or FTP operations.
Once networking has been configured, you may mount the directory with the install files via NFS, or download them via FTP.
To mount them via nfs, type
# mount -t nfs <hostname:/path/to/nfs/volume> /mnt2
If this volume has been exported read-only, you may need the -r option to mount.
To download the install sets with ftp, create a directory in which to put them and then use the ftp client to download them. Mirror sites are listed at: http://www.NetBSD.org/mirrors/ A typical session might be:
# mkdir /mnt/usr/release
# cd /mnt/usr/release
# ftp ftp.NetBSD.org
the following commands are given to the ftp program after logging in
ftp> prompt
ftp> cd /pub/NetBSD/NetBSD-2.1/alpha/binary/sets
ftp> mget *
ftp> quit
Feel free, of course, to leave off the sets that you don't need if you don't plan to install everything.
Change to the root directory of your hard
drive (which is
/mnt
if you've used the standard install script
to this point) by typing
# cd /mnt
For this and the following commands, replace
/mnt/usr/release/
with the path to your NFS volume or CD-ROM if that's how you
chose to access your install files instead.
The sets and kernel are extracted with:
# cd /mnt
# for i in base kern comp etc games man misc text; do
tar -zxpf /mnt/usr/release/$i.tgz;
# done
or perhaps:
# cd /mnt
# for i in /mnt/usr/release/*.tgz; do
echo $i
tar -zxpf $i
# done
Now make the device nodes:
# cd /mnt/dev
# sh ./MAKEDEV all
Unmount the file systems and halt. The exact instructions to type here will depend on the file systems you created, but typically the commands are:
# cd /
# umount /mnt/usr
# umount /mnt
# sync
(sync)is not strictly necessary but it is traditional
# halt
You should now be at the SRM console's
>>>
prompt and can reboot
into the new configuration (possibly after an optional power cycle)
with a command such as:
>>> boot dka0
This command might be: boot dka100 if your drive is on ID 1. You can usually use show device to see a full list of bootable devices in your system. Your system will come up in single-user mode, ready for you to configure it.
You can create the floppy needed for installation under MS-DOS or Windows. Supposing your 1.44 MB floppy drive is drive A:, and your CD is drive E:, do the following from an MS-DOS command prompt:
e:
cd \NetBSD-2.1\installation\misc
rawrite
When asked for a source filename, answer
...\floppy\disk1of2
When asked for a destination drive answer
a
(Repeat the procedure for
installation/floppy/disk2of2.)
Once you've got the operating system running, there are a few things you need to do in order to bring the system into a properly configured state, with the most important ones described below.
/etc/rc.conf
If you or the installation software haven't done any configuration of
/etc/rc.conf
(sysinst
usually will),
the system will drop you into single user mode on first reboot with the
message
/etc/rc.conf is not configured. Multiuser boot aborted.
and with the root file system
(/)
mounted read-only.
When the system asks you to choose a shell, simply press
RETURN
to get to a
/bin/sh
prompt.
If you are asked for a terminal type, respond with
vt220
(or whatever is appropriate for your terminal type)
and press
RETURN.
You may need to type one of the following commands to get your delete key
to work properly, depending on your keyboard:
# stty erase '^h'
# stty erase '^?'
At this point, you need to configure at least
one file in the
/etc
directory.
You will need to mount your root file system read/write with:
# /sbin/mount -u -w /
Change to the
/etc
directory and take a look at the
/etc/rc.conf
file.
Modify it to your tastes, making sure that you set
rc_configured=YES
so that your changes will be enabled and a multi-user boot can
proceed.
Default values for the various programs can be found in
/etc/defaults/rc.conf,
where some in-line documentation may be found.
More complete documentation can be found in
rc.conf(5).
If your
/usr
directory is on a separate partition and you do not know how to use
ed,
you will have to mount your
/usr
partition to gain access to
ex
or
vi.
Do the following:
# mount /usr
# export TERM=vt220
If you have
/var
on a separate partition, you need to repeat that step for it.
After that, you can edit
/etc/rc.conf
with
vi(1).
When you have finished, type
exit
at the prompt to
leave the single-user shell and continue with the multi-user boot.
Other values that need to be set in
/etc/rc.conf
for a networked environment are
hostname
and possibly
defaultroute,
furthermore add an
ifconfig_int
for your
<int>
network interface,
along the lines of
ifconfig_de0="inet 123.45.67.89 netmask 255.255.255.0"
or, if you have
myname.my.dom
in
/etc/hosts:
ifconfig_de0="inet myname.my.dom netmask 255.255.255.0"
To enable proper hostname resolution, you will also want to add an
/etc/resolv.conf
file or (if you are feeling a little more adventurous) run
named(8).
See
resolv.conf(5)
or
named(8)
for more information.
Instead of manually configuring network and naming service,
DHCP can be used by setting
dhclient=YES
in
/etc/rc.conf.
Other files in
/etc
that may require modification or setting up include
/etc/mailer.conf,
/etc/nsswitch.conf,
and
/etc/wscons.conf.
After reboot, you can log in as
root
at the login prompt.
Unless you've set a password in
sysinst,
there
is no initial password.
If you're using the machine in a networked environment,
you should create an account for yourself (see below) and protect it and the
``root''
account with good passwords.
By default, root login from the network is disabled (even via
ssh(1)).
One way to become root over the network is to log in as a different
user that belongs to group
``wheel''
(see
group(5))
and use
su(1)
to become root.
Unless you have connected an unusual terminal device as the console
you can just press
RETURN
when it prompts for
Terminal type? [...].
Use the
useradd(8)
command to add accounts to your system.
Do not
edit
/etc/passwd
directly! See
vipw(8)
and
pwd_mkdb(8)
if you want to edit the password database.
If you have installed the X Window System, look at the files in
/usr/X11R6/lib/X11/doc
for information.
Don't forget to add
/usr/X11R6/bin
to your path in your shell's dot file so that you have access to the X binaries.
If you wish to install any of the software freely available for UNIX-like systems you are strongly advised to first check the NetBSD package system. This automatically handles any changes necessary to make the software run on NetBSD, retrieval and installation of any other packages on which the software may depend, and simplifies installation (and deinstallation), both from source and precompiled binaries.
2.1/alpha/All
subdir.
You can install them with the following commands under
sh(1):
# PKG_PATH=ftp://ftp.NetBSD.org/pub/NetBSD/packages/2.1/alpha/All # export PKG_PATH # pkg_add -v tcsh # pkg_add -v bash # pkg_add -v perl # pkg_add -v apache # pkg_add -v kde # pkg_add -v mozilla ...
If you are using
csh(1)
then replace the first two lines with the following:
# setenv PKG_PATH ftp://ftp.NetBSD.org/pub/NetBSD/packages/2.1/alpha/All ...
The above commands will install the Tenex-csh and Bourne Again shell, the Perl programming language, Apache web server, KDE desktop environment and the Mozilla web browser as well as all the packages they depend on.
/usr/pkgsrc
(though other locations work fine), with the commands:
# mkdir /usr/pkgsrc
#( cd /usr/pkgsrc ; tar -zxpf - ) < pkgsrc.tar.gz
After extracting, see the
README
and
doc/pkgsrc.txt
files in the extraction directory (e.g.
/usr/pkgsrc/README)
for more information.
/etc/mail/aliases
to forward root mail to the right place.
Don't forget to run
newaliases(1)
afterwards.
/etc/mail/sendmail.cf
file will almost definitely need to be adjusted;
files aiding in this can be found in
/usr/share/sendmail.
See the
README
file there for more information.
If you prefer postfix as MTA, adjust
/etc/mailer.conf.
/etc/rc.local
to run any local daemons you use.
/etc
files are documented in section 5 of the manual; so just invoking
# man 5 filename
is likely to give you more information on these files.
The upgrade to NetBSD2.1 is a binary upgrade; it can be quite difficult to update the system from an earlier version by recompiling from source, primarily due to interdependencies in the various components.
To do the upgrade, you must have the boot floppy
set
available.
You must also have at least the
base
and
kern
binary distribution sets available, so that you can upgrade with them,
using one of the upgrade methods described above.
Finally, you must have sufficient disk space available to install the
new binaries.
Since files already installed on the system are overwritten in place,
you only need additional free space for files which weren't previously
installed or to account for growth of the sets between releases.
If you have a few megabytes free on each of your root
(/)
and
/usr
partitions, you should have enough space.
Since upgrading involves replacing the kernel, the boot blocks on your NetBSD partition, and most of the system binaries, it has the potential to cause data loss. You are strongly advised to back up any important data on the NetBSD partition or on another operating system's partition on your disk before beginning the upgrade process.
The upgrade procedure using the
sysinst
tool is similar to an installation, but without the hard disk partitioning.
sysinst
will attempt to merge the settings stored in your
/etc
directory with the new version of
NetBSD.
Getting the binary
sets is done in the same manner as the installation procedure;
refer to the installation part of the document
for how to do this.
Also, some sanity checks are done, i.e.
file systems are checked before unpacking the sets.
After a new kernel has been copied to your hard disk, your
machine is a complete
NetBSD2.1
system.
However, that doesn't mean that you're finished with the upgrade process.
You will probably want to update the set of device
nodes you have in
/dev.
If you've changed the contents of
/dev
by hand, you will need to be careful about this, but if
not, you can just cd into
/dev,
and run the command:
# sh MAKEDEV all
Finally, you will want to delete old binaries that were part
of the version of
NetBSD
that you upgraded from and have since been removed from the
NetBSD
distribution.
Users upgrading from previous versions of NetBSD may wish to bear the following problems and compatibility issues in mind when upgrading to NetBSD2.1.
mkdir /tmp/upgrade
cd /tmp/upgrade
pax -zrpe -f /path/to/etc.tgz
./etc/postinstall -s `pwd` check
./etc/postinstall -s `pwd` fix
Issues fixed by postinstall:
/etc
need upgrading.
These include:
/etc/defaults/*
/etc/mtree/*
/etc/daily
/etc/weekly
/etc/monthly
/etc/security
/etc/rc.subr
/etc/rc
/etc/rc.shutdown
/etc/rc.d/*
/etc/rc.d/fsck.sh
/etc/rc.d/gated
/etc/rc.d/kerberos
/etc/rc.d/NETWORK
/etc/rc.d/systemfs
/etc/rc.d/xntpd
and
/etc/rc.d/ypset.
The following issues need to be resolved manually:
postfix(8)
configuration files require upgrading.
cd /usr/share/examples/postfix
cp post-install postfix-files postfix-script /etc/postfix
postfix check
Documentation is available if you first install the manual
distribution set.
Traditionally, the
``man pages''
(documentation) are denoted by
`name(section)'.
Some examples of this are
intro(1),
man(1),
apropros(1),
passwd(1),
and
passwd(5).
The section numbers group the topics into several categories, but three are of primary interest: user commands are in section 1, file formats are in section 5, and administrative information is in section 8.
The man command is used to view the documentation on a topic, and is started by entering man[ section] topic. The brackets [] around the section should not be entered, but rather indicate that the section is optional. If you don't ask for a particular section, the topic with the lowest numbered section name will be displayed. For instance, after logging in, enter
# man passwd
to read the documentation for
passwd(1).
To view the documentation for
passwd(5),
enter
# man 5 passwd
instead.
If you are unsure of what man page you are looking for, enter
apropos subject-word
where subject-word is your topic of interest; a list of possibly related man pages will be displayed.
If you've got something to say, do so! We'd like your input. There are various mailing lists available via the mailing list server at majordomo@NetBSD.org. To get help on using the mailing list server, send mail to that address with an empty body, and it will reply with instructions.
There are various mailing lists set up to deal with comments and questions about this release. Please send comments to: netbsd-comments@NetBSD.org.
To report bugs, use the
send-pr(1)
command shipped with
NetBSD,
and fill in as much information about the problem as you can.
Good bug reports include lots of details.
Additionally, bug reports can be sent by mail to:
netbsd-bugs@NetBSD.org.
Use of
send-pr(1)
is encouraged, however, because bugs reported with it
are entered into the
NetBSD
bugs database, and thus can't slip through
the cracks.
There are also port-specific mailing lists, to discuss aspects of each port of NetBSD. Use majordomo to find their addresses, or visit http://www.NetBSD.org/MailingLists/. If you're interested in doing a serious amount of work on a specific port, you probably should contact the `owner' of that port (listed below).
If you'd like to help with this effort, and have an idea as to how you could be useful, send us mail or subscribe to: netbsd-help@NetBSD.org.
As a favor, please avoid mailing huge documents or files to these mailing lists. Instead, put the material you would have sent up for FTP or WWW somewhere, then mail the appropriate list about it, or, if you'd rather not do that, mail the list saying you'll send the data to those who want it.
Keith Bostic Ralph Campbell Mike Karels Marshall Kirk McKusick
for their ongoing work on BSD systems, support, and encouragement.
AboveNet Communications, Inc. Advanced System Products, Inc. Alex Poylisher Alistair Crooks Andrew Brown Atsushi YOKOYAMA Avalon Computer Systems Bay Area Internet Solutions Ben Collver Bill Coldwell Bill Sommerfeld Brad Salai Brains Corporation, Japan Brian Carlstrom Brian McGroarty Canada Connect Corporation Castor Fu Central Iowa (Model) Railroad Charles Conn Charles D. Cranor Charles M. Hannum Chris Legrow Christer O. Andersson Christopher g. Demetriou Christos Zoulas Chuck Silvers Co-operative Research Centre for Enterprise Distributed Curt Sampson Dave Burgess Dave Rand David Brownlee Demon Internet, UK Derek Fellion Digital Equipment Corporation Distributed Processing Technology Douglas J. Trainor Easynet, UK Ed Braaten Edward Richley Eric and Rosemary Spahr Free Hardware Foundation Greg Gingerich Guenther Grau Harald Koerfgen Harry McDonald Heiko W. Rupp Herb Peyerl Hubert Feyrer Innovation Development Enterprises of America Internet Software Consortium James Chacon Jan Joris Vereijken Jason Birnschein Jason Brazile Jason R. Thorpe Jim Wise John Kohl Jonathan P. Kay Jordan K. Hubbard Kenneth Alan Hornstein Kevin Keith Woo Kimmo Suominen Krister Waldfridsson Lex Wennmacher LinuxFest Northwest Luke Mewburn MS Macro System GmbH, Germany Mark Brinicombe Mark S. Thomas Mason Loring Bliss Mattias Karlsson Michael Graff Michael L. Hitch Michael Richardson Michael Thompson Michael W. James Mike Price Neil J. McRae Noah M. Keiserman Norman R. McBride Numerical Aerospace Simulation Facility, NASA Ames Research Oliver Cahagne Perry E. Metzger Petri T. Koistinen Piermont Information Systems Inc. Precedence Technologies Ltd Ralph Campbell Reinoud Zandijk Richard Nelson Rob Windsor Ross Harvey SDF Public Access Unix, Inc. 501(c)(7) Salient Systems Inc. Scott Ellis Scott Kaplan Simon Burge Soren Jacobsen Soren Jorvang Steve Allen Steve Wadlow SunROOT# Project Ted Lemon Ted Spradley Thor Lancelot Simon Tim Law Tom Coulter Toru Nishimura VMC Harald Frank, Germany Warped Communications, Inc. Wasabi Systems Whitecross Database Systems Ltd. William Gnadt Worria Web Hosting
(If you're not on that list and should be, tell us! We probably were not able to get in touch with you, to verify that you wanted to be listed.)
(in alphabetical order)
| The NetBSD core group: | |||
| Allen Briggs | briggs@NetBSD.org | ||
| Matt Thomas | matt@NetBSD.org | ||
| Valeriy E. Ushakov | uwe@NetBSD.org | ||
| YAMAMOTO Takashi | yamt@NetBSD.org | ||
| Christos Zoulas | christos@NetBSD.org | ||
|
| |||
| The portmasters (and their ports): | |||
| Ta | |||
| Allen Briggs | briggs@NetBSD.org | sandpoint | |
| Anders Magnusson | ragge@NetBSD.org | vax | |
| Andrey Petrov | petrov@NetBSD.org | sparc64 | |
| Ben Harris | bjh21@NetBSD.org | acorn26 | |
| Chris Gilbert | chris@NetBSD.org | cats | |
| Christian Limpach | cl@NetBSD.org | xen | |
| Eduardo Horvath | eeh@NetBSD.org | evbppc | |
| Frank van der Linden | fvdl@NetBSD.org | amd64 | |
| Frank van der Linden | fvdl@NetBSD.org | i386 | |
| Gavan Fantom | gavan@NetBSD.org | iyonix | |
| IWAMOTO Toshihiro | toshii@NetBSD.org | hpcarm | |
| Ichiro Fukuhara | ichiro@NetBSD.org | hpcarm | |
| Ignatios Souvatzis | is@NetBSD.org | amiga | |
| Izumi Tsutsui | tsutsui@NetBSD.org | hp300 | |
| Izumi Tsutsui | tsutsui@NetBSD.org | news68k | |
| Jason Thorpe | thorpej@NetBSD.org | algor | |
| Jason Thorpe | thorpej@NetBSD.org | evbarm | |
| Jason Thorpe | thorpej@NetBSD.org | shark | |
| Jeremy Cooper | jeremy@NetBSD.org | sun3 | |
| Jonathan Stone | jonathan@NetBSD.org | pmax | |
| Julian Coleman | jdc@NetBSD.org | atari | |
| Jun-ichiro itojun Hagino | itojun@NetBSD.org | evbsh3 | |
| Jun-ichiro itojun Hagino | itojun@NetBSD.org | mmeye | |
| Kazuki Sakamoto | sakamoto@NetBSD.org | bebox | |
| Lennart Augustsson | augustss@NetBSD.org | pmppc | |
| Marcus Comstedt | marcus@NetBSD.org | dreamcast | |
| Martin Husemann | martin@NetBSD.org | sparc64 | |
| Matt DeBergalis | deberg@NetBSD.org | next68k | |
| Matt Fredette | fredette@NetBSD.org | hp700 | |
| Matt Fredette | fredette@NetBSD.org | sun2 | |
| Matt Thomas | matt@NetBSD.org | alpha | |
| Matt Thomas | matt@NetBSD.org | netwinder | |
| Matthias Drochner | drochner@NetBSD.org | cesfic | |
| NISHIMURA Takeshi | nsmrtks@NetBSD.org | x68k | |
| NONAKA Kimihiro | nonaka@NetBSD.org | prep | |
| Nathan Williams | nathanw@NetBSD.org | sun3 | |
| Noriyuki Soda | soda@NetBSD.org | arc | |
| Paul Kranenburg | pk@NetBSD.org | sparc | |
| Phil Nelson | phil@NetBSD.org | pc532 | |
| Reinoud Zandijk | reinoud@NetBSD.org | acorn32 | |
| Ross Harvey | ross@NetBSD.org | alpha | |
| Søren Jørvang | soren@NetBSD.org | cobalt | |
| Søren Jørvang | soren@NetBSD.org | sgimips | |
| Scott Reynolds | scottr@NetBSD.org | mac68k | |
| Shin Takemura | takemura@NetBSD.org | hpcmips | |
| Simon Burge | simonb@NetBSD.org | evbmips | |
| Simon Burge | simonb@NetBSD.org | evbppc | |
| Simon Burge | simonb@NetBSD.org | pmax | |
| Simon Burge | simonb@NetBSD.org | sbmips | |
| Steve Woodford | scw@NetBSD.org | evbsh5 | |
| Steve Woodford | scw@NetBSD.org | mvme68k | |
| Steve Woodford | scw@NetBSD.org | mvmeppc | |
| Tohru Nishimura | nisimura@NetBSD.org | luna68k | |
| Tsubai Masanari | tsubai@NetBSD.org | macppc | |
| Tsubai Masanari | tsubai@NetBSD.org | newsmips | |
| UCHIYAMA Yasushi | uch@NetBSD.org | hpcsh | |
| UCHIYAMA Yasushi | uch@NetBSD.org | playstation2 | |
| Wayne Knowles | wdk@NetBSD.org | mipsco | |
| Wolfgang Solfrank | ws@NetBSD.org | ofppc | |
|
| |||
| The NetBSD 2.1 Release Engineering team: | |||
| Grant Beattie | grant@NetBSD.org | ||
| Erik Berls | cyber@NetBSD.org | ||
| James Chacon | jmc@NetBSD.org | ||
| Julian Coleman | jdc@NetBSD.org | ||
| Håvard Eidnes | he@NetBSD.org | ||
| Jun-ichiro itojun Hagino | itojun@NetBSD.org | ||
| Soren Jacobsen | snj@NetBSD.org | ||
| SAITOH Masanobu | msaitoh@NetBSD.org | ||
| Luke Mewburn | lukem@NetBSD.org | ||
| Jeff Rizzo | riz@NetBSD.org | ||
| Matthias Scheler | tron@NetBSD.org | ||
| Curt Sampson | cjs@NetBSD.org | ||
| Jim Wise | jwise@NetBSD.org | ||
|
| |||
| NetBSD Developers: | |||
| Nathan Ahlstrom | nra@NetBSD.org | ||
| Steve Allen | wormey@NetBSD.org | ||
| Jukka Andberg | jandberg@NetBSD.org | ||
| Julian Assange | proff@NetBSD.org | ||
| Lennart Augustsson | augustss@NetBSD.org | ||
| Christoph Badura | bad@NetBSD.org | ||
| Bang Jun-Young | junyoung@NetBSD.org | ||
| Dieter Baron | dillo@NetBSD.org | ||
| Robert V. Baron | rvb@NetBSD.org | ||
| Grant Beattie | grant@NetBSD.org | ||
| Jason Beegan | jtb@NetBSD.org | ||
| Erik Berls | cyber@NetBSD.org | ||
| Hiroyuki Bessho | bsh@NetBSD.org | ||
| John Birrell | jb@NetBSD.org | ||
| Mason Loring Bliss | mason@NetBSD.org | ||
| Charles Blundell | cb@NetBSD.org | ||
| Rafal Boni | rafal@NetBSD.org | ||
| Sean Boudreau | seanb@NetBSD.org | ||
| Manuel Bouyer | bouyer@NetBSD.org | ||
| John Brezak | brezak@NetBSD.org | ||
| Allen Briggs | briggs@NetBSD.org | ||
| Mark Brinicombe | mark@NetBSD.org | ||
| Aaron Brown | abrown@NetBSD.org | ||
| Andrew Brown | atatat@NetBSD.org | ||
| David Brownlee | abs@NetBSD.org | ||
| Frederick Bruckman | fredb@NetBSD.org | ||
| Jon Buller | jonb@NetBSD.org | ||
| Simon Burge | simonb@NetBSD.org | ||
| Robert Byrnes | byrnes@NetBSD.org | ||
| D'Arcy J.M. Cain | darcy@NetBSD.org | ||
| Dave Carrel | carrel@NetBSD.org | ||
| Daniel Carosone | dan@NetBSD.org | ||
| James Chacon | jmc@NetBSD.org | ||
| Bill Coldwell | billc@NetBSD.org | ||
| Julian Coleman | jdc@NetBSD.org | ||
| Ben Collver | ben@NetBSD.org | ||
| Jeremy Cooper | jeremy@NetBSD.org | ||
| Chuck Cranor | chuck@NetBSD.org | ||
| Alistair Crooks | agc@NetBSD.org | ||
| Aidan Cully | aidan@NetBSD.org | ||
| Johan Danielsson | joda@NetBSD.org | ||
| John Darrow | jdarrow@NetBSD.org | ||
| Matt DeBergalis | deberg@NetBSD.org | ||
| Rob Deker | deker@NetBSD.org | ||
| Chris G. Demetriou | cgd@NetBSD.org | ||
| Tracy Di Marco White | gendalia@NetBSD.org | ||
| Jaromír Dolecek | jdolecek@NetBSD.org | ||
| Andy Doran | ad@NetBSD.org | ||
| Roland Dowdeswell | elric@NetBSD.org | ||
| Emmanuel Dreyfus | manu@NetBSD.org | ||
| Matthias Drochner | drochner@NetBSD.org | ||
| Jun Ebihara | jun@NetBSD.org | ||
| Elad Efrat | elad@NetBSD.org | ||
| Håvard Eidnes | he@NetBSD.org | ||
| Stoned Elipot | seb@NetBSD.org | ||
| Michael van Elst | mlelstv@NetBSD.org | ||
| Enami Tsugutomo | enami@NetBSD.org | ||
| Bernd Ernesti | veego@NetBSD.org | ||
| Erik Fair | fair@NetBSD.org | ||
| Gavan Fantom | gavan@NetBSD.org | ||
| Hubert Feyrer | hubertf@NetBSD.org | ||
| Jason R. Fink | jrf@NetBSD.org | ||
| Matt Fredette | fredette@NetBSD.org | ||
| Thorsten Frueauf | frueauf@NetBSD.org | ||
| Castor Fu | castor@NetBSD.org | ||
| Ichiro Fukuhara | ichiro@NetBSD.org | ||
| Quentin Garnier | cube@NetBSD.org | ||
| Thomas Gerner | thomas@NetBSD.org | ||
| Simon J. Gerraty | sjg@NetBSD.org | ||
| Justin Gibbs | gibbs@NetBSD.org | ||
| Chris Gilbert | chris@NetBSD.org | ||
| Eric Gillespie | epg@NetBSD.org | ||
| Adam Glass | glass@NetBSD.org | ||
| Michael Graff | explorer@NetBSD.org | ||
| Brian C. Grayson | bgrayson@NetBSD.org | ||
| Matthew Green | mrg@NetBSD.org | ||
| Andreas Gustafsson | gson@NetBSD.org | ||
| Jun-ichiro itojun Hagino | itojun@NetBSD.org | ||
| Juergen Hannken-Illjes | hannken@NetBSD.org | ||
| Charles M. Hannum | mycroft@NetBSD.org | ||
| Ben Harris | bjh21@NetBSD.org | ||
| Ross Harvey | ross@NetBSD.org | ||
| Eric Haszlakiewicz | erh@NetBSD.org | ||
| John Hawkinson | jhawk@NetBSD.org | ||
| HAMAJIMA Katsuomi | hamajima@NetBSD.org | ||
| HAYAKAWA Koichi | haya@NetBSD.org | ||
| John Heasley | heas@NetBSD.org | ||
| René Hexel | rh@NetBSD.org | ||
| Kouichirou Hiratsuka | hira@NetBSD.org | ||
| Michael L. Hitch | mhitch@NetBSD.org | ||
| Christian E. Hopps | chopps@NetBSD.org | ||
| Ken Hornstein | kenh@NetBSD.org | ||
| Marc Horowitz | marc@NetBSD.org | ||
| Eduardo Horvath | eeh@NetBSD.org | ||
| Nick Hudson | skrll@NetBSD.org | ||
| Shell Hung | shell@NetBSD.org | ||
| Martin Husemann | martin@NetBSD.org | ||
| Dean Huxley | dean@NetBSD.org | ||
| Love Hörnquist Åstrand | lha@NetBSD.org | ||
| Bernardo Innocenti | bernie@NetBSD.org | ||
| Tetsuya Isaki | isaki@NetBSD.org | ||
| ITOH Yasufumi | itohy@NetBSD.org | ||
| IWAMOTO Toshihiro | toshii@NetBSD.org | ||
| Matthew Jacob | mjacob@NetBSD.org | ||
| Soren Jacobsen | snj@NetBSD.org | ||
| Lonhyn T. Jasinskyj | lonhyn@NetBSD.org | ||
| Darrin Jewell | dbj@NetBSD.org | ||
| Chris Jones | cjones@NetBSD.org | ||
| Søren Jørvang | soren@NetBSD.org | ||
| Takahiro Kambe | taca@NetBSD.org | ||
| Antti Kantee | pooka@NetBSD.org | ||
| Masanori Kanaoka | kanaoka@NetBSD.org | ||
| Mattias Karlsson | keihan@NetBSD.org | ||
| KAWAMOTO Yosihisa | kawamoto@NetBSD.org | ||
| Mario Kemper | magick@NetBSD.org | ||
| Min Sik Kim | minskim@NetBSD.org | ||
| Thomas Klausner | wiz@NetBSD.org | ||
| Klaus Klein | kleink@NetBSD.org | ||
| John Klos | jklos@NetBSD.org | ||
| Wayne Knowles | wdk@NetBSD.org | ||
| Takayoshi Kochi | kochi@NetBSD.org | ||
| John Kohl | jtk@NetBSD.org | ||
| Daniel de Kok | daniel@NetBSD.org | ||
| Paul Kranenburg | pk@NetBSD.org | ||
| Martti Kuparinen | martti@NetBSD.org | ||
| Kentaro A. Kurahone | kurahone@NetBSD.org | ||
| Kevin Lahey | kml@NetBSD.org | ||
| Johnny C. Lam | jlam@NetBSD.org | ||
| Martin J. Laubach | mjl@NetBSD.org | ||
| Greg Lehey | grog@NetBSD.org | ||
| Ted Lemon | mellon@NetBSD.org | ||
| Christian Limpach | cl@NetBSD.org | ||
| Frank van der Linden | fvdl@NetBSD.org | ||
| Joel Lindholm | joel@NetBSD.org | ||
| Mike Long | mikel@NetBSD.org | ||
| Michael Lorenz | macallan@NetBSD.org | ||
| Warner Losh | imp@NetBSD.org | ||
| Tomasz Luchowski | zuntum@NetBSD.org | ||
| Federico Lupi | federico@NetBSD.org | ||
| Brett Lymn | blymn@NetBSD.org | ||
| Paul Mackerras | paulus@NetBSD.org | ||
| Anders Magnusson | ragge@NetBSD.org | ||
| MAEKAWA Masahide | gehenna@NetBSD.org | ||
| David Maxwell | david@NetBSD.org | ||
| Dan McMahill | dmcmahill@NetBSD.org | ||
| Gregory McGarry | gmcgarry@NetBSD.org | ||
| Jared D. McNeill | jmcneill@NetBSD.org | ||
| Neil J. McRae | neil@NetBSD.org | ||
| Perry Metzger | perry@NetBSD.org | ||
| Simas Mockevicius | symka@NetBSD.org | ||
| Juan Romero Pardines | xtraeme@NetBSD.org | ||
| Julio M. Merino Vidal | jmmv@NetBSD.org | ||
| Minoura Makoto | minoura@NetBSD.org | ||
| Luke Mewburn | lukem@NetBSD.org | ||
| der Mouse | mouse@NetBSD.org | ||
| Joseph Myers | jsm@NetBSD.org | ||
| Ken Nakata | kenn@NetBSD.org | ||
| Takeshi Nakayama | nakayama@NetBSD.org | ||
| Phil Nelson | phil@NetBSD.org | ||
| Bob Nestor | rnestor@NetBSD.org | ||
| NISHIMURA Takeshi | nsmrtks@NetBSD.org | ||
| Tohru Nishimura | nisimura@NetBSD.org | ||
| NONAKA Kimihiro | nonaka@NetBSD.org | ||
| Takehiko NOZAKI | tnozaki@NetBSD.org | ||
| Jesse Off | joff@NetBSD.org | ||
| Tatoku Ogaito | tacha@NetBSD.org | ||
| OKANO Takayoshi | kano@NetBSD.org | ||
| Masaru Oki | oki@NetBSD.org | ||
| Atsushi Onoe | onoe@NetBSD.org | ||
| Greg Oster | oster@NetBSD.org | ||
| Jonathan Perkin | sketch@NetBSD.org | ||
| Herb Peyerl | hpeyerl@NetBSD.org | ||
| Matthias Pfaller | matthias@NetBSD.org | ||
| Chris Pinnock | cjep@NetBSD.org | ||
| Adrian Portelli | adrianp@NetBSD.org | ||
| Rui Paulo | rpaulo@NetBSD.org | ||
| Peter Postma | peter@NetBSD.org | ||
| Dante Profeta | dante@NetBSD.org | ||
| Chris Provenzano | proven@NetBSD.org | ||
| Niels Provos | provos@NetBSD.org | ||
| Michael Rauch | mrauch@NetBSD.org | ||
| Marc Recht | recht@NetBSD.org | ||
| Darren Reed | darrenr@NetBSD.org | ||
| Jeremy C. Reed | reed@NetBSD.org | ||
| Antoine Reilles | tonio@NetBSD.org | ||
| Tyler R. Retzlaff | rtr@NetBSD.org | ||
| Scott Reynolds | scottr@NetBSD.org | ||
| Michael Richardson | mcr@NetBSD.org | ||
| Tim Rightnour | garbled@NetBSD.org | ||
| Jeff Rizzo | riz@NetBSD.org | ||
| Gordon Ross | gwr@NetBSD.org | ||
| Steve Rumble | rumble@NetBSD.org | ||
| Ilpo Ruotsalainen | lonewolf@NetBSD.org | ||
| Heiko W. Rupp | hwr@NetBSD.org | ||
| David Sainty | dsainty@NetBSD.org | ||
| SAITOH Masanobu | msaitoh@NetBSD.org | ||
| Kazuki Sakamoto | sakamoto@NetBSD.org | ||
| Curt Sampson | cjs@NetBSD.org | ||
| Wilfredo Sanchez | wsanchez@NetBSD.org | ||
| Ty Sarna | tsarna@NetBSD.org | ||
| SATO Kazumi | sato@NetBSD.org | ||
| Jan Schaumann | jschauma@NetBSD.org | ||
| Matthias Scheler | tron@NetBSD.org | ||
| Karl Schilke (rAT) | rat@NetBSD.org | ||
| Amitai Schlair | schmonz@NetBSD.org | ||
| Konrad Schroder | perseant@NetBSD.org | ||
| Georg Schwarz | schwarz@NetBSD.org | ||
| Lubomir Sedlacik | salo@NetBSD.org | ||
| Christopher SEKIYA | sekiya@NetBSD.org | ||
| Reed Shadgett | dent@NetBSD.org | ||
| John Shannon | shannonjr@NetBSD.org | ||
| Tim Shepard | shep@NetBSD.org | ||
| Takeshi Shibagaki | shiba@NetBSD.org | ||
| Naoto Shimazaki | igy@NetBSD.org | ||
| Takao Shinohara | shin@NetBSD.org | ||
| Takuya SHIOZAKI | tshiozak@NetBSD.org | ||
| Chuck Silvers | chs@NetBSD.org | ||
| Thor Lancelot Simon | tls@NetBSD.org | ||
| Jeff Smith | jeffs@NetBSD.org | ||
| Noriyuki Soda | soda@NetBSD.org | ||
| Wolfgang Solfrank | ws@NetBSD.org | ||
| SOMEYA Yoshihiko | someya@NetBSD.org | ||
| Bill Sommerfeld | sommerfeld@NetBSD.org | ||
| Ignatios Souvatzis | is@NetBSD.org | ||
| Bill Squier | groo@NetBSD.org | ||
| Jonathan Stone | jonathan@NetBSD.org | ||
| Bill Studenmund | wrstuden@NetBSD.org | ||
| Kevin Sullivan | sullivan@NetBSD.org | ||
| SUNAGAWA Keiki | kei@NetBSD.org | ||
| Kimmo Suominen | kim@NetBSD.org | ||
| Shin Takemura | takemura@NetBSD.org | ||
| TAMURA Kent | kent@NetBSD.org | ||
| Shin'ichiro TAYA | taya@NetBSD.org | ||
| Ian Lance Taylor | ian@NetBSD.org | ||
| Matt Thomas | matt@NetBSD.org | ||
| Jason Thorpe | thorpej@NetBSD.org | ||
| Christoph Toshok | toshok@NetBSD.org | ||
| Greg Troxel | gdt@NetBSD.org | ||
| Tsubai Masanari | tsubai@NetBSD.org | ||
| Izumi Tsutsui | tsutsui@NetBSD.org | ||
| UCHIYAMA Yasushi | uch@NetBSD.org | ||
| Masao Uebayashi | uebayasi@NetBSD.org | ||
| Shuichiro URATA | ur@NetBSD.org | ||
| Todd Vierling | tv@NetBSD.org | ||
| Aymeric Vincent | aymeric@NetBSD.org | ||
| Paul Vixie | vixie@NetBSD.org | ||
| Mike M. Volokhov | mishka@NetBSD.org | ||
| Krister Walfridsson | kristerw@NetBSD.org | ||
| Lex Wennmacher | wennmach@NetBSD.org | ||
| Leo Weppelman | leo@NetBSD.org | ||
| Assar Westerlund | assar@NetBSD.org | ||
| Todd Whitesel | toddpw@NetBSD.org | ||
| Nathan Williams | nathanw@NetBSD.org | ||
| Rob Windsor | windsor@NetBSD.org | ||
| Dan Winship | danw@NetBSD.org | ||
| Jim Wise | jwise@NetBSD.org | ||
| Michael Wolfson | mbw@NetBSD.org | ||
| Steve Woodford | scw@NetBSD.org | ||
| Colin Wood | ender@NetBSD.org | ||
| YAMAMOTO Takashi | yamt@NetBSD.org | ||
| Yuji Yamano | yyamano@NetBSD.org | ||
| Reinoud Zandijk | reinoud@NetBSD.org | ||
| S.P.Zeidler | spz@NetBSD.org | ||
| Maria Zevenhoven | maria7@NetBSD.org | ||
| Christos Zoulas | christos@NetBSD.org | ||
|
| |||
| Other contributors: | |||
| Dave Burgess | burgess@cynjut.infonet.net | ||
| Brian R. Gaeke | brg@dgate.org | ||
| Brad Grantham | grantham@tenon.com | ||
| Lawrence Kesteloot | kesteloo@cs.unc.edu | ||
| Waldi Ravens | waldi@moacs.indiv.nl.net |
All product names mentioned herein are trademarks or registered trademarks of their respective owners.
The following notices are required to satisfy the license terms of the software that we have mentioned in this document:
This product includes software developed by the University of
California, Berkeley and its contributors.