INSTALL.
ext,
where
ext
is one of
.ps
, .html
, .more
,
or
.txt
.
.ps
.html
.more
more(1)
and
less(1)
pager utility programs. This is the format in which the on-line
man
pages are generally presented.
.txt
You 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.3 is an upgrade of NetBSD 1.4.2, 1.4.1, NetBSD 1.4 and earlier major and patch 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.3 can not be used to upgrade a system running one of those intermediate development versions. Trying to use the NetBSD1.4.3 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.3 to determine if a given feature is present or absent in 1.4.3. The development of 1.4 and the subsequent patch or ``point'' releases 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 cycle of 1.4 and its patch releases, selective fixes have been imported from the main development trunk (the intent is to only import fixes with no or minor impact on the stability of the release branch). So, there are features in 1.4.3 which were not in e.g. 1.4H, but the reverse is also true.
wi(4)
.
ti(4)
.
pciide(4.)
In addition, many bugs have been fixed -- more than 40 problems reported through our problem tracking system have been fixed, and some other non-reported problems have also been found and fixed. See the CHANGES-1.4.3 file for the complete list.
issetugid(2)
.
This means that you
will
have to upgrade the kernel before installing the new user-land
code.
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.
NetBSD/arm32 1.4.3 has a number of improvements over the last release.
Support has been added for the following hardware platforms:
Additionally there has also been:
NetBSD1.4.3 on arm32 is, as usual, also fully backward compatible with old NetBSD arm32 binaries, so you don't need to recompile all your local programs provided you set the appropriate binary compatibility options in your kernel configuration.
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.3/
BUGS
CHANGES
LAST_MINUTE
MIRRORS
README.files
TODO
patches/
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.3 has a binary distribution. There are also 'README.export-control' files sprinkled liberally throughout the distribution tree, which spell out the current restrictions related to export of this code from the United States of America. Note that these regulations were recently changed so that most countries can import the entire release without significant restrictions. See
http://www.NetBSD.ORG/Misc/crypto-export.html
which contains 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 contains the
sources normally found in
/usr/src/domestic
- primarily Kerberos (version 4) and
other cryptographic security related software.
This code can now be exported from the US to most countries.
The document on
http://www.NetBSD.ORG/Misc/crypto-export.html
spells out the current (rather lenient) restrictions applicable for
the export of this code.
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.
arm32
subdirectory of the distribution:
.../NetBSD-1.4.3/arm32/
INSTALL.html
INSTALL.ps
INSTALL.txt
INSTALL.more
.more
file contains underlined text using the
more(1)
conventions for indicating italic and bold display.
binary/
sets/
security/
installation/
kernels/
arm32/binary/sets
subdirectory
of the
NetBSD1.4.3
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. (If you are upgrading,
it's recommended that you get a copy of this set and
carefully
upgrade your configuration files by hand.)
/usr/share
.
groff(1)
,
all related programs, and their manual pages.
The arm32 security distribution set is named
secr and can be found in the
arm32/binary/security
subdirectory of the
NetBSD1.4.3
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.
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 arm32 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 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/arm32 1.4.3 runs on a number of systems with
ARM6
or later processors,
with or without FPU coprocessor. The minimal configuration is said to
require 8M of RAM and 50M of disk space, though we do not know of anyone
running with a system quite this minimal today. To install the entire
system requires much more disk space (the unpacked binary distribution,
without sources, requires at least 65M without counting space needed for
swap space, etc), and to run X or compile the system, more RAM is
recommended. (8M of RAM will actually allow you to run X and/or compile,
but it won't be speedy. Note that until you have around 16M of RAM,
getting more RAM is more important than getting a faster CPU.)
Supported devices include (but is not limited to):
SCSI host adapters:
Cumana SCSI 2.
PowerTec SCSI 2.
MCS Connect32 SCSI 2.
Acorn SCSI.
Oak SCSI I.
Morley SCSI I (uncached only).
VIDC20 video.
RiscPC Motherboard serial port.
RiscPC Motherboard parallel port.
Ethernet adapters:
Acorn Ether1.
Atomwide Ether3.
ANT Ether3.
ANT Ether5.
Atomwide EtherA.
ANT EtherB.
Acorn EtherH.
I-cubed EtherH.
ANT EtherM.
Most SCSI disk drives.
Most SCSI tape drives.
CD-ROM drives:
Most SCSI CD-ROM drives.
Most ATAPI CD-ROM drives.
[ Note: Some low-priced IDE CDROM drives are known
for being not or not fully ATAPI compliant, and thus
requires some hack (generally an entry to a quirk
table) to work with NetBSD.]
Mice:
RiscPC quadrature mouse.
A7000 PS/2 mouse.
Processors:
ARM 610.
ARM 700.
ARM 700 + FPA11.
ARM 710.
ARM 7500.
ARM 7500FE.
ARM 810. [*]
SA110.
Motherboards:
Acorn RiscPC.
Acorn A7000.
Acorn A7000+.
VLSI RC7500.
Digital DNARD.
Intel EBSA285.
Chalice CATS.
Other devices:
RiscPC keyboard.
A7000 keyboard.
RiscPC realtime clock.
VLSI RC7500 motherboard devices.
Digital DNARD devices
IDE
keyboard
mouse
ethernet
smartcard
audio
joystick
Chalice CATS devices
ALI M1543 southbridge inc PS/2 keyboard & mouse, ide, serial
parallel, USB and ISA bus
RTC
Intel EBSA285 & Chalice CATS PCI devices
PCI - PCI bridges
DC21150
DC21152
DC21153
DC21154
Hint HB1
Digital DC21x4x-based PCI Ethernet adapters, including:
Cogent EM1X0, EM960 (a.k.a. Adaptec ANA-69XX)
Cogent EM964 [b]
Cogent EM4XX [b]
Compex Readylink PCI
DANPEX EN-9400P3
Digital Celebris GL, GLST on-board ethernet
Digital (DEC) PCI Ethernet/Fast Ethernet adapters (all)
JCIS Condor JC1260
Linksys PCI Fast Ethernet
SMC EtherPower 10, 10/100 (PCI only!)
SMC EtherPower
SVEC PN0455
SVEC FD1000-TP
Znyx ZX34X
Qlogic ISP [12]0x0 SCSI/FibreChannel boards
Adaptec AHA-2x4x[U][W] cards using the AIC-7770, AIC-7850,
AIC-7860, AIC-7870, or AIC-7880 chip.
NE2000 PCI ethernet adapters
Universal Serial Bus:
UHCI host controllers
OHCI host controllers
Hubs
Keyboards using the boot protocol
Mice
Printers
Generic support for HID devices
Video cards
Diamond Stealth 3D 2000 Pro
ATI Charger 4MB
STB Velocity 128
Cirrus Logic 5446
IGS 2010
IGS 5000
S3 based interfaces
Drivers for hardware marked with "[*]" are NOT present in installation
kernels.
Other PCI device may be supported by Intel EBSA285 & Chalice CATS but
have not been tested.
Support for some devices is limited to particular kernels. eg there is no
SA110 support in A7000 kernels.
Hardware the we do NOT currently support, but get many questions
about:
Drivers are planned for some of the above devices.
Installation is supported from several media types, including:
No matter which installation medium you choose, you'll need to have an
installation kernel and possibly a boot application, see
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.
The distribution sets for
installation or upgrade depend on which installation medium you
choose. The steps for the various media are outlined below.
Find out where the distribution set files are on the CDROM.
Proceed to the instruction on installation.
Count the number of "set_name.xx" files that make up the
distribution sets you want to install or upgrade. You will
need that number of 1.44M floppies.
Format all of the floppies with DOS. DO NOT make any of them
bootable DOS floppies. (If the floppies are bootable, then
the 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 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 DOS disks.
Once you have the files on 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.
To install NetBSD from a tape, you need to make a tape that
contains the distribution set files, in "tar" format. If
you're making the tape on a UN*X-like system, the easiest way
to do so is probably something like:
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.
Place the NetBSD distribution sets you wish to install into a
directory on an NFS server, and make that directory mountable
by the machine on which you are installing or upgrading NetBSD.
This will probably require modifying the /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 the numeric IP address of the NFS server,
and, if the server is not on a network directly connected to
the machine on which you're installing or upgrading NetBSD,
you need to know the numeric IP address of the router closest
to the NetBSD machine. Finally, you need to know the numeric
IP address of the NetBSD machine 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.
The preparations for this installation/upgrade method are
easy; all you make sure that there's some FTP site from which
you can retrieve the NetBSD distribution when you're about to
install or upgrade. You need to know the numeric IP address
of that site, and, if it's not on a network directly connected
to the machine on which you're installing or upgrading NetBSD,
you need to know the 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 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.
Place the distribution sets you wish to upgrade somewhere in
your current file system tree.
Please note that the /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.
At a bare minimum, you must upgrade the "base" binary
distribution, and so must put the "base" set somewhere in
your file system. If you wish, you can do the other sets, as
well, but you should NOT upgrade the "etc" distribution; the
"etc" distribution 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.
First and foremost, before beginning the installation process,
make sure you have a reliable backup
of any data on your hard disk that you
wish to keep. Repartitioning your hard disk is an excellent way to
destroy important data.
Second, read and perform the instructions in
Finally, when you are happy with your
NetBSD
installation, do whatever
is necessary to restore order to the partition you took space away from.
This will most likely involve restoring files, but might involve some
other
``house-work''.
Your hard disk is now prepared to have
NetBSD
installed on it, and you should proceed with the installation instructions.
Installing
NetBSD
is a relatively complex process, but if you have
this document in hand and are careful to read and remember the
information which is presented to you by the install program, it
shouldn't be too much trouble.
Before you begin, you should know the geometry of your hard disk, i.e.
the sector size (note that sector sizes other than 512 bytes are not
currently supported), the number of sectors per track, the number of
tracks per cylinder (also known as the number of heads), and the
number of cylinders on the disk. The
NetBSD
kernel will try to
discover these parameters on its own, and if it can it will print them
at boot time. If possible, you should use the parameters it prints.
(You might not be able to because you're sharing your disk with
another operating system, or because your disk is old enough that the
kernel can't figure out its geometry.)
If
NetBSD
will be sharing the disk with RiscOS or another operating
system, you should have already completed the section of these notes
that instructed you on how to prepare your hard disk. You should know
the size of the
NetBSD
area of the disk and its offset from the
beginning of the disk. You will need this information when setting up
your
NetBSD
partitions.
You should now be ready to install NetBSD. It might be handy for you
to have a pencil, some paper, and a calculator handy.
The following is a walk-through of the steps you will take while
getting
NetBSD
installed on your hard disk. If any question has a
default answer, it will be displayed in brackets ("[]") after the
question. If you wish to stop the installation, you may hit Control-C
at any time, but if you do, you'll have to begin the installation
process again from scratch.
Boot your machine using the installation kernel for your
platform. (Instructions for doing this on your platform can be
found in the preparation section of this document.)
If this doesn't work, ensure that you're using the correct
kernel for your hardware.
Depending upon your platform and the method of loading the,
it may take a while to load the kernel.
You will then be presented with the
NetBSD
kernel boot
messages. You will want to read them, to determine your
disk's name and geometry. Its name will be something like
"sd0" or "wd0" and the geometry will be printed on a line that
begins with its name. As mentioned above, you will need your
disk's geometry when creating NetBSD's partitions. You will
also need to know the name, to tell the install tools what
disk to install on.
While booting, you will probably see several warnings. You
should be warned that no swap space is present, and that
init(8) cannot find
You will be asked if you wish to install or upgrade your
system or go to a shell prompt. Enter
install.
You will be presented with a welcome message and a prompt,
asking if you wish to proceed with the installation process.
If you wish to proceed, enter
y
and hit return.
You will be asked what type of disk driver you have. The
valid options are listed by the install program, to make sure
you get it right.
The install program will then tell you which disks of that
type it can install on, and ask you which it should use.
Reply with the name of your disk. (The first disk of the type
you selected, either "wd0" for IDE disks, or "sd0" for SCSI
disks, is the default.)
You will then be asked to name your disk's disklabel. The
default response is "mywd" or "mysd" depending on the type of
your disk, and for most purposes it 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 will be prompted for your disk's geometry information,
i.e. the number of bytes per sector, cylinders on the disk,
tracks per cylinder (heads), and sectors per track. Enter
them when they are requested. If you make a mistake, hit
Control-C and when you get to the shell prompt, restart the
install process by running the
install
command. Once you
have entered this data, the install program will tell you the
total size of your disk, in both sectors, and cylinders.
Remember this number; if you're installing on the whole disk,
you'll need it again soon.
When describing your partitions, you will have the option of
entering data about them in units of disk sectors or
cylinders. If you choose to enter the information in units of
sectors, remember that, for optimal performance, partitions
should begin and end on cylinder boundaries. You will be
asked about which units you wish to use, and you should reply
with "c" for cylinders, or "s" for sectors.
You will be asked for the size of the
NetBSD
portion of the
disk. If you're installing on the whole disk, reply with the
size of the disk, as printed earlier by the install program.
If you're using only part of the disk, reply with the size
that you specified in the partition editor. (Don't forget to
enter the size in the units you specified in the last step!)
If you are not installing on the whole disk, you will be asked
for the offset of the
NetBSD
partition from the beginning of
the disk. Reply with the appropriate offset (again, in
whichever units you specified), as determined by how you
set up your disk using the partition editor.
You will be asked to enter the size of your
NetBSD
root
partition. It should be at least 13M, but if you are going to
be doing development, 14-16M is a more desirable size. This
size should be expressed in units of sectors or cylinders,
depending on which you said you wanted to use.
Next, you will be asked for the size of your swap partition.
You should probably allocate twice as much swap space as you
have real memory. Systems that will be heavily used should
have more swap space allocated, and systems that will be
lightly used can get by with less. If you want the system to
be able to save crash dumps when it panics, you will need at
least as much swap space as you have RAM. Again, this number
should be expressed in units of sectors or cylinders, as
appropriate.
The install program will then ask you for information about
the rest of the partitions you want on your disk. For most
purposes, you will want only one more partition,
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, and its
contents may be scrambled at the whim of the install program.
This is especially likely if you have given the install
program incorrect information. 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 filesystems will be initialized to
contain
NetBSD
bootstrapping binaries and configuration files.
It will also create an
You will be placed at a shell prompt ("#"). The task is to
install the distribution sets. The flow of installation
differs depending on your hardware resources, and on what
media the distribution sets reside.
After you have picked a temporary directory, enter the
"Load_fd" command, to load the distribution sets from
your floppies.
You will be asked which floppy drive to use. Enter
"0" (zero) if you're using the first floppy drive, or
enter "1" if you're using the second.
You will be prompted to insert a floppy into the drive,
to have its contents copied to your hard disk. Do so,
and hit return to begin copying. When that is done,
read the remainder of the floppies that contain the
distribution sets that you want to install, one by
one. When the last is read, and you are being
prompted for another, hit Control-C.
Run the
Extract
command once for each distribution
set you wish to install. For instance, if you wish to
install the "base13" distribution set, followed by the
"text13" distribution set, and finally the "etc13"
distribution set, use the commands:
Once you are finished extracting all of the sets that
you wish to install, you should proceed to the
instructions below (after the last install medium
type-specific instructions), that explain how you
should configure your system.
After you have picked a temporary directory, enter the
"Load_tape" command, to load the distribution sets from
tape.
You will be asked which tape drive to use. The
default is "rst0", which is correct if you're using
the SCSI tape drive with the lowest SCSI ID number.
(For the SCSI tape drive with the next lowest SCSI ID
number, you should use "rst1", and so on.)
You will be prompted to hit return when you have
inserted the tape into the tape drive. When you do,
the contents of the tape will be extracted into the
temporary directory, and the names of the files being
extracted will be printed.
After the tape has been extracted, to go the directory
containing the first distribution set you wish to
install. (Depending on how you made the tape, it's
probably a subdirectory of the temporary directory you
specified above.) Once there, run the "Set_tmp_dir"
command again, and accept its default answer by
hitting return at the prompt.
Use the "Extract" command to extract the distribution
set. For instance, if you're extracting the "base13"
set, use the command:
Repeat the previous two steps for each distribution
set you wish to install. Change to the set's
directory, run
Set_tmp_dir,
and then run
Extract set_name
to extract the set.
Once you are finished extracting all of the sets that
you wish to install, you should proceed to the
instructions below (after the last install medium
type-specific instructions), that explain how you
should configure your system.
Configure the appropriate ethernet interface (e.g.
ea0, eb0, etc.) up, with a command like:
ifconfig ifname ipaddr
[netmask netmask]
where
ifname is the interface name, like those
listed above, and
ipaddr is the numeric IP address
of the interface. If the interface has a special
netmask, supply the word
netmask and that netmask
at the end of the command line. (The brackets
indicate that those arguments are optional.) For
instance, to configure interface ea0 with IP address
129.133.10.10, use the command:
and to configure interface eb0 with IP address
128.32.240.167 and a special netmask, 0xffffff00, use
the command:
If the NFS server or FTP server is not on a directly-
connected network, you need to set up a route to it
using a command like:
If you are NFS-mounting the distribution sets, mount
them on the temporary directory with a command like:
where
serv_ipaddr
is the server's numeric IP address,
dist_dir
is the path to the distribution files on the server, and
tmp_dir
is the name of the local temporary directory.
Once this is done, proceed as if you had loaded the
files from tape, changing to the appropriate
directories, running "Set_tmp_dir", and running
"Extract" as appropriate.
If you are retrieving the distribution sets using ftp,
change into the temporary directory, and execute the
command:
ftp serv_ipaddr
where
serv_ipaddr
is once again the server's numeric
IP address. Get the files with FTP, taking care to
use binary mode when transferring the files.
Once you have all of the files for the distribution
sets that you wish to install, you can proceed using
the instructions above, as if you had installed from a
floppy. (Note that as with the floppy install, if
you're short on disk space, you can transfer only one
set at a time, extract it, then delete it, to save
space.)
Then all you need to do is mount the CDROM.
For the first CDROM drive use:
Once this is done, extract the required sets as
described in the "To install from floppy" section, but
ensure that you set the temporary directory to the
location of the sets on the CDROM (usually
Congratulations, you have successfully installed
NetBSD1.4.3.
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
You will need to set up a configuration file, see
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
They are typically extracted into
Upgrading from a previous version of
NetBSD
isn't currently supported by
NetBSD/arm32. If you are currently running NetBSD/arm32 then make a
FULL BACKUP of your current installation, and install
NetBSD1.4.3
from scratch. Obviously some of the steps can be skipped (in particular,
hard disk partitioning) as they will already be done.
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)
RiscPC/A7000(+) floppy controller.
IDE controllers:
Acorn motherboard IDE.
Simtec IDE controller.
RapIDE Issue 2 IDE controller.
ICS V5 & V6 IDE controller.
Getting the NetBSD System on to Useful Media
arm32/
platform/prep
for details.
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-1.4.3 # the top of the tree
cd arm32/binary
And then:
tar cf tape_device misc etc kern
Preparing your System for NetBSD Installation
arm32/
platform/prep
that are specific to your platform for partitioning and booting (even if you're
dedicating a device to NetBSD).
Installing the NetBSD System
/etc/rc.
Do not be alarmed, these are
completely normal. When you reach the prompt asking you for a
shell name, just hit return.
/usr
.
(Machines used as servers will probably also want
/var
as a separate partition. That can be done with these installation
tools, but is not covered here.) The install program will
tell you how much space there is left to be allocated in the
NetBSD area of the disk, and, if you only want one more
partition
(/usr
),
you should enter it at the prompt when the
installer asks you how large the next partition should be.
It will then ask you for the name of the mount point for that
partition. If you're doing a basic installation, that is
/usr
.
/etc/fstab
for your system, and mount
all of the file systems under
/mnt.
no
(In
other
words,
your
root
partition will be mounted on
/mnt,
your /usr
partition on
/mnt/usr
,
and so on.) There should be no errors in this
section of the installation. If there are, restart from the
beginning of the installation process.
To install from floppy
The first thing you should do is pick a temporary
directory where the distribution files can be stored.
To do this, enter the command "Set_tmp_dir", and enter
the name of the temporary directory. (Don't forget
that if your disk is still mounted under
/mnt
; you
should probably pick a directory under
/mnt/usr
.)
For each extraction, it will ask you if the extraction
should be verbose. If you reply affirmatively, it
will print out the name of each file that's being
extracted.
Extract base13
Extract text13
Extract etc13
To install from tape
The first thing you should do is pick a temporary
directory where the distribution files can be stored.
To do this, enter the command "Set_tmp_dir", and enter
the name of the temporary directory. (Don't forget
that your disk is mounted under
/mnt
;
you should
probably pick a directory under
/mnt/usr
.)
The default is /mnt/usr/distrib
.
Extract
base13
You will be asked if you wish the extraction to be
verbose. If you reply affirmatively, the name of each
file being extracted will be printed.
To install via FTP or NFS
The first thing you should do is pick a temporary
directory where the distribution files can be stored.
To do this, enter the command "Set_tmp_dir", and enter
the name of the temporary directory. (Don't forget
that your disk is mounted under
/mnt
; you should
probably pick a directory under
/mnt/usr
.)
The default is /mnt/usr/distrib.
ifconfig
ea0
129.133.10.10
ifconfig
eb0
128.32.240.167
netmask
0xffffff00
route add default gate_ipaddr
where gate_ipaddr
is your gateway's numeric IP address.
mount -t nfs serv_ipaddr:dist_dir tmp_dir
To install from CDROM:
First create a mount point so that you can mount the
CDROM:
mkdir
/mnt/cdrom
If you get an error here of "mkdir: /mnt/cdrom", don't
worry it just means that you didn't need to create the
directory.
mount
-rt
cd9660
/dev/cd0a
/mnt/cdrom
Or, for the second use:
mount
-rt
cd9660
/dev/cd1a
/mnt/cdrom
/cdrom/distrib
,
but check the release notes that came with the CD).
Completing your installation
Once you have finished extracting all of the distribution sets
that you wish to install, and are back at the "#" prompt, you
are ready to configure your system. The configuration utility
expects that you have installed the "base13" and "etc13"
distribution sets. If you have not, you will not be able to
run it successfully (nor will you have a functional system, in
any case). To configure your newly-installed
NetBSD
system,
run the command "Configure". It will ask you for the system's
host name, domain name, and other network configuration
information. It will set up your configuration files and make
the device nodes for the newly-installed system.
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/lib/X11/XF86Config.eg
for an example. See
http://www.xfree86.org/
and the XFree86 manual page for more information.
/usr/X11R6/bin
to your path in your shell's dot file so that you have access to the X binaries.
/usr/pkgsrc
(though other locations work fine), as with the command:
cat pkgsrc.tar.gz | gunzip | (mkdir /usr/pkgsrc;
cd /usr/pkgsrc; tar xpf - )
After extracting, then see the
README
file in the extraction directory (e.g.
/usr/pkgsrc/README
)
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
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.3
/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.3 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 | |||||||
Ichiro Fukuhara | ichiro@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 | |||||||
IWAMOTO Toshihiro | toshii@NetBSD.ORG | |||||||
Matthew Jacob | mjacob@NetBSD.ORG | |||||||
Lonhyn T. Jasinskyj | lonhyn@NetBSD.ORG | |||||||
Chris Jones | cjones@NetBSD.ORG | |||||||
Soren Jorvang | soren@NetBSD.ORG | |||||||
Takahiro Kambe | taca@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 | |||||||
Takuya SHIOZAKI | tshiozak@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 | |||||||
SUNAGAWA Keiki | kei@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 Mark Brinicombe.
This product includes software developed by Neil Carson.
This product includes software developed by Scott Stevens.