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.
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, 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.
NetBSD 1.4.2 is an upgrade of NetBSD 1.4.1, NetBSD 1.4 and earlier releases of NetBSD such as versions 1.3.3, 1.2 etc.
The intermediate development versions of code available on the main trunk in our CVS repository (also known as ``NetBSD-current'') from after the point where the release cycle for 1.4 was started are designated by version identifiers such as 1.4A, 1.4B, 1.4P etc. These identifiers do not designate releases, but indicate major changes in internal kernel APIs. Note that the kernel from NetBSD 1.4.2 can not be used to upgrade a system running one of those intermediate development versions. Trying to use the NetBSD1.4.2 kernel on such a system will in all probability result in problems.
Please also note that it is not possible to do a direct ``version'' comparison between any of the intermediate development versions mentioned above and 1.4.2 to determine if a given feature is present or absent in 1.4.2. The development of 1.4, 1.4.1 and 1.4.2 is done on a separate branch in the CVS repository which was created when the release cylcle for 1.4 was started, and during the release cycles for all these versions selective fixes (with minor impact on the stability of the code on the release branch) have been imported from the main development trunk. So, there are features in 1.4.2 which were not in e.g. 1.4H, but the reverse is also true.
ti(4).
rl(4).
dpt(4).
ioat(4).
mktemp(1).
amd(8)
has been updated to fix a security problem.
In addition, many, many bugs have been fixed -- more than 100 problems reported through our problem tracking system have been fixed, and many other non-reported problems have also been found and fixed. See the CHANGES-1.4.2 file for the complete list.
ipf(8)
caused a change of the kernel API. Thus, if you are using
ipf(8)
you need to upgrade both the kernel and the user-land utilities to
control that feature in order for it to work.
It is impossible to completely summarize the nearly two years of development that went into the NetBSD1.4 release. Some highlights include:
ftp(1)
client has been improved even further. See the man page for details.
wscons(4),
has been integrated into many ports.
usb(4)
for an overview.
nsswitch.conf(5)
functionality to the system to specify the search order for system databases.
syslogd(8)
now supports listening on multiple sockets, to make the
chrooting of servers easier.
As has been noted, there have also been innumerable bug fixes.
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.
There have been many, many Alpha-specific enchancements since the 1.3 release. These include:
NetBSD 1.4.2 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 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. In addition, Anonymous CVS access to the NetBSD source tree has been added since NetBSD 1.4.1; see http://www.netbsd.org/Changes/#anoncvs-available We have also added a browsable CVS repository on the web at http://cvsweb.netbsd.org/cgi-bin/cvsweb.cgi/
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.
.../NetBSD-1.4.2/
BUGSCHANGESLAST_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 NetBSD1.4.2 has a binary distribution. There are also 'README.export-control' files sprinkled liberally throughout the distribution tree, which point out that there are some portions of the distribution (i.e. the `domestic' portion) that may be subject to export regulations of the United States. It is your responsibility to determine whether or not it is legal for you to export these portions and to act accordingly. The NetBSD project maintains a web page at
http://www.NetBSD.ORG/Misc/crypto-export.html
which should contain up-to-date information on this issue.
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:
Most of the above source sets are located in the
source/sets
subdirectory of the distribution tree. The secrsrc.tgz set is
contained in the
source/security
subdirectory. This set, which may only be
available to users in the United States and Canada, contains the
sources normally found in
/usr/src/domestic
- primarily Kerberos and
other cryptographic security related software. (Remember, because of
United States law, it may not be legal to distribute this set to
locations outside of the United States and Canada. Again, see
http://www.NetBSD.ORG/Misc/crypto-export.html
for updated information on this issue.)
The source sets are distributed as compressed tar files. They may be
unpacked into
/usr/src
with the command:
cat set_name.tgz | gunzip | (cd /; tar xpf - )
The sets/Split/
and security/Split/
subdirectories contain 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 are named "set_name.xx" where "set_name" is the
distribution set name, and "xx" 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
distribution set.)
The split distributions may be reassembled and extracted with
cat as follows:
cat set_name.?? | gunzip | (cd /; tar xpf - )
In each of the source distribution set directories, there is a file
named
CKSUMS
which contains the checksums of the files in that
directory, as generated by the
cksum(1)
utility. You can use cksum to
check the integrity of the archives, if you suspect that one of the
files is corrupt and have access to a cksum binary. Checksums based on
other algorithms may also be present - see the
release(7)
man page for details.
alpha
subdirectory of the distribution:
.../NetBSD-1.4.2/alpha/
INSTALL.htmlINSTALL.psINSTALL.txtINSTALL.more.more file contains underlined text using the
more(1)
conventions for indicating italic and bold display.
binary/sets/security/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 filesystem wrappers.
It can be netbooted or diskbooted from a previous installation. Note: there is
no need to ungzip this image.
misc/GENERIC.fs,
a GENERIC
kernel in a bootable filesystem 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:
The alpha security distribution set is named
secr and can be found in the
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:
The alpha binary distribution sets are distributed as gzipped tar files
named with the extension
.tgz, e.g.
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
below
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
tar xfp
command from /.
All BSDSUM
files are historic
BSD checksums for the various files
in that directory, in the format produced by the command:
cksum -o 1 file
All CKSUM files are
POSIX
checksums for the various files in that
directory, in the format produced by the command:
cksum file.
All MD5 files are
MD5
digests for the various files in that
directory, in the format produced by the command:
cksum -m file.
All SYSVSUM
files are historic AT&T System V
UNIX
checksums for the various files in that directory, in the format produced by
the command:
cksum -o -2 file.
The MD5 digest is the safest checksum, followed by the POSIX
checksum. The other two checksums are provided only to ensure
that the widest possible range of system can check the integrity
of the release files.
NetBSD/alpha 1.4.2 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.
Supported devices by bus type are:
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? 0x300 5 memory at D0000-DFFFF
le? 0x200 10 memory 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 0x300 any
lc1 0x320 any
You should enter the following SRM console command to enable the device:
>>> add_de205
A large number of different media types can be used to hold the
binary distribution sets, but they must originally be obtained
from the
NetBSD
project via a mechanism from the list below.
The steps necessary to prepare the distribution sets
for installation depend on which installation medium you choose.
The steps for the various media are outlined below.
You need to know the 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 closest router .
Finally, you need to know the numeric
IP address of the NetBSD machine itself. The install
program will ask you to provide this information to be able
to access the sets.
Once the NFS server is set up properly and you have the
information mentioned above, you can start the actual
installation process.
Once you have this information, you can proceed to the actual
installation.
Place the distribution sets you wish to upgrade somewhere in
your current file system tree. Please note that the
At a bare minimum, you must upgrade the
base
and
kern
binary distribution, and so must put the
base
and
kern
sets somewhere in your file system. If you wish,
you can do the other sets, as well, but you should
not
upgrade the
etc
distribution; it contains system
configuration 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.
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 mainlist by mailing a line saying
If you encounter any problems, please report them via the mailing list or the
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.
The 3.5", 1.44 MB boot floppy set is found under the
NetBSD/alpha 1.4.2 distribution directory in
If you have a Unix system handy, you can do this with commands
like the following:
If the Unix system you are using is not a NetBSD system, you will
probably need to replace
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
Once the floppy has been made, you simply need to put it in the
drive and type
All three of these media types use the same initial image:
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
The gzipped image can be booted directly; it is not necessary to
uncompress it first.
Booting NetBSD/alpha 1.4.2 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:
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
http://www.NetBSD.org/Ports/alpha
At the time of this
release, the URL for the netbooting instructions is:
http://www.netbsd.org/Ports/alpha/netboot.html
You'll want to map root to
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 Micro$oft Window$ 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
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
For the BOOTP server you need to specify the:
Here's an example for a Unix system running bootpd:
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 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:
You should permanently set your protocol to
BOOTP
with:
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:
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 to be completed.
Do not let this discourage you, the install program is not hard
to use.
There is a serious bug that may make installation of
NetBSD
on
PCMCIA
machines difficult. This bug does not make
use
of
PCMCIA
difficult once a machine is installed. 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.
This will explain how to work around the installation problem.
What is the bug: 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 ports.
Unfortunately, not all devices are included in the
This problem will impact some, but not all, users of
PCMCIA.
If this bug 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 hit Control-C
at any time, but if you do, you'll have to begin the installation
process again from scratch.
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 section 3. This section
describes a basic installation, using a CD-ROM install as
an example.
Boot your machine using the boot floppy. The boot loader will
start, and will print a countdown and begin booting.
If the boot loader messages do not appear in a reasonable
amount of time, you either have a bad boot floppy or a
hardware problem. Try writing the install floppy image to
a different disk, and using that.
It will take a while to load the kernel from the floppy,
probably around a minute or so, then, the kernel boot messages
will be displayed. This may take a little while also, as
NetBSD
will be probing your system to discover which hardware devices are
installed.
The most important thing to know is that
Note that, once the system has finished booting, you need not
leave the floppy in the disk drive.
Once
NetBSD
has booted and printed all the boot messages,
you will be presented with a welcome message and a main menu.
It will also include instructions for using the menus.
If you will not use network operation during the installation,
but you do want your machine to be configured for networking once
it is installed, you should first go to the utilities menu, and select
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 Domain Name Service (DNS),
you can give an empty response in reply to answers relating to
this.
To start the installation, select the menu option to install
NetBSD
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
Next, depending on whether you are using a
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.
If you want to use the entire disk for
NetBSD,
you can skip
the following section and go to
Editing the
NetBSD
disklabel.
The partition table of the
NetBSD
part of a disk is called a
disklabel.
There are 3 layouts for the
NetBSD
part of the disk that you can pick from:
Standard, Standard with X
and
Custom.
The first two use a set of default
values (that you can change) suitable for a normal
installation, possibly including X. The last option
lets you specify everything yourself.
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. Partition
a is always the root partition,
b is the swap partition, and
c is the whole disk. Partitions
e-h
are available for other use. Traditionally,
d
is the partition mounted on the
You will then be asked to name your disk's disklabel. The
default response is
mydisk.
For most purposes this will be OK.
If you choose to name it something different, make sure the name
is a single word and contains no special characters. You don't
need to remember this name.
You are now at the point of no return.
Nothing has been
written to your disk yet, but if you confirm that you want to
install
NetBSD,
your hard drive will be modified. If you are
sure you want to proceed, enter
The install program will now label your disk and make the file
systems you specified. The filesystems 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 section 9
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
to provide some data, like IP number, 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,
and the account name and password used to log into that
host using ftp. If you did not set up DNS when answering
the questions to configure networking, you will need to
specify an IP number 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
to provide some data, like IP number, 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 number
instead of a hostname for the NFS server.
When installing from a CD-ROM, you will be asked to specify
the device name for your CD-ROM player
(usually
sysinst
will then check if the files are indeed available
in the specified location, and proceed to the actual
extraction of the sets.
In order to install from a local filesystem, you will
need to specify the device that the filesystem resides
on
(for example
This option assumes that you have already done some preparation
yourself. The sets should be located in a directory on a
filesystem 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.
Congratulations, you have successfully installed
NetBSD1.4.2.
You can now reboot the machine, and boot from harddisk.
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:
If you are reviewing man pages on NetBSD platforms other than
alpha, be sure that when reading
At this point you need only unpack the distribution sets by running
The
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.
Once you've specified this information, the install script will
write the disklabel, install boot blocks to make the disk
bootable, initialise the filesystems, and mount them all under
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
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:
The first thing you need to do is configure the loopback network
interface, which is done with the command
To configure your ethernet card, type
ifconfig if
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
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
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/Sites/net.html
A typical session might be:
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
The sets and kernel are extracted with
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:
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:
You can create the floppy needed for installation
under DOS or Windows. Supposing your 1.44M floppy
drive is drive A:, and your CD is drive
E:,
do the following from an MS-DOS command prompt:
(Repeat the procedure for
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 propperly
configured state, with the most important ones described below.
If you haven't done any configuration of
Other values that need to be set in
Other files in
After reboot, you can log in as
Use the
If you have installed the X window system, look at the files in
Don't forget to add
There is a lot of software freely available for Unix-based systems,
almost all of which can run on
NetBSD.
Modifications are usually needed to
when transferring programs between different Unix-like systems, so
the
NetBSD
packages collection incorporates any such
changes necessary to make that software run on
NetBSD,
and makes
the installation (and deinstallation) of the software packages
easy. There's also the option of building a package from source, in
case there's no precompiled binary available.
Precompiled binaries can be found at
ftp://ftp.netbsd.org/pub/NetBSD/packages/
Package sources for compiling packages can be obtained by
retrieving the file
ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-current/tar_files/pkgsrc.tar.gz
and extracting it into
The upgrade to
NetBSD1.4.2
is a binary upgrade; it can be quite difficult
to advance to a later version by recompiling from source due primarily
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 the old binaries are being overwritten in place, you only need
space for the new binaries, which weren't previously on the system.
If you have a few megabytes free on each of your root and
Since upgrading involves replacing the boot blocks on your
NetBSD
partition, the kernel, 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 your disk,
whether on the
NetBSD
partition or on
another operating system's partition, before beginning the upgrade
process.
The upgrade procedure using the
sysinst tool is similar to
an installation, but without the hard disk partitioning.
Another difference is that existing configuration files in
After a new kernel has been copied to your hard disk, your
machine is a complete
NetBSD1.4.2
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
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
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.
Documentation is available if you first install the manual
distribution set. Traditionally, the
``man pages''
(documentation) are denoted by
``
The section numbers group the topics into several categories, but three
are of primary interest: user commands are in section 1, file formats
are in section 5, and administrative information is in section 8.
The man
command is used to view the documentation on a topic, and is
started by entering
man[ section]
topic.
The brackets
[]
around the
section should not be entered, but rather indicate that the section is
optional. If you don't ask for a particular section, the topic with the
lowest numbered section name will be displayed. For instance, after
logging in, enter
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.
There are various mailing lists set up to deal with comments and
questions about this release. Please send comments to:
netbsd-comments@NetBSD.ORG.
To report bugs, use the
Use of
There are also port-specific mailing lists, to discuss aspects of
each port of
NetBSD.
Use majordomo to find their addresses. 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 somewhere, then mail the appropriate list about it, or, if
you'd rather not do that, mail the list saying you'll send the data
to those who want it.
for their ongoing work on BSD systems, support, and encouragement.
for answering lots of questions, fixing bugs, and doing the various work
they've done.
(in alphabetical order)
ncr(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.
Binary Distribution Sets
The
NetBSD
alpha
binary distribution sets contain the binaries which
comprise the
NetBSD1.4.2
release for the alpha. There are eight binary distribution
sets and the security distribution set.
The binary distribution sets can be found in the
alpha/binary/sets
subdirectory
of the
NetBSD1.4.2
distribution tree, and are as follows:
15.0M gzipped, 40.0M uncompressed
/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.
11.7M gzipped, 49.5M uncompressed
/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. (If you are upgrading,
it's recommended that you get a copy of this set and
carefully
upgrade your configuration files by hand.)
57K gzipped, 360K uncompressed
3M gzipped, 7.4M uncompressed
/netbsd.
You must
install this distribution set.
1.4M gzipped, 3.3M uncompressed
4.1M gzipped, 16.4M uncompressed
/usr/share.
2.2M gzipped, 8.5M uncompressed
groff(1),
all related programs, and their manual pages.
1.3M gzipped, 4.9M uncompressed
alpha/binary/security
subdirectory of the
NetBSD1.4.2
distribution tree. It contains security-related binaries
which depend on cryptographic source code. You do not need this
distribution set to use encrypted passwords in your password file; the
base
distribution includes a crypt library which can perform
only the one-way encryption function. The security distribution
includes a version of the Kerberos IV network security system, and
a Kerberized version of
telnet(1)
program. The secr
distribution set can be found only on those sites which carry the complete
NetBSD
distribution and which can legally obtain it. Because
of United States law, it may not be legal to distribute this set
to locations outside of the United States and Canada. See
http://www.NetBSD.ORG/Misc/crypto-export.html
for updated information on this issue.
1M gzipped, 3M uncompressed
3.4M gzipped 12.9M uncompressed
2.5M gzipped, 13.2M uncompressed
229k gzipped, 830k uncompressed
5.6M gzipped, 6.8M uncompressed
base.tgz.
NetBSD/alpha System Requirements and Supported Devices
Cyclades Cyclom-Y serial boards (cy, UNTESTED)
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]
Getting the NetBSD System on to Useful Media
/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.)
/dev
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.
Preparing your System for NetBSD Installation
Installing the NetBSD System
subscribe port-alpha
to
majordomo@netsbd.org.
Also, see
http://www.netbsd.org
for more information.
send-pr(1)
program so that they can be fixed for the next release.
alpha/installation/floppy/
as two files called
disk1of2
and
disk2of2.
You need to put these two disk images on two floppy disks.
dd if=disk1of2 of=/dev/rfd0a bs=18k
dd if=disk2of2 of=/dev/rfd0a bs=18k
/dev/rfd0a
with the name of the floppy device on your particular system.
i386/installation/misc;
a documentation file,
rawrite.doc
is available there as well.
>>> B DVA0
.../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!
instkernel/
contains
netbsd.gz;
this is the same install kernel but without a bootable filesystem
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.
/netbsd.
/dev
with
sh ./MAKEDEV all.
Detailed instructions on netbooting can be found by visiting the
NetBSD
Alpha platform page:
root
(rather than the default
nobody)
when you export your root filesystem. A typical
/etc/exports
line on a NetBSD system would be:
/usr/export/alpha -maproot=0 myclient.mydom.com
instkernel
image from the distribution.
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.
And here's an example for a Unix system running the ISC dhcpd:
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:
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";
}
>>> boot -proto bootp ewa0
>>> set ewa0_protocols bootp
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
Running the Sysinst Installation Program
INSTALL
kernels in order to save space. Let's say 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. This
is especially bad if one of the devices in question is your
ethernet card.
>>> B DVA0
The main menu will be displayed.
root,
and set a password for that account. You are also
advised to edit the file
/etc/rc.conf to match your system needs.
/usr/X11R6/lib/X11/doc.
Further information can be found on
http://www.xfree86.org/
wd0
is NetBSD's name for your first IDE disk,
wd1
the second, etc.
sd0
is your first SCSI disk,
sd1
the second, etc.
wd0,
wd1,
sd0,
or
sd1.
wdx
or
wdx
disk,
you will either be asked for the type of disk
(wdx)
you are
using or you will be asked if you want to specify a fake geometry
for your SCSI disk
(sdx).
The types of disk are be
IDE, ST-506
or
ESDI.
If you're installing on an
ST-506
or
ESDI
drive, you'll be asked if your disk supports automatic sector forwarding.
If you are
sure
that it does, reply affirmatively. Otherwise, the install
program will automatically reserve space for bad144 tables.
/usr
directory, but this is historical practice, not a fixed value.
yes
at the prompt.
cd0),
and the directory name on the CD-ROM where the distribution files are.
wd1e)
the type of the filesystem,
and the directory on the specified filesystem where the sets are located.
sysinst
will then check if it
can indeed access the sets at that location.
Manual and Script-Assisted Installation
All of the installation procedures consist of
putting a label on the disk to provide information on
the sizes and placement of the partitions into which the disk
is divided, putting the boot blocks on the disk, creating the
filesystems on the partitions, and unpacking the distribution
tar archives.
/etc/disktab,
see
disktab(5)
disklabel(8),
newfs(8)
mount(8)
the new root on
/mnt
/usr/mdec
and run
installboot(8)
installboot(8)
you read the alpha
version by typing: "man 8 alpha/installboot".
tar(1)
as described below.
/install
and
/upgrade
traditional installation scripts
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.
/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.
/mnt.
You are now ready to go on to the next step.
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 necesary tar files.
mount -r -t cd9660 /dev/cd0a /mnt2
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).
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
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.
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.
[the following commmands are given to the ftp program
after logging in]
mkdir /mnt/usr/release
cd /mnt/usr/release
ftp ftp.netbsd.org
prompt
cd /pub/NetBSD/NetBSD-1.4.2/alpha/binary/sets
mget *
bye
/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.
or perhaps:
cd /mnt
for i in base kern comp etc games man misc text; do
tar xpzf /mnt/usr/release/$i.tgz;
done
Now make the device nodes:
cd /mnt
for i in /mnt/usr/release/*.tgz; do
echo $i
tar xpzf $i
done
cd /mnt/dev
sh ./MAKEDEV all
cd /
umount /mnt/usr
umount /mnt
sync # not needed but traditional
halt
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.
e:
cd \NetBSD-1.4.2\installation\misc
rawrite
When asked for a source filename, answer
...\floppy\disk1of2
When asked for a destination drive answer
a
installation/floppy/disk2of2.)
Post installation steps
/etc/rc.conf
/etc/rc.conf,
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 filesystem mounted read-write. When the system
asks you to choose a shell, simply hit return to get to a
prompt. If you are asked for a terminal type, respond with
vt220
(or whatever is appropriate for your terminal type)
and hit return. At this point, you need to configure at least
one file in the
/etc directory. 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. If your
/usr directory is on a separate partition
and you do not know how to use 'ed' or 'ex', you will have to mount your
/usr
partition to gain access to 'vi'. Do the following:
mount /usr
export TERM=vt220
If you have
/var
on a seperate partition, you need to repeat
that step for it. After that, you can edit
/etc/rc.conf
with
vi(1).
When you have finished, type
exit
at the prompt to
leave the single-user shell and continue with the multi-user boot.
/etc/rc.conf
for a networked environment are
hostname and possibly
defaultroute,
furthermore add an
ifconfig_int
for your interface
<int>,
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.
/etc
that are new to NetBSD 1.4 and may require modification or
setting up include
/etc/mailer.conf,
/etc/nsswitch.conf
and
/etc/wscons.conf.
root
at the login prompt. There
is no initial password, but 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.
vipw(8)
command to add accounts to your system,
do not edit /etc/passwd
directly. See
adduser(8)
for more information on the process of how to add a new user to the system.
/usr/X11R6/lib/X11/doc
for information.
/usr/X11R6/bin
to your path in your shell's dot file so that you have access to the X binaries.
/usr/pkgsrc.
See
/usr/pkgsrc/README
then for more information.
/etc/localtime
symlink to the appropriate file under
/usr/share/zoneinfo.
/etc/aliases
to forward root mail to the right place (run
newaliases(1)
afterwards.)
/etc/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.
/etc/rc.local
to run any local daemons you use.
/etc
files are documented in section 5 of the manual; so just invoking
man filename
is likely to give you more information on these files.
Upgrading a previously-installed NetBSD System
/usr
partitions, you should have enough space.
/etc
are backed up and merged with the new files. 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.
filesystems are checked before unpacking the sets.
/dev.
If you've changed the contents of
/dev
by hand, you will need to be careful about this, but if
not, you can just cd into
/dev, and run the command
sh MAKEDEV all
/etc/fstab
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 systems' mount commands, for example
mount_nfs(8)
for NFS.
Compatibility Issues With Previous NetBSD Releases
Users upgrading from previous versions of
NetBSD
may wish to bear the
following problems and compatibility issues in mind when upgrading to
NetBSD1.4.2
/usr/include/machine
directory changed to a symbolic link in NetBSD 1.4.
# rm -r /usr/include/machine
to remove the old directory and it contents and reinstall the
comp
set.
Using online NetBSD documentation
name(section)''.
Some examples of this are
intro(1),
man(1),
apropros(1),
passwd(1),
and
passwd(5).
man passwd
to read the documentation for
passwd(1).
To view the documentation for
passwd(5)m
enter
man 5 passwd
instead.
Administrivia
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.
send-pr(1)
command shipped with
NetBSD,
and fill in as much information about the problem as you can. Good
bug reports include lots of details. Additionally, bug reports can
be sent by mail to:
netbsd-bugs@NetBSD.ORG.
send-pr(1)
is encouraged, however, because bugs reported with it
are entered into the
NetBSD
bugs database, and thus can't slip through
the cracks.
Thanks go to
Keith Bostic
Ralph Campbell
Mike Karels
Marshall Kirk McKusick
Mike Hibler
Rick Macklem
Jan-Simon Pendry
Chris Torek
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
Soren Jorvang
Scott Kaplan
Noah M. Keiserman
John Kohl
Chris Legrow
Ted Lemon
Neil J. McRae
Perry E. Metzger
Herb Peyerl
Mike Price
Dave Rand
Michael Richardson
Heiko W. Rupp
Brad Salai
Chuck Silvers
Thor Lancelot Simon
Bill Sommerfeld
Paul Southworth
Ted Spradley
Kimmo Suominen
Jason R. Thorpe
Steve Wadlow
Krister Walfridsson
Jim Wise
Christos Zoulas
(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.)
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
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.
VMC Harald Frank, Germany
Warped Communications, Inc.
We are...
| The NetBSD core group: | ||||||||
| Alistair Crooks | agc@NetBSD.ORG | |||||||
| Jun-ichiro itojun Hagino | itojun@NetBSD.ORG | |||||||
| Frank van der Linden | fvdl@NetBSD.ORG | |||||||
| Luke Mewburn | lukem@NetBSD.ORG | |||||||
| Christos Zoulas | christos@NetBSD.ORG | |||||||
|
| ||||||||
| The portmasters (and their ports): | ||||||||
| Mark Brinicombe | mark@NetBSD.ORG | arm32 | ||||||
| Jeremy Cooper | jeremy@NetBSD.ORG | sun3x | ||||||
| Ross Harvey | ross@NetBSD.ORG | alpha | ||||||
| Ignatios Souvatzis | is@NetBSD.ORG | amiga | ||||||
| Jun-ichiro itojun Hagino | itojun@NetBSD.ORG | sh3 | ||||||
| Eduardo Horvath | eeh@NetBSD.ORG | sparc64 | ||||||
| Paul Kranenburg | pk@NetBSD.ORG | sparc | ||||||
| Anders Magnusson | ragge@NetBSD.ORG | vax | ||||||
| Tsubai Masanari | tsubai@NetBSD.ORG | macppc | ||||||
| Tsubai Masanari | tsubai@NetBSD.ORG | newsmips | ||||||
| Minoura Makoto | minoura@NetBSD.ORG | x68k | ||||||
| Phil Nelson | phil@NetBSD.ORG | pc532 | ||||||
| Scott Reynolds | scottr@NetBSD.ORG | mac68k | ||||||
| Darrin Jewell | dbj@NetBSD.ORG | next68k | ||||||
| Kazuki Sakamoto | sakamoto@NetBSD.ORG | bebox | ||||||
| Wolfgang Solfrank | ws@NetBSD.ORG | ofppc | ||||||
| Jonathan Stone | jonathan@NetBSD.ORG | pmax | ||||||
| Shin Takemura | takemura@NetBSD.ORG | hpcmips | ||||||
| Jason Thorpe | thorpej@NetBSD.ORG | hp300 | ||||||
| Frank van der Linden | fvdl@NetBSD.ORG | i386 | ||||||
| Leo Weppelman | leo@NetBSD.ORG | atari | ||||||
| Nathan Williams | nathanw@NetBSD.ORG | sun3 | ||||||
| Steve Woodford | scw@NetBSD.ORG | mvme68k | ||||||
|
| ||||||||
| The NetBSD 1.4.2 Release Engineering team: | ||||||||
| Chris G. Demetriou | cgd@NetBSD.ORG | |||||||
| Havard Eidnes | he@NetBSD.ORG | |||||||
| Ted Lemon | mellon@NetBSD.ORG | |||||||
| Perry Metzger | perry@NetBSD.ORG | |||||||
| Curt Sampson | cjs@NetBSD.ORG | |||||||
|
| ||||||||
| Developers and other contributors: | ||||||||
| Steve Allen | wormey@NetBSD.ORG | |||||||
| Julian Assange | proff@NetBSD.ORG | |||||||
| Lennart Augustsson | augustss@NetBSD.ORG | |||||||
| Christoph Badura | bad@NetBSD.ORG | |||||||
| Robert V. Baron | rvb@NetBSD.ORG | |||||||
| Erik Berls | cyber@NetBSD.ORG | |||||||
| John Birrell | jb@NetBSD.ORG | |||||||
| Mason Loring Bliss | mason@NetBSD.ORG | |||||||
| Manuel Bouyer | bouyer@NetBSD.ORG | |||||||
| John Brezak | brezak@NetBSD.ORG | |||||||
| Allen Briggs | briggs@NetBSD.ORG | |||||||
| Aaron Brown | abrown@NetBSD.ORG | |||||||
| David Brownlee | abs@NetBSD.ORG | |||||||
| Frederick Bruckman | fredb@NetBSD.ORG | |||||||
| Jon Buller | jonb@NetBSD.ORG | |||||||
| Simon Burge | simonb@NetBSD.ORG | |||||||
| Dave Burgess | burgess@cynjut.infonet.net | |||||||
| Robert Byrnes | byrnes@NetBSD.org | |||||||
| D'Arcy J.M. Cain | darcy@NetBSD.ORG | |||||||
| Dave Carrel | carrel@NetBSD.ORG | |||||||
| Bill Coldwell | billc@NetBSD.ORG | |||||||
| Julian Coleman | jdc@NetBSD.ORG | |||||||
| Chuck Cranor | chuck@NetBSD.ORG | |||||||
| Aidan Cully | aidan@NetBSD.ORG | |||||||
| Johan Danielsson | joda@NetBSD.ORG | |||||||
| Matt DeBergalis | deberg@NetBSD.ORG | |||||||
| Rob Deker | deker@NetBSD.ORG | |||||||
| Chris G. Demetriou | cgd@NetBSD.ORG | |||||||
| Jaromir Dolecek | jdolecek@NetBSD.ORG | |||||||
| Andy Doran | ad@NetBSD.ORG | |||||||
| Roland Dowdeswell | elric@NetBSD.ORG | |||||||
| Matthias Drochner | drochner@NetBSD.ORG | |||||||
| Jun Ebihara | jun@NetBSD.ORG | |||||||
| Havard Eidnes | he@NetBSD.ORG | |||||||
| Enami Tsugutomo | enami@NetBSD.ORG | |||||||
| Bernd Ernesti | veego@NetBSD.ORG | |||||||
| Erik Fair | fair@NetBSD.ORG | |||||||
| Hubert Feyrer | hubertf@NetBSD.ORG | |||||||
| Thorsten Frueauf | frueauf@NetBSD.ORG | |||||||
| Castor Fu | castor@NetBSD.ORG | |||||||
| Brian R. Gaeke | brg@dgate.org | |||||||
| Thomas Gerner | thomas@NetBSD.ORG | |||||||
| Simon J. Gerraty | sjg@NetBSD.ORG | |||||||
| Justin Gibbs | gibbs@NetBSD.ORG | |||||||
| Adam Glass | glass@NetBSD.ORG | |||||||
| Michael Graff | explorer@NetBSD.ORG | |||||||
| Brian C. Grayson | bgrayson@NetBSD.ORG | |||||||
| Brad Grantham | grantham@tenon.com | |||||||
| Matthew Green | mrg@NetBSD.ORG | |||||||
| Juergen Hannken-Illjes | hannken@NetBSD.ORG | |||||||
| Charles M. Hannum | mycroft@NetBSD.ORG | |||||||
| Eric Haszlakiewicz | erh@NetBSD.ORG | |||||||
| HAYAKAWA Koichi | haya@NetBSD.ORG | |||||||
| Rene Hexel | rh@NetBSD.ORG | |||||||
| Michael L. Hitch | mhitch@NetBSD.ORG | |||||||
| Christian E. Hopps | chopps@NetBSD.ORG | |||||||
| Ken Hornstein | kenh@NetBSD.ORG | |||||||
| Marc Horowitz | marc@NetBSD.ORG | |||||||
| Dean Huxley | dean@netbsd.org | |||||||
| ITOH Yasufumi | itohy@NetBSD.ORG | |||||||
| Matthew Jacob | mjacob@NetBSD.ORG | |||||||
| Lonhyn T. Jasinskyj | lonhyn@NetBSD.ORG | |||||||
| Chris Jones | cjones@NetBSD.ORG | |||||||
| Soren Jorvang | soren@NetBSD.ORG | |||||||
| Antti Kantee | pooka@NetBSD.ORG | |||||||
| Lawrence Kesteloot | kesteloo@cs.unc.edu | |||||||
| Thomas Klausner | wiz@NetBSD.ORG | |||||||
| Klaus Klein | kleink@NetBSD.ORG | |||||||
| John Kohl | jtk@NetBSD.ORG | |||||||
| Kevin Lahey | kml@NetBSD.ORG | |||||||
| Johnny C. Lam | jlam@NetBSD.ORG | |||||||
| Martin J. Laubach | mjl@NetBSD.ORG | |||||||
| Ted Lemon | mellon@NetBSD.ORG | |||||||
| Joel Lindholm | joel@NetBSD.ORG | |||||||
| Mike Long | mikel@NetBSD.ORG | |||||||
| Warner Losh | imp@NetBSD.ORG | |||||||
| Brett Lymn | blymn@NetBSD.ORG | |||||||
| Paul Mackerras | paulus@NetBSD.ORG | |||||||
| Dan McMahill | dmcmahill@NetBSD.ORG | |||||||
| Neil J. McRae | neil@NetBSD.ORG | |||||||
| Perry Metzger | perry@NetBSD.ORG | |||||||
| der Mouse | mouse@NetBSD.ORG | |||||||
| Joseph Myers | jsm@NetBSD.ORG | |||||||
| Ken Nakata | kenn@NetBSD.ORG | |||||||
| Bob Nestor | rnestor@NetBSD.ORG | |||||||
| Tohru Nishimura | nisimura@NetBSD.ORG | |||||||
| Masaru Oki | oki@NetBSD.ORG | |||||||
| Greg Oster | oster@NetBSD.ORG | |||||||
| Herb Peyerl | hpeyerl@NetBSD.ORG | |||||||
| Matthias Pfaller | matthias@NetBSD.ORG | |||||||
| Dante Profeta | dante@NetBSD.ORG | |||||||
| Chris Provenzano | proven@NetBSD.ORG | |||||||
| Waldi Ravens | waldi@moacs.indiv.nl.net | |||||||
| Darren Reed | darrenr@NetBSD.ORG | |||||||
| Michael Richardson | mcr@NetBSD.ORG | |||||||
| Tim Rightnour | garbled@NetBSD.ORG | |||||||
| Gordon Ross | gwr@NetBSD.ORG | |||||||
| Heiko W. Rupp | hwr@NetBSD.ORG | |||||||
| SAITOH Masanobu | msaitoh@NetBSD.ORG | |||||||
| Curt Sampson | cjs@NetBSD.ORG | |||||||
| Wilfredo Sanchez | wsanchez@NetBSD.ORG | |||||||
| Ty Sarna | tsarna@NetBSD.ORG | |||||||
| SATO Kazumi | sato@NetBSD.ORG | |||||||
| Matthias Scheler | tron@NetBSD.ORG | |||||||
| Karl Schilke (rAT) | rat@NetBSD.ORG | |||||||
| Konrad Schroder | perseant@NetBSD.ORG | |||||||
| Tim Shepard | shep@NetBSD.ORG | |||||||
| Takao Shinohara | shin@NetBSD.ORG | |||||||
| Chuck Silvers | chs@NetBSD.ORG | |||||||
| Thor Lancelot Simon | tls@NetBSD.ORG | |||||||
| Noriyuki Soda | soda@NetBSD.ORG | |||||||
| Bill Sommerfeld | sommerfeld@NetBSD.ORG | |||||||
| Bill Studenmund | wrstuden@NetBSD.ORG | |||||||
| Kevin Sullivan | sullivan@NetBSD.ORG | |||||||
| Kimmo Suominen | kim@NetBSD.ORG | |||||||
| Matt Thomas | matt@NetBSD.ORG | |||||||
| Christoph Toshok | toshok@NetBSD.ORG | |||||||
| Izumi Tsutsui | tsutsui@NetBSD.ORG | |||||||
| UCHIYAMA Yasushi | uch@NetBSD.ORG | |||||||
| Todd Vierling | tv@NetBSD.ORG | |||||||
| Aymeric Vincent | aymeric@NetBSD.ORG | |||||||
| Paul Vixie | vixie@NetBSD.ORG | |||||||
| Krister Walfridsson | kristerw@NetBSD.ORG | |||||||
| Lex Wennmacher | wennmach@NetBSD.ORG | |||||||
| Assar Westerlund | assar@NetBSD.ORG | |||||||
| Rob Windsor | windsor@NetBSD.ORG | |||||||
| Dan Winship | danw@NetBSD.ORG | |||||||
| Jim Wise | jwise@NetBSD.ORG | |||||||
| Colin Wood | ender@NetBSD.ORG | |||||||
This product includes software developed by the University of
California, Berkeley and its contributors.
This product includes software developed by the Computer
Systems Engineering Group at Lawrence Berkeley Laboratory.
This product includes software developed by the NetBSD
Foundation, Inc. and its contributors.
This product includes software developed by Adam Glass
and Charles Hannum.
This product includes software developed by Adam Glass.
This product includes software developed by Berkeley Software
Design, Inc.
This product includes software developed by Charles D. Cranor
and Washington University.
This product includes software developed by Charles D. Cranor.
This product includes software developed by Charles Hannum,
by the University of Vermont and State Agricultural College
and Garrett A. Wollman, by William F. Jolitz, and by the
University of California, Berkeley, Lawrence Berkeley Laboratory,
and its contributors.
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 product includes software developed by Christopher G. Demetriou.
This product includes software developed by Christos Zoulas.
This product includes software developed by David Jones and Gordon Ross.
This product includes software developed by Dean Huxley.
This product includes software developed by Eric S. Hvozda.
This product includes software developed by Ezra Story.
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 Herb Peyerl.
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 developed by Jochen Pohl
for The NetBSD Project.
This product includes software developed by John Polstra.
This product includes software developed 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 product includes software developed by Kenneth Stailey.
This product includes software developed by Leo Weppelman.
This product includes software developed by Lloyd Parkes.
This product includes software developed by Mark Brinicombe.
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 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 Scott Bartram.
This product includes software developed by SigmaSoft, Th. Lockert.
This product includes software developed by Terrence R. Lambert.
This product includes software developed by Theo de Raadt
and John Brezak.
This product includes software developed by Theo de Raadt.
This product includes software developed by TooLs GmbH.
This product includes software developed by Winning Strategies, Inc.
This product includes software developed by the Center for
Software Science at the University of Utah.
This product includes software developed by the University 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 software 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 Project
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 includes 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 developed for the NetBSD Project
by Ted Lemon.
This product includes software developed by LAN Media Corporation
and its contributors.
This product includes software developed by Michael Graff for
the NetBSD Project.
This product includes software developed by Niklas Hallqvist,
C Stone and Job de Haas.
This product includes software developed by Charles Hannum.
This product includes software developed by Charles Hannum, by
the University of Vermont and State Agricultural College and
Garrett A. Wollman, by William F. Jolitz, and by the
University of California, Berkeley, Lawrence Berkeley
Laboratory, 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 by Dean Huxley.
This product includes software developed by Herb Peyerl.
In the following statement, "This software" refers to the parallel
port driver:
This software is a component of "386BSD" developed by
William F. Jolitz, TeleMuse.