About this Document............................................2
What is NetBSD?................................................2
Changes Between The NetBSD 2.0.1 and 2.0.2 updates.............3
Kernel......................................................3
Networking..................................................3
System administration and user tools........................4
atari specific..............................................4
Changes Between The NetBSD 2.0 release and 2.0.1 update........4
Kernel......................................................4
Networking..................................................4
System administration and user tools........................4
atari specific..............................................5
Changes Between The NetBSD 1.6 and 2.0 Releases................5
Kernel......................................................5
Networking..................................................5
File system.................................................6
Security....................................................6
System administration and user tools........................6
Miscellaneous...............................................6
atari specific..............................................7
Important notes about NetBSD 2.0.2.............................7
The Future of NetBSD...........................................7
Sources of NetBSD..............................................8
NetBSD 2.0.2 Release Contents..................................8
NetBSD/atari subdirectory structure.........................9
Binary distribution sets...................................10
NetBSD/atari System Requirements and Supported Devices........12
Supported devices..........................................13
Getting the NetBSD System on to Useful Media..................13
Preparing your System for NetBSD installation.................14
Preparing your hard disk for the NetBSD installation.......14
Booting the installer on an existing system................16
Booting the installer on new systems.......................16
Using loadbsd.ttp..........................................16
Installing the NetBSD System..................................17
Running the sysinst installation program...................17
Introduction............................................17
General.................................................17
Quick install...........................................18
Booting NetBSD..........................................19
Network configuration...................................19
Installation drive selection and parameters.............19
Partitioning the disk...................................19
Preparing your hard disk................................20
Getting the distribution sets...........................21
Installation using ftp..................................21
Installation using NFS..................................21
Installation from CD-ROM................................21
Installation from an unmounted file system..............22
Installation from a local directory.....................22
Extracting the distribution sets........................22
Finalizing your installation............................22
Post installation steps.......................................22
Upgrading a previously-installed NetBSD System................25
Compatibility Issues With Previous NetBSD Releases............25
Issues affecting an upgrade from NetBSD 1.6................26
Using online NetBSD documentation.............................26
Administrivia.................................................27
Thanks go to..................................................27
We are........................................................30
Legal Mumbo-Jumbo.............................................35
The End.......................................................40
This document describes the installation procedure for
NetBSD2.0.2
on the
atari
platform.
It is available in four different formats titled
INSTALL.ext,
where
.ext
is one of
.ps, .html, .more,
or .txt:
.ps.html.moremore(1)
and
less(1)
pager utility programs.
This is the format in which the on-line
man
pages are generally presented.
.txtYou are reading the HTML version.
The NetBSD Operating System is a fully functional Open Source UNIX-like operating system derived from the University of California, Berkeley Networking Release 2 (Net/2), 4.4BSD-Lite, and 4.4BSD-Lite2 sources. NetBSD runs on fifty four different system architectures (ports), featuring seventeen machine architectures across fifteen distinct CPU families, and is being ported to more. The NetBSD2.0.2 release contains complete binary releases for many different system architectures. (A few ports are not fully supported at this time and are thus not part of the binary distribution. For information on them, please see the NetBSD web site at http://www.NetBSD.org/.)
NetBSD is a completely integrated system. In addition to its highly portable, high performance kernel, NetBSD features a complete set of user utilities, compilers for several languages, the X Window System, firewall software and numerous other tools, all accompanied by full source code.
NetBSD is a creation of the members of the Internet community. Without the unique cooperation and coordination the net makes possible, it's likely that NetBSD wouldn't exist.
The NetBSD2.0.2 release is the second security/critical update of the NetBSD 2.0 release branch. This represents a selected subset of fixes deemed critical in nature for stability or security reasons. All of these fixes will also appear on future NetBSD releases (e.g. NetBSD2.1 , etc) from the NetBSD 2.0 release branch as well.
Specific updates are as follows:
cgd(4)
code to avoid possibly security issues.
The NetBSD2.0.1 release is the first security/critical update of the NetBSD 2.0 release branch. This represents a selected subset of fixes deemed critical in nature for stability or security reasons. All of these fixes will also appear on future NetBSD releases (e.g. NetBSD2.1 , etc) from the NetBSD 2.0 release branch as well.
Specific updates are as follows:
wm(4)
sk(4)
performance on ASUS A8V motherboards.
swapcontext(3)
for amd64 so that it works correctly.
The NetBSD 2.0 release provides numerous significant functional enhancements, including support for many new devices, integration of hundreds of bug fixes, new and updated kernel subsystems, and many user-land enhancements. The result of these improvements is a stable operating system fit for production use that rivals most commercially available systems.
It is impossible to completely summarize over two years of development that went into the NetBSD2.0.2 release. Some highlights include:
sysctl(9)
was switched from a static binding to a dynamic implementation.
satalink(4)
and move SATA support from other controllers into this along with adding support
for new controllers.
ipf(8)
has been upgraded to version 4.1.3.
tcp(4)
now implements path MTU discovery blackhole detection (i.e. it will turn off
path MTU discovery if the connection is losing).
wi(4)
has support for Host-AP mode, allowing Intersil Prism2/2.5/3-based boards to
be used to make an 802.11 Access Point.
ipf(8)
has been added to
bridge(4)
and
brconfig(8)
Kernel interfaces have continued to be refined, and more subsystems and device drivers are shared among the different ports. You can look for this trend to continue.
The atari release was imported into NetBSD in in March 1995. The first major release was NetBSD1.1. About a year later, NetBSD1.2 was released for the Atari. This release fixed a large number of bugs and made the Atari-port a stable member of the NetBSD family. The saga continued with the NetBSD1.3 release. In this release, support was added for the Medusa Hades, Riebl ethernet and Falcon IDE support. NetBSD1.4 was released a couple of years later, and added support for various devices. NetBSD1.5 was released in late 2000. and add And now, NetBSD2.0.2 is emerging!
In order to retain the functionality that a newly installed system can send mail ``out of the box'', the default has changed so that sendmail will now start by default, and listen for host-local connections.
If this behaviour is not desired, you can either
/etc/rc.conf,
/etc/mail/submit.cf
to point to another host,
/etc/mailer.conf
to point to something else than sendmail, or
/etc/mail/submit.cf,
and set the sendmail_suid variable to ``YES'' in
/etc/rc.conf.
The NetBSD Foundation has been incorporated as a non-profit organization. Its purpose is to encourage, foster and promote the free exchange of computer software, namely the NetBSD Operating System. The foundation will allow for many things to be handled more smoothly than could be done with our previous informal organization. In particular, it provides the framework to deal with other parties that wish to become involved in the NetBSD Project.
The NetBSD Foundation will help improve the quality of NetBSD by:
We intend to begin narrowing the time delay between releases. Our ambition is to provide a full release every six to eight months.
We hope to support even more hardware in the future, and we have a rather large number of other ideas about what can be done to improve NetBSD.
We intend to continue our current practice of making the NetBSD-current development source available on a daily basis.
We intend to integrate free, positive changes from whatever sources submit them, providing that they are well thought-out and increase the usability of the system.
Above all, we hope to create a stable and accessible system, and to be
responsive to the needs and desires of
NetBSD
users, because it is for
and because of them that
NetBSD
exists.
Refer to
http://www.NetBSD.org/Sites/net.html.
The root directory of the NetBSD2.0.2 release is organized as follows:
.../NetBSD-2.0.2/
CHANGESLAST_MINUTEMIRRORSREADME.filesTODOpatches/source/In addition to the files and directories listed above, there is one directory per architecture, for each of the architectures for which NetBSD2.0.2 has a binary distribution.
The source distribution sets can be found in subdirectories of the
source
subdirectory of the distribution tree.
They contain the complete sources to the system.
The source distribution sets are as follows:
config(8);
and
dbsym(8).
All the above source sets are located in the
source/sets
subdirectory of the distribution tree.
The source sets are distributed as compressed tar files.
Except for the
pkgsrc
set, which is traditionally unpacked into
/usr/pkgsrc,
all sets may be unpacked into
/usr/src
with the command:
#( cd / ; tar -zxpf - ) < set_name.tgz
In each of the source distribution set directories, there are files which contain the checksums of the files in the directory:
BSDSUMCKSUMMD5SYSVSUMThe MD5 digest is the safest checksum, followed by the POSIX checksum. The other two checksums are provided only to ensure that the widest possible range of system can check the integrity of the release files.
atari
subdirectory of the distribution:
.../NetBSD-2.0.2/atari/.
It contains the following files and directories:
INSTALL.htmlINSTALL.psINSTALL.txtINSTALL.more.more
file contains underlined text using the
more(1)
conventions for indicating italic and bold display.
binary/kernel/netbsd-ATARITT.gznetbsd-BOOT.gznetbsd-BOOTX.gznetbsd-FALCON.gznetbsd-HADES.gznetbsd-MILAN-ISAIDE.gznetbsd-MILAN-PCIIDE.gzsets/installation/floppy/miniroot/misc/atari/binary/sets
subdirectory
of the
NetBSD2.0.2
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.
/netbsd.
You
must
install the kernel that matches your hardware.
/usr/share.
groff(1),
all related programs, and their manual pages.
NetBSD maintains its own set of sources for the X Window System in order to assure tight integration and compatibility. These sources are based on XFree86, and tightly track XFree86 releases. They are currently equivalent to XFree86 4.4.0. Binary sets for the X Window System are distributed with NetBSD. The sets are:
The atari binary distribution sets are distributed as gzipped tar files
named with the extension
.tgz,
e.g.
base.tgz.
The instructions given for extracting the source sets work equally
well for the binary sets, but it is worth noting that if you use that
method, the filenames stored in the sets are relative and therefore
the files are extracted
below the current directory.
Therefore, if you want to extract the binaries into your system, i.e.
replace the system binaries with them, you have to run the
tar -xpf
command from the root directory (
/
) of your system.
Additional kernels to those included in the distribution sets may be found
in the
atari/binary/kernel
subdirectory of the
NetBSD2.0.2
distribution tree.
These kernels are generally named something like
netbsd-BOOT.gz
or some other suitable name.
Please note that these kernels are simply gzipped and are not in tar archives.
There are six atari floppy images to be found in the
atari/installation/floppies
subdirectory of the
NetBSD2.0.2
distribution.
Three of them are bootable
TOS
kernel floppies and the other
three are installation floppies.
They are described in more detail below.
There are gzipped versions of each available, for easier downloading.
(The gzipped versions have the
.gz
extension added to their names.)
For the TT030 and Falcon, the (720 KB) floppy is named
boot.fs
and
the kernel supplied is
BOOT.
For the Hades, you need the
hades-boot.fs
floppy (1.44 MB), the kernel is
HADES.
For the Milan, you need the
milan-boot.fs
floppy (1.44 MB), the kernel is MILAN-PCIIDE.
/
(root) and
/usr
partitions and getting
ready to extract (and possibly first fetching) the distribution
sets.
There is enough on this file system to allow you to
make a slip connection, configure an ethernet, mount an NFS
file system or ftp.
You can also load distribution sets from a SCSI tape or from one of
your existing
GEMDOS
partitions.
The floppies meant for 720 KB disks are named
miniroot.fs.1
and
miniroot.fs.2.
There is also an image for an 1.44 MB disk:
miniroot.fs.
There are also
TOS
utilities in the
atari/installation/misc
subdirectory, which you will need to get
NetBSD/atari
up-and-running.
gzip.ttp -d filename.gz
atari/floppies
directory.
sysinst.fs
to a partition with id SWP.
In this way, you can run the installation from the swap partition
instead of a memory disk.
This is a necessity for small memory systems.
NetBSD/atari 2.0.2 runs on a TT030, Falcon, Hades and MilanI. An FPU is not required. The minimum amount of RAM required is 4 MB. On the Hades, only the Tseng PCI VGA cards (ET4000/ET6000/ET6100) are supported in the 2.0.2 release. When an unsupported video card is present, you can use NetBSD with a serial console only.
Here is a table of recommended HD partition sizes for a full install:
| Partition | Suggested | + X | Needed | + X |
| root (/) | 25 MB | 25 MB | 20 MB | 20 MB |
| /usr | 245 MB | 270 MB | 120 MB | 145 MB |
| /var | 20 MB | 20 MB | 5 MB | 5 MB |
| swap | 2*RAM below 32 MB, then up to you |
In addition of the rule of thumb for the swap size mentioned below, you
probably want to make sure that the size of the swap partition does not
drop below 20 MB (30 MB for systems with X).
Another item is the add-on packages.
You might want 20-30M (or more) in
/usr/local
(or added to
/usr)
to store packages from the
NetBSD
package system.
As you may note the recommended size of
/usr
is 125 MB greater than needed.
This is to leave room for a kernel source and compile tree
as you will probably want to compile your own kernel.
(GENERIC
is large and bulky to accommodate all people,
BOOT
is small and might not have all the features you want).
This list is incomplete by definition.
We can not test all SCSI peripherals, ISA cards or PCI cards.
If you have problems with such a peripheral, please contact the
port-atari@NetBSD.org
mailing list.
Installation is supported from several media types, including:
No matter what you do, however, you'll need to have three disks handy, on which you will put the install and boot floppy images.
All the images are available from the directory
installation/floppies
under the root of the
NetBSD/atari
tree at your favorite archive site.
If you are using
NetBSD/atari
to make the floppies, you should use
the command
dd(1)
to write the raw floppy images (.fs files) to
the disk.
As an example, to write the first part of the miniroot file system
onto a 720 KB floppy in fd0 use:
# dd if=miniroot.fs.1 of=/dev/rfd0b bs=9b
If you are using
TOS
to make the floppies, grab the
rawwrite
utility from the
atari/utils
directory and issue the command:
rawwrite boot.fs
This will create the boot-floppy on the floppy in drive a. The floppies should be pre-formatted on 720 KB / 1.44 MB for both the dd and rawwrite commands to work. Pre-formatting can be best done using the desktop format command. Some other utilities seem to be giving problems.
Since the 1.3 release, it is also possible to use HD-floppies.
You should than use the floppy device
/dev/rfd0c
or add the
-H
flag to
rawwrite.
The steps necessary to prepare the distribution sets for installation depend on which method of installation you choose. The various methods are explained below.
Note where you placed the files, you will need this later.
Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk.
# cd .../NetBSD-2.0.2/atari/binary/sets
# T=<tape_device>
# mt -f $T rewind
# for f in base etc comp games man misc text
dd if=$f.tgz of=$T conv=sync bs=5k
# done
# mt -f $T rewind
where
``<tape_device>''
is the name of the (non-rewinding!) tape
device that you're using (probably something like
/dev/nrst0,
but we make no guarantees 8-).
If you can't figure it out, ask your system administrator.
Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk.
If
NetBSD
has to share the disk with another operating system, you can
either take care of partitioning your harddisk before installing
NetBSD
or delay this until the installer requests you to do it.
If you decide to do it now, please create space for at least
/
(root), swap and
/usr
partitions and possibly at least one more for
/local
if you have the space.
Whatever you decide, take note of the paragraphs below!
You need this info to create bootable disks.
If you want to use an AHDI partitioning scheme and you want to be able to boot directly into NetBSD, there are some constraints on the partition layout.
As you might know; every hard disk has a `root sector' that contains information about the size of the hard disk and the partitions on the hard disk. The root sector can only contain the necessary data for four partitions. Nobody thought that this limitation would cause any problems. After all, 640 KByte should be enough. As hard disk grew, it was necessary to define more than four partitions. In order to be more or less compatible with the old format, a new type of partition entry was defined: XGM partions.
An XGM partition is a `look over there' sign: Another root sector can be found at the start of the XGM partition. This root sector contains the remaining real partitions. And this is the big mystery: Partitions defined in the root sector of the hard disk are called `primary partitions', partitions defined in the root sector of an XGM partition are called `extended partitions'.
The bootblock will only work if the first NBD partition is a primary partition. This is not a limitation of NetBSD but a limitation of TOS/AHDI: You can only boot from primary partitions.
If you are creating your partitions with HDX, you'll have to be very careful to fulfill this rule. HDX has some very strange ideas when it comes to extended partitions. Fortunately, you can edit this stuff: The ``Edit partition scheme of the unit'' dialog box has a button labeled ``expert''. This button is inactive unless you have defined more than four partitions. Click on it after you have defined the sizes of the partitions.
A new dialog box appears on the screen. The left side contains two blocks of partitions; the upper block always contains the first four partitions, the lower block contains the last three partitions. If you have defined less than 7 partitions, some fields of the lower block will contain the string ``unused''. Some of the partitions will be displayed in reverse video: These are the extended partitions.
The right side contains six possible ranges for the extended partitions. It is not possible to define your own range, you will have to use one of the schemes offered by HDX. To quote from Ghostbusters: Choose and die. The default scheme used by HDX is the first scheme: Extended partitions start with the second partition and end with the second to last partition. If you have defined 7 partitions, partitions #2 to #5 will be extended partitions, while partitions #1, #6 and #7 will be primary partitions.
You can move the extended partition range by clicking on one of the buttons on the right side of the dialog box. Try to find one where your first NetBSD partition is a primary partition. Golden rules:
dd if=sysinst.fs of=/dev/rsd0b
where
/dev/rsd0b
should be the device path of the swap partition your system
is configured to use.
Once the file is copied, reboot back to the booter
and use the '-b' option to make the kernel prompt for a root device.
Now enter the swap device as your root device to start the installer.
For new new installations on small memory systems, things are a bit more complicated. The easiest way is to mark an AHDI partition as id 'SWP'. You can either accomplish this with HDdriver or use the chg_pid.ttp program supplied on the bootfloppy. To use the fifth partition of your first drive to a swap partition, do the following:
chg_pid -w 0 4 SWP
As you can see, both the drive and the partition numbers are zero based.
When a swap partition has been created, you can transfer the installer using the file2swp.ttp command, which is also on the bootfloppy. This program copies a (gzipped)file to the first AHDI partition with id 'SWP' on the designated disk. To copy sysinst.fs to your first SCSI disk, use:
file2swp -w -f sysinst.fs s0
Note that file2swp automatically detects a gzipped file, there is no need for a .gz extension.
loadbsd -b a:/netbsd
You should see the screen clear and some information about your system as the kernel configures the hardware. Then you will be prompted for a root device. If you copied the installer to a swap partition, as explained above, you have to enter the swap partition as the boot device. When you used your first SCSI disk, this will be sd0b. On the first IDE drive it would be wd0b.
When you didn't copy the installer to swap, need to use the RAMdisk, so remove the GEMDOS kernel boot floppy from the drive if present and insert the NetBSD install floppy 1. Now enter the name of the boot device depending on the floppy type you have inserted. Use:
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 must have already prepared your hard disk as detailed in the section on preparing your system for install.
The following is a walk-through of the steps necessary to get NetBSD installed on your hard disk.
Using sysinst, installing NetBSD is a relatively easy process. You still should read this document and have it in hand when doing the installation process. This document tries to be a good guideline for the installation and as such covers many details for the sake of completeness. Do not let this discourage you; the install program is not hard to use.
The following is a walk-through of the steps you will take while
getting
NetBSD
installed on your hard disk.
sysinst
is a menu driven
installation system that allows for some freedom in doing the
installation.
Sometimes, questions will be asked and in many cases
the default answer will be displayed in brackets
(``[ ]'')
after the question.
If you wish to stop the installation, you may press
CONTROL-C
at any time, but if you do, you'll have to begin the installation
process again from scratch by running the
/sysinst
program from the command prompt.
It is not necessary to reboot.
First, let's describe a quick install. The other sections of this document go into the installation procedure in more detail, but you may find that you do not need this. If you want detailed instructions, skip to the next section. This section describes a basic installation, using a CD-ROM install as an example.
.***********************************************.
* NetBSD-2.0 Install System *
* *
*>a: Install NetBSD to hard disk *
* b: Upgrade NetBSD on a hard disk *
* c: Re-install sets or install additional sets *
* d: Reboot the computer *
* e: Utility menu *
* x: Exit Install System *
.***********************************************.
root,
and set a password for that account.
You are also advised to edit the file
/etc/rc.conf
to match your system needs.
/usr/X11R6/lib/X11/doc.
Further information can be found on
http://www.xfree86.org/.
Boot the system as described in the "Booting the installer" section above.
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.
You may want to read the
boot messages, to notice 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 may need your disk's geometry when creating
NetBSD
partitions.
You will also need to know the name, to tell
sysinst
on which disk
to install.
The most important thing to know is that
wd0
is the
NetBSD
name for your first IDE disk,
wd1
the second, etc.
sd0
is your first SCSI disk,
sd1
the second, etc.
Once NetBSD has booted and printed all the boot messages, you will be presented with a welcome message and a main menu. It will also include instructions for using the menus.
If you will not use network operation during the installation, but you do want your machine to be configured for networking once it is installed, you should first go to the Utility menu, and select the Configure network option. If you only want to temporarily use networking during the installation, you can specify these parameters later. If you are not using the Domain Name System (DNS), you can give an empty response in reply to answers relating to this.
To start the installation, select Install NetBSD to hard disk from the main menu.
The first thing is to identify the disk on which you want to
install
NetBSD.
sysinst
will report a list of disks it finds
and ask you for your selection.
Depending on how many disks are found, you may get a different message.
You should see disk names like
sd0
or
sd1.
You will be prompted if you want an AHDI compatible partitioning on your disk. If you are installing NetBSD on a dedicated drive, just answer 'no' and skip to the next section.
If you answer 'yes', the ahdilabel program is started. You can now change the AHDI partition ID's on your root disk. Because NetBSD imposes a special ordering in disk partitions it uses for / (root) and swap. Also, because it wants to guard you against an unwanted demolition of partitions used by other systems, you have to tell it what partitions it is allowed to use. You have to mark the partition you want to use as swap SWP or (deprecated!) NBS and the other partitions as NBD. Note that all the changes you make to the ID's are reversable as long as you remember the original value. ahdilabel is capable of creating or changing an AHDI compatible partioning on the disk, and in the partition-ID editor, the partitions are shown in the order that AHDI created them. When you leave this editor and continue with sysinst, your changes to the ID's do have consequences to the partition order! They will show up as follows:
abd (and up)The partition table of the NetBSD part of a disk is called a disklabel. There are 4 layouts for the NetBSD part of the disk that you can pick from: Standard, Standard with X, Custom and Use Existing. The first two use a set of default values (that you can change) suitable for a normal installation, possibly including X. With the Custom option you can specify everything yourself. The last option uses the partition info already present on the disk.
If you want to use NetBSD on an AHDI partitioned disk, you will have to use: Use Existing.
You will be presented with the current layout of the NetBSD disklabel, and given a chance to change it. For each partition, you can set the type, offset and size, block and fragment size, and the mount point. The type that NetBSD uses for normal file storage is called 4.2BSD. A swap partition has a special type called swap. Some partitions in the disklabel have a fixed purpose.
a/)
bcd-pd
is the partition mounted on
/usr,
but this is historical practice and not a fixed value.
You will then be asked to name your disk's disklabel. The default response will be ok for most purposes. If you choose to name it something different, make sure the name is a single word and contains no special characters. You don't need to remember this name.
You are now at the point of no return.
Apart from the changes you made with
ahdilabel
nothing has been modified on your disk yet.
If you confirm that you want to install
NetBSD,
the partitions now assigned to
NetBSD
will be actually written to.
If you are sure you want to proceed, enter
yes
at the prompt.
The install program will now label your disk and make the file systems you specified. The file systems will be initialized to contain NetBSD bootstrapping binaries and configuration files. You will see messages on your screen from the various NetBSD disk preparation tools that are running. There should be no errors in this section of the installation. If there are, restart from the beginning of the installation process. Otherwise, you can continue the installation program after pressing the return key.
The NetBSD distribution consists of a number of sets, that come in the form of gzipped tarfiles. A few sets must be installed for a working system, others are optional. At this point of the installation, you will be presented with a menu which enables you to choose from one of the following methods of installing the sets. Some of these methods will first load the sets on your hard disk, others will extract the sets directly.
For all these methods, the first step is making the sets available for extraction, and then do the actual installation. The sets can be made available in a few different ways. The following sections describe each of those methods. After reading the one about the method you will be using, you can continue to the section labeled `Extracting the distribution sets'.
To be able to install using ftp, you first need to configure
your network setup, if you haven't already at the start of
the install procedure.
sysinst
will do this for you, asking you
if you want to use DHCP, and if not
to provide data like IP address, hostname, etc.
If you do not have name service set up for the machine that you
are installing on, you can just press
RETURN
in answer to these questions, and DNS will not be used.
You will also be asked to specify the host that you want to transfer the sets from, the directory on that host, the account name and password used to log into that host using ftp, and optionally a proxy server to use. If you did not set up DNS when answering the questions to configure networking, you will need to specify an IP address instead of a hostname for the ftp server.
sysinst will proceed to transfer all the default set files from the remote site to your hard disk.
To be able to install using NFS, you first need to configure
your network setup, if you haven't already at the start of
the install procedure.
sysinst
will do this for you, asking you
if you want to use DHCP, and if not
to provide data like IP address, hostname, etc.
If you do not have name service set up for the machine that you
are installing on, you can just press
RETURN
in answer to these questions, and DNS will not be used.
You will also be asked to specify the host that you want to transfer the sets from, and the directory on that host that the files are in. This directory should be mountable by the machine you are installing on, i.e. correctly exported to your machine.
If you did not set up DNS when answering the questions to configure networking, you will need to specify an IP address instead of a hostname for the NFS server.
When installing from a CD-ROM, you will be asked to specify
the device name for your CD-ROM player
(usually cd0),
and the directory name on the CD-ROM where the distribution files are.
sysinst will then check if the files are indeed available in the specified location, and proceed to the actual extraction of the sets.
In order to install from a local file system, you will
need to specify the device that the file system resides
on
(for example sd1e)
the type of the file system,
and the directory on the specified file system where the sets are located.
sysinst
will then check if it
can indeed access the sets at that location.
This option assumes that you have already done some preparation yourself. The sets should be located in a directory on a file system that is already accessible. sysinst will ask you for the name of this directory.
After the install sets containing the NetBSD distribution have been made available, you can either extract all the sets (a full installation), or only extract sets that you have selected. In the latter case, you will be shown the currently selected sets, and given the opportunity to select the sets you want. Some sets always need to be installed (kern, base) and etc they will not be shown in this selection menu.
Before extraction begins, you can elect to watch the files being extracted; the name of each file that is extracted will be shown. This can slow down the installation process considerably, especially on machines with slow graphics consoles or serial consoles.
After all the files have been extracted, all the necessary device node files will be created. If you have already configured networking, you will be asked if you want to use this configuration for normal operation. If so, these values will be installed in the network configuration files. The next menu will allow you to select the time zone that you're in, to make sure your clock has the right offset from UTC. Finally you will be asked to select a password encryption algorithm and can than set a password for the "root" account, to prevent the machine coming up without access restrictions.
Congratulations, you have successfully installed NetBSD2.0.2. You can now reboot the machine, and boot NetBSD from hard disk.
Once you've got the operating system running, there are a few things you need to do in order to bring the system into a properly configured state, with the most important ones described below.
/etc/rc.conf
If you or the installation software haven't done any configuration of
/etc/rc.conf
(sysinst
usually will),
the system will drop you into single user mode on first reboot with the
message
/etc/rc.conf is not configured. Multiuser boot aborted.
and with the root file system
(/)
mounted read-only.
When the system asks you to choose a shell, simply press
RETURN
to get to a
/bin/sh
prompt.
If you are asked for a terminal type, respond with
vt220
(or whatever is appropriate for your terminal type)
and press
RETURN.
You may need to type one of the following commands to get your delete key
to work properly, depending on your keyboard:
# stty erase '^h'
# stty erase '^?'
At this point, you need to configure at least
one file in the
/etc
directory.
You will need to mount your root file system read/write with:
# /sbin/mount -u -w /
Change to the
/etc
directory and take a look at the
/etc/rc.conf
file.
Modify it to your tastes, making sure that you set
rc_configured=YES
so that your changes will be enabled and a multi-user boot can
proceed.
Default values for the various programs can be found in
/etc/defaults/rc.conf,
where some in-line documentation may be found.
More complete documentation can be found in
rc.conf(5).
If your
/usr
directory is on a separate partition and you do not know how to use
ed,
you will have to mount your
/usr
partition to gain access to
ex
or
vi.
Do the following:
# mount /usr
# export TERM=vt220
If you have
/var
on a separate partition, you need to repeat that step for it.
After that, you can edit
/etc/rc.conf
with
vi(1).
When you have finished, type
exit
at the prompt to
leave the single-user shell and continue with the multi-user boot.
Other values that need to be set in
/etc/rc.conf
for a networked environment are
hostname
and possibly
defaultroute,
furthermore add an
ifconfig_int
for your
<int>
network interface,
along the lines of
ifconfig_de0="inet 123.45.67.89 netmask 255.255.255.0"
or, if you have
myname.my.dom
in
/etc/hosts:
ifconfig_de0="inet myname.my.dom netmask 255.255.255.0"
To enable proper hostname resolution, you will also want to add an
/etc/resolv.conf
file or (if you are feeling a little more adventurous) run
named(8).
See
resolv.conf(5)
or
named(8)
for more information.
Instead of manually configuring network and naming service,
DHCP can be used by setting
dhclient=YES
in
/etc/rc.conf.
Other files in
/etc
that may require modification or setting up include
/etc/mailer.conf,
/etc/nsswitch.conf,
and
/etc/wscons.conf.
You will have to edit the
/etc/ttys
file.
If you don't have a Milan, you must disable the
ttyEx
devices.
For the Milan, you will have to disable the
ttyex
devices.
This is easy, just change 'on' to 'off' on the corresponding lines.
After reboot, you can log in as
root
at the login prompt.
Unless you've set a password in
sysinst,
there
is no initial password.
If you're using the machine in a networked environment,
you should create an account for yourself (see below) and protect it and the
``root''
account with good passwords.
By default, root login from the network is disabled (even via
ssh(1)).
One way to become root over the network is to log in as a different
user that belongs to group
``wheel''
(see
group(5))
and use
su(1)
to become root.
Unless you have connected an unusual terminal device as the console
you can just press
RETURN
when it prompts for
Terminal type? [...].
Use the
useradd(8)
command to add accounts to your system.
Do not
edit
/etc/passwd
directly! See
vipw(8)
and
pwd_mkdb(8)
if you want to edit the password database.
If you have installed the X Window System, look at the files in
/usr/X11R6/lib/X11/doc
for information.
Don't forget to add
/usr/X11R6/bin
to your path in your shell's dot file so that you have access to the X binaries.
If you wish to install any of the software freely available for UNIX-like systems you are strongly advised to first check the NetBSD package system. This automatically handles any changes necessary to make the software run on NetBSD, retrieval and installation of any other packages on which the software may depend, and simplifies installation (and deinstallation), both from source and precompiled binaries.
2.0.2/atari/All
subdir.
You can install them with the following commands under
sh(1):
# PKG_PATH=ftp://ftp.NetBSD.org/pub/NetBSD/packages/2.0.2/atari/All # export PKG_PATH # pkg_add -v tcsh # pkg_add -v bash # pkg_add -v perl # pkg_add -v apache # pkg_add -v kde # pkg_add -v mozilla ...
If you are using
csh(1)
then replace the first two lines with the following:
# setenv PKG_PATH ftp://ftp.NetBSD.org/pub/NetBSD/packages/2.0.2/atari/All ...
The above commands will install the Tenex-csh and Bourne Again shell, the perl programming language , Apache web server, KDE desktop environment and the Mozilla web browser as well as all the packages they depend on.
/usr/pkgsrc
(though other locations work fine), with the commands:
# mkdir /usr/pkgsrc
#( cd /usr/pkgsrc ; tar -zxpf - ) < pkgsrc.tar.gz
After extracting, see the
README
and
Packages.txt
files in the extraction directory (e.g.
/usr/pkgsrc/README)
for more information.
/etc/mail/aliases
to forward root mail to the right place.
Don't forget to run
newaliases(1)
afterwards.
/etc/mail/sendmail.cf
file will almost definitely need to be adjusted;
files aiding in this can be found in
/usr/share/sendmail.
See the
README
file there for more information.
If you prefer postfix as MTA, adjust
/etc/mailer.conf.
/etc/rc.local
to run any local daemons you use.
/etc
files are documented in section 5 of the manual; so just invoking
# man 5 filename
is likely to give you more information on these files.
The upgrade to NetBSD2.0.2 is a binary upgrade; it can be quite difficult to update the system from an earlier version by recompiling from source, primarily due to interdependencies in the various components.
To do the upgrade, you must first boot the system as described in the
Booting the installer
section.
You must also have at least the
base
and
kern
binary distribution sets available, so that you can upgrade with them,
using one of the upgrade methods described above.
Finally, you must have sufficient disk space available to install the
new binaries.
Since files already installed on the system are overwritten in place,
you only need additional free space for files which weren't previously
installed or to account for growth of the sets between releases.
If you have a few megabytes free on each of your root
(/)
and
/usr
partitions, you should have enough space.
Since upgrading involves replacing the kernel, the boot blocks on your NetBSD partition, and most of the system binaries, it has the potential to cause data loss. You are strongly advised to back up any important data on the NetBSD partition or on another operating system's partition on your disk before beginning the upgrade process.
The upgrade procedure using the
sysinst
tool is similar to an installation, but without the hard disk partitioning.
sysinst
will attempt to merge the settings stored in your
/etc
directory with the new version of
NetBSD.
Getting the binary
sets is done in the same manner as the installation procedure;
refer to the installation part of the document
for how to do this.
Also, some sanity checks are done, i.e.
file systems are checked before unpacking the sets.
After a new kernel has been copied to your hard disk, your
machine is a complete
NetBSD2.0.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
/dev.
If you've changed the contents of
/dev
by hand, you will need to be careful about this, but if
not, you can just cd into
/dev,
and run the command:
# sh MAKEDEV all
Finally, you will want to delete old binaries that were part
of the version of
NetBSD
that you upgraded from and have since been removed from the
NetBSD
distribution.
Users upgrading from previous versions of NetBSD may wish to bear the following problems and compatibility issues in mind when upgrading to NetBSD2.0.2.
mkdir /tmp/upgrade
cd /tmp/upgrade
pax -zrpe -f /path/to/etc.tgz
./etc/postinstall -s `pwd` check
./etc/postinstall -s `pwd` fix
Issues fixed by postinstall:
/etc
need upgrading.
These include:
/etc/defaults/*
/etc/mtree/*
/etc/daily
/etc/weekly
/etc/monthly
/etc/security
/etc/rc.subr
/etc/rc
/etc/rc.shutdown
/etc/rc.d/*
/etc/rc.d/fsck.sh
/etc/rc.d/gated
/etc/rc.d/kerberos
/etc/rc.d/NETWORK
/etc/rc.d/systemfs
/etc/rc.d/xntpd
and
/etc/rc.d/ypset.
The following issues need to be resolved manually:
postfix(8)
configuration files require upgrading.
cd /usr/share/examples/postfix
cp post-install postfix-files postfix-script /etc/postfix
postfix check
Documentation is available if you first install the manual
distribution set.
Traditionally, the
``man pages''
(documentation) are denoted by
`name(section)'.
Some examples of this are
intro(1),
man(1),
apropros(1),
passwd(1),
and
passwd(5).
The section numbers group the topics into several categories, but three are of primary interest: user commands are in section 1, file formats are in section 5, and administrative information is in section 8.
The man command is used to view the documentation on a topic, and is started by entering man[ section] topic. The brackets [] around the section should not be entered, but rather indicate that the section is optional. If you don't ask for a particular section, the topic with the lowest numbered section name will be displayed. For instance, after logging in, enter
# man passwd
to read the documentation for
passwd(1).
To view the documentation for
passwd(5),
enter
# man 5 passwd
instead.
If you are unsure of what man page you are looking for, enter
apropos subject-word
where subject-word is your topic of interest; a list of possibly related man pages will be displayed.
If you've got something to say, do so! We'd like your input. There are various mailing lists available via the mailing list server at majordomo@NetBSD.org. To get help on using the mailing list server, send mail to that address with an empty body, and it will reply with instructions.
There are various mailing lists set up to deal with comments and questions about this release. Please send comments to: netbsd-comments@NetBSD.org.
To report bugs, use the
send-pr(1)
command shipped with
NetBSD,
and fill in as much information about the problem as you can.
Good bug reports include lots of details.
Additionally, bug reports can be sent by mail to:
netbsd-bugs@NetBSD.org.
Use of
send-pr(1)
is encouraged, however, because bugs reported with it
are entered into the
NetBSD
bugs database, and thus can't slip through
the cracks.
There are also port-specific mailing lists, to discuss aspects of each port of NetBSD. Use majordomo to find their addresses, or visit http://www.NetBSD.org/MailingLists/. If you're interested in doing a serious amount of work on a specific port, you probably should contact the `owner' of that port (listed below).
If you'd like to help with this effort, and have an idea as to how you could be useful, send us mail or subscribe to: netbsd-help@NetBSD.org.
As a favor, please avoid mailing huge documents or files to these mailing lists. Instead, put the material you would have sent up for FTP or WWW somewhere, then mail the appropriate list about it, or, if you'd rather not do that, mail the list saying you'll send the data to those who want it.
Keith Bostic Ralph Campbell Mike Karels Marshall Kirk McKusick
for their ongoing work on BSD systems, support, and encouragement.
AboveNet Communications, Inc. Advanced System Products, Inc. Alex Poylisher Alistair Crooks Andrew Brown Atsushi YOKOYAMA Avalon Computer Systems Bay Area Internet Solutions Ben Collver Bill Coldwell Bill Sommerfeld Brad Salai Brains Corporation, Japan Brian Carlstrom Brian McGroarty Canada Connect Corporation Castor Fu Central Iowa (Model) Railroad Charles Conn Charles D. Cranor Charles M. Hannum Chris Legrow Christer O. Andersson Christopher g. Demetriou Christos Zoulas Chuck Silvers Co-operative Research Centre for Enterprise Distributed Curt Sampson Dave Burgess Dave Rand David Brownlee Demon Internet, UK Derek Fellion Digital Equipment Corporation Distributed Processing Technology Douglas J. Trainor Easynet, UK Ed Braaten Edward Richley Eric and Rosemary Spahr Free Hardware Foundation Greg Gingerich Guenther Grau Harald Koerfgen Harry McDonald Heiko W. Rupp Herb Peyerl Hubert Feyrer Innovation Development Enterprises of America Internet Software Consortium James Chacon Jan Joris Vereijken Jason Birnschein Jason Brazile Jason R. Thorpe Jim Wise John Kohl Jonathan P. Kay Jordan K. Hubbard Kenneth Alan Hornstein Kevin Keith Woo Kimmo Suominen Krister Waldfridsson Lex Wennmacher LinuxFest Northwest Luke Mewburn MS Macro System GmbH, Germany Mark Brinicombe Mark S. Thomas Mason Loring Bliss Mattias Karlsson Michael Graff Michael L. Hitch Michael Richardson Michael Thompson Michael W. James Mike Price Neil J. McRae Noah M. Keiserman Norman R. McBride Numerical Aerospace Simulation Facility, NASA Ames Research Oliver Cahagne Perry E. Metzger Petri T. Koistinen Piermont Information Systems Inc. Precedence Technologies Ltd Ralph Campbell Reinoud Zandijk Richard Nelson Rob Windsor Ross Harvey SDF Public Access Unix, Inc. 501(c)(7) Salient Systems Inc. Scott Ellis Scott Kaplan Simon Burge Soren Jacobsen Soren Jorvang Steve Allen Steve Wadlow SunROOT# Project Ted Lemon Ted Spradley Thor Lancelot Simon Tim Law Tom Coulter Toru Nishimura VMC Harald Frank, Germany Warped Communications, Inc. Wasabi Systems Whitecross Database Systems Ltd. William Gnadt Worria Web Hosting
(If you're not on that list and should be, tell us! We probably were not able to get in touch with you, to verify that you wanted to be listed.)
(in alphabetical order)
| The NetBSD core group: | |||
| Allen Briggs | briggs@NetBSD.org | ||
| Frank van der Linden | fvdl@NetBSD.org | ||
| Luke Mewburn | lukem@NetBSD.org | ||
| Matt Thomas | matt@NetBSD.org | ||
| Christos Zoulas | christos@NetBSD.org | ||
|
| |||
| The portmasters (and their ports): | |||
| Allen Briggs | briggs@NetBSD.org | sandpoint | |
| Anders Magnusson | ragge@NetBSD.org | vax | |
| Andrey Petrov | petrov@NetBSD.org | sparc64 | |
| Ben Harris | bjh21@NetBSD.org | acorn26 | |
| Chris Gilbert | chris@NetBSD.org | cats | |
| Christian Limpach | cl@NetBSD.org | xen | |
| Eduardo Horvath | eeh@NetBSD.org | evbppc | |
| Frank van der Linden | fvdl@NetBSD.org | amd64 | |
| Frank van der Linden | fvdl@NetBSD.org | i386 | |
| IWAMOTO Toshihiro | toshii@NetBSD.org | hpcarm | |
| Ichiro Fukuhara | ichiro@NetBSD.org | hpcarm | |
| Ignatios Souvatzis | is@NetBSD.org | amiga | |
| Izumi Tsutsui | tsutsui@NetBSD.org | hp300 | |
| Izumi Tsutsui | tsutsui@NetBSD.org | news68k | |
| Jason Thorpe | thorpej@NetBSD.org | algor | |
| Jason Thorpe | thorpej@NetBSD.org | shark | |
| Jeremy Cooper | jeremy@NetBSD.org | sun3 | |
| Jonathan Stone | jonathan@NetBSD.org | pmax | |
| Julian Coleman | jdc@NetBSD.org | atari | |
| Jun-ichiro itojun Hagino | itojun@NetBSD.org | evbsh3 | |
| Jun-ichiro itojun Hagino | itojun@NetBSD.org | mmeye | |
| Kazuki Sakamoto | sakamoto@NetBSD.org | bebox | |
| Lennart Augustsson | augustss@NetBSD.org | pmppc | |
| Marcus Comstedt | marcus@NetBSD.org | dreamcast | |
| Martin Husemann | martin@NetBSD.org | sparc64 | |
| Matt DeBergalis | deberg@NetBSD.org | next68k | |
| Matt Fredette | fredette@NetBSD.org | hp700 | |
| Matt Fredette | fredette@NetBSD.org | sun2 | |
| Matt Thomas | matt@NetBSD.org | alpha | |
| Matt Thomas | matt@NetBSD.org | netwinder | |
| Matthias Drochner | drochner@NetBSD.org | cesfic | |
| NISHIMURA Takeshi | nsmrtks@NetBSD.org | x68k | |
| NONAKA Kimihiro | nonaka@NetBSD.org | prep | |
| Nathan Williams | nathanw@NetBSD.org | sun3 | |
| Noriyuki Soda | soda@NetBSD.org | arc | |
| Paul Kranenburg | pk@NetBSD.org | sparc | |
| Phil Nelson | phil@NetBSD.org | pc532 | |
| Reinoud Zandijk | reinoud@NetBSD.org | acorn32 | |
| Ross Harvey | ross@NetBSD.org | alpha | |
| S(/oren Jørvang | soren@NetBSD.org | cobalt | |
| S(/oren Jørvang | soren@NetBSD.org | sgimips | |
| Scott Reynolds | scottr@NetBSD.org | mac68k | |
| Shin Takemura | takemura@NetBSD.org | hpcmips | |
| Simon Burge | simonb@NetBSD.org | evbmips | |
| Simon Burge | simonb@NetBSD.org | evbppc | |
| Simon Burge | simonb@NetBSD.org | pmax | |
| Simon Burge | simonb@NetBSD.org | sbmips | |
| Steve Woodford | scw@NetBSD.org | evbsh5 | |
| Steve Woodford | scw@NetBSD.org | mvme68k | |
| Steve Woodford | scw@NetBSD.org | mvmeppc | |
| Tohru Nishimura | nisimura@NetBSD.org | luna68k | |
| Tsubai Masanari | tsubai@NetBSD.org | macppc | |
| Tsubai Masanari | tsubai@NetBSD.org | newsmips | |
| UCHIYAMA Yasushi | uch@NetBSD.org | hpcsh | |
| UCHIYAMA Yasushi | uch@NetBSD.org | playstation2 | |
| Wayne Knowles | wdk@NetBSD.org | mipsco | |
| Wolfgang Solfrank | ws@NetBSD.org | ofppc | |
|
| |||
| The NetBSD 2.0.2 Release Engineering team: | |||
| Grant Beattie | grant@NetBSD.org | ||
| Erik Berls | cyber@NetBSD.org | ||
| James Chacon | jmc@NetBSD.org | ||
| Julian Coleman | jdc@NetBSD.org | ||
| Håvard Eidnes | he@NetBSD.org | ||
| Jun-ichiro itojun Hagino | itojun@NetBSD.org | ||
| SAITOH Masanobu | msaitoh@NetBSD.org | ||
| Luke Mewburn | lukem@NetBSD.org | ||
| Matthias Scheler | tron@NetBSD.org | ||
| Curt Sampson | cjs@NetBSD.org | ||
| Jim Wise | jwise@NetBSD.org | ||
|
| |||
| NetBSD Developers: | |||
| Nathan Ahlstrom | nra@NetBSD.org | ||
| Steve Allen | wormey@NetBSD.org | ||
| Jukka Andberg | jandberg@NetBSD.org | ||
| Julian Assange | proff@NetBSD.org | ||
| Lennart Augustsson | augustss@NetBSD.org | ||
| Christoph Badura | bad@NetBSD.org | ||
| Bang Jun-Young | junyoung@NetBSD.org | ||
| Dieter Baron | dillo@NetBSD.org | ||
| Robert V. Baron | rvb@NetBSD.org | ||
| Grant Beattie | grant@NetBSD.org | ||
| Jason Beegan | jtb@NetBSD.org | ||
| Erik Berls | cyber@NetBSD.org | ||
| Hiroyuki Bessho | bsh@NetBSD.org | ||
| John Birrell | jb@NetBSD.org | ||
| Mason Loring Bliss | mason@NetBSD.org | ||
| Charles Blundell | cb@NetBSD.org | ||
| Rafal Boni | rafal@NetBSD.org | ||
| Manuel Bouyer | bouyer@NetBSD.org | ||
| John Brezak | brezak@NetBSD.org | ||
| Allen Briggs | briggs@NetBSD.org | ||
| Mark Brinicombe | mark@NetBSD.org | ||
| Aaron Brown | abrown@NetBSD.org | ||
| Andrew Brown | atatat@NetBSD.org | ||
| David Brownlee | abs@NetBSD.org | ||
| Frederick Bruckman | fredb@NetBSD.org | ||
| Jon Buller | jonb@NetBSD.org | ||
| Simon Burge | simonb@NetBSD.org | ||
| Robert Byrnes | byrnes@NetBSD.org | ||
| D'Arcy J.M. Cain | darcy@NetBSD.org | ||
| Dave Carrel | carrel@NetBSD.org | ||
| Daniel Carosone | dan@NetBSD.org | ||
| James Chacon | jmc@NetBSD.org | ||
| Bill Coldwell | billc@NetBSD.org | ||
| Julian Coleman | jdc@NetBSD.org | ||
| Ben Collver | ben@NetBSD.org | ||
| Jeremy Cooper | jeremy@NetBSD.org | ||
| Chuck Cranor | chuck@NetBSD.org | ||
| Alistair Crooks | agc@NetBSD.org | ||
| Aidan Cully | aidan@NetBSD.org | ||
| Johan Danielsson | joda@NetBSD.org | ||
| John Darrow | jdarrow@NetBSD.org | ||
| Matt DeBergalis | deberg@NetBSD.org | ||
| Rob Deker | deker@NetBSD.org | ||
| Chris G. Demetriou | cgd@NetBSD.org | ||
| Tracy Di Marco White | gendalia@NetBSD.org | ||
| Jaromír Dolecek | jdolecek@NetBSD.org | ||
| Andy Doran | ad@NetBSD.org | ||
| Roland Dowdeswell | elric@NetBSD.org | ||
| Emmanuel Dreyfus | manu@NetBSD.org | ||
| Matthias Drochner | drochner@NetBSD.org | ||
| Jun Ebihara | jun@NetBSD.org | ||
| Håvard Eidnes | he@NetBSD.org | ||
| Stoned Elipot | seb@NetBSD.org | ||
| Enami Tsugutomo | enami@NetBSD.org | ||
| Bernd Ernesti | veego@NetBSD.org | ||
| Erik Fair | fair@NetBSD.org | ||
| Gavan Fantom | gavan@NetBSD.org | ||
| Hubert Feyrer | hubertf@NetBSD.org | ||
| Jason R. Fink | jrf@NetBSD.org | ||
| Matt Fredette | fredette@NetBSD.org | ||
| Thorsten Frueauf | frueauf@NetBSD.org | ||
| Castor Fu | castor@NetBSD.org | ||
| Ichiro Fukuhara | ichiro@NetBSD.org | ||
| Quentin Garnier | cube@NetBSD.org | ||
| Thomas Gerner | thomas@NetBSD.org | ||
| Simon J. Gerraty | sjg@NetBSD.org | ||
| Justin Gibbs | gibbs@NetBSD.org | ||
| Chris Gilbert | chris@NetBSD.org | ||
| Eric Gillespie | epg@NetBSD.org | ||
| Adam Glass | glass@NetBSD.org | ||
| Michael Graff | explorer@NetBSD.org | ||
| Brian C. Grayson | bgrayson@NetBSD.org | ||
| Matthew Green | mrg@NetBSD.org | ||
| Andreas Gustafsson | gson@NetBSD.org | ||
| Jun-ichiro itojun Hagino | itojun@NetBSD.org | ||
| Juergen Hannken-Illjes | hannken@NetBSD.org | ||
| Charles M. Hannum | mycroft@NetBSD.org | ||
| Ben Harris | bjh21@NetBSD.org | ||
| Ross Harvey | ross@NetBSD.org | ||
| Eric Haszlakiewicz | erh@NetBSD.org | ||
| John Hawkinson | jhawk@NetBSD.org | ||
| HAYAKAWA Koichi | haya@NetBSD.org | ||
| John Heasley | heas@NetBSD.org | ||
| René 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 | ||
| Eduardo Horvath | eeh@NetBSD.org | ||
| Nick Hudson | skrll@NetBSD.org | ||
| Shell Hung | shell@NetBSD.org | ||
| Martin Husemann | martin@NetBSD.org | ||
| Dean Huxley | dean@NetBSD.org | ||
| Love Hörnquist Åstrand | lha@NetBSD.org | ||
| Bernardo Innocenti | bernie@NetBSD.org | ||
| Tetsuya Isaki | isaki@NetBSD.org | ||
| ITOH Yasufumi | itohy@NetBSD.org | ||
| IWAMOTO Toshihiro | toshii@NetBSD.org | ||
| Matthew Jacob | mjacob@NetBSD.org | ||
| Soren Jacobsen | snj@NetBSD.org | ||
| Lonhyn T. Jasinskyj | lonhyn@NetBSD.org | ||
| Darrin Jewell | dbj@NetBSD.org | ||
| Chris Jones | cjones@NetBSD.org | ||
| Søren Jørvang | soren@NetBSD.org | ||
| Takahiro Kambe | taca@NetBSD.org | ||
| Antti Kantee | pooka@NetBSD.org | ||
| Masanori Kanaoka | kanaoka@NetBSD.org | ||
| Mattias Karlsson | keihan@NetBSD.org | ||
| KAWAMOTO Yosihisa | kawamoto@NetBSD.org | ||
| Mario Kemper | magick@NetBSD.org | ||
| Min Sik Kim | minskim@NetBSD.org | ||
| Thomas Klausner | wiz@NetBSD.org | ||
| Klaus Klein | kleink@NetBSD.org | ||
| Wayne Knowles | wdk@NetBSD.org | ||
| Takayoshi Kochi | kochi@NetBSD.org | ||
| John Kohl | jtk@NetBSD.org | ||
| Daniel de Kok | daniel@NetBSD.org | ||
| Paul Kranenburg | pk@NetBSD.org | ||
| Martti Kuparinen | martti@NetBSD.org | ||
| Kevin Lahey | kml@NetBSD.org | ||
| Johnny C. Lam | jlam@NetBSD.org | ||
| Martin J. Laubach | mjl@NetBSD.org | ||
| Greg Lehey | grog@NetBSD.org | ||
| Ted Lemon | mellon@NetBSD.org | ||
| Christian Limpach | cl@NetBSD.org | ||
| Frank van der Linden | fvdl@NetBSD.org | ||
| Joel Lindholm | joel@NetBSD.org | ||
| Mike Long | mikel@NetBSD.org | ||
| Warner Losh | imp@NetBSD.org | ||
| Tomasz Luchowski | zuntum@NetBSD.org | ||
| Federico Lupi | federico@NetBSD.org | ||
| Brett Lymn | blymn@NetBSD.org | ||
| Paul Mackerras | paulus@NetBSD.org | ||
| Anders Magnusson | ragge@NetBSD.org | ||
| MAEKAWA Masahide | gehenna@NetBSD.org | ||
| David Maxwell | david@NetBSD.org | ||
| Dan McMahill | dmcmahill@NetBSD.org | ||
| Gregory McGarry | gmcgarry@NetBSD.org | ||
| Jared D. McNeill | jmcneill@NetBSD.org | ||
| Neil J. McRae | neil@NetBSD.org | ||
| Perry Metzger | perry@NetBSD.org | ||
| Simas Mockevicius | symka@NetBSD.org | ||
| Juan Romero Pardines | xtraeme@NetBSD.org | ||
| Julio M. Merino Vidal | jmmv@NetBSD.org | ||
| Minoura Makoto | minoura@NetBSD.org | ||
| Luke Mewburn | lukem@NetBSD.org | ||
| der Mouse | mouse@NetBSD.org | ||
| Joseph Myers | jsm@NetBSD.org | ||
| Ken Nakata | kenn@NetBSD.org | ||
| Takeshi Nakayama | nakayama@NetBSD.org | ||
| Phil Nelson | phil@NetBSD.org | ||
| Bob Nestor | rnestor@NetBSD.org | ||
| NISHIMURA Takeshi | nsmrtks@NetBSD.org | ||
| Tohru Nishimura | nisimura@NetBSD.org | ||
| NONAKA Kimihiro | nonaka@NetBSD.org | ||
| Jesse Off | joff@NetBSD.org | ||
| Tatoku Ogaito | tacha@NetBSD.org | ||
| OKANO Takayoshi | kano@NetBSD.org | ||
| Masaru Oki | oki@NetBSD.org | ||
| Atsushi Onoe | onoe@NetBSD.org | ||
| Greg Oster | oster@NetBSD.org | ||
| Jonathan Perkin | sketch@NetBSD.org | ||
| Herb Peyerl | hpeyerl@NetBSD.org | ||
| Matthias Pfaller | matthias@NetBSD.org | ||
| Chris Pinnock | cjep@NetBSD.org | ||
| Adrian Portelli | adrianp@NetBSD.org | ||
| Dante Profeta | dante@NetBSD.org | ||
| Chris Provenzano | proven@NetBSD.org | ||
| Niels Provos | provos@NetBSD.org | ||
| Michael Rauch | mrauch@NetBSD.org | ||
| Marc Recht | recht@NetBSD.org | ||
| Darren Reed | darrenr@NetBSD.org | ||
| Jeremy C. Reed | reed@NetBSD.org | ||
| Tyler R. Retzlaff | rtr@NetBSD.org | ||
| Scott Reynolds | scottr@NetBSD.org | ||
| Michael Richardson | mcr@NetBSD.org | ||
| Tim Rightnour | garbled@NetBSD.org | ||
| Gordon Ross | gwr@NetBSD.org | ||
| Steve Rumble | rumble@NetBSD.org | ||
| Ilpo Ruotsalainen | lonewolf@NetBSD.org | ||
| Heiko W. Rupp | hwr@NetBSD.org | ||
| David Sainty | dsainty@NetBSD.org | ||
| SAITOH Masanobu | msaitoh@NetBSD.org | ||
| Kazuki Sakamoto | sakamoto@NetBSD.org | ||
| Curt Sampson | cjs@NetBSD.org | ||
| Wilfredo Sanchez | wsanchez@NetBSD.org | ||
| Ty Sarna | tsarna@NetBSD.org | ||
| SATO Kazumi | sato@NetBSD.org | ||
| Jan Schaumann | jschauma@NetBSD.org | ||
| Matthias Scheler | tron@NetBSD.org | ||
| Karl Schilke (rAT) | rat@NetBSD.org | ||
| Amitai Schlair | schmonz@NetBSD.org | ||
| Konrad Schroder | perseant@NetBSD.org | ||
| Lubomir Sedlacik | salo@NetBSD.org | ||
| Christopher SEKIYA | sekiya@NetBSD.org | ||
| Reed Shadgett | dent@NetBSD.org | ||
| John Shannon | shannonjr@NetBSD.org | ||
| Tim Shepard | shep@NetBSD.org | ||
| Takeshi Shibagaki | shiba@NetBSD.org | ||
| Naoto Shimazaki | igy@NetBSD.org | ||
| Takao Shinohara | shin@NetBSD.org | ||
| Takuya SHIOZAKI | tshiozak@NetBSD.org | ||
| Chuck Silvers | chs@NetBSD.org | ||
| Thor Lancelot Simon | tls@NetBSD.org | ||
| Jeff Smith | jeffs@NetBSD.org | ||
| Noriyuki Soda | soda@NetBSD.org | ||
| Wolfgang Solfrank | ws@NetBSD.org | ||
| SOMEYA Yoshihiko | someya@NetBSD.org | ||
| Bill Sommerfeld | sommerfeld@NetBSD.org | ||
| Ignatios Souvatzis | is@NetBSD.org | ||
| Bill Squier | groo@NetBSD.org | ||
| Jonathan Stone | jonathan@NetBSD.org | ||
| Bill Studenmund | wrstuden@NetBSD.org | ||
| Kevin Sullivan | sullivan@NetBSD.org | ||
| SUNAGAWA Keiki | kei@NetBSD.org | ||
| Kimmo Suominen | kim@NetBSD.org | ||
| Shin Takemura | takemura@NetBSD.org | ||
| TAMURA Kent | kent@NetBSD.org | ||
| Shin'ichiro TAYA | taya@NetBSD.org | ||
| Ian Lance Taylor | ian@NetBSD.org | ||
| Matt Thomas | matt@NetBSD.org | ||
| Jason Thorpe | thorpej@NetBSD.org | ||
| Christoph Toshok | toshok@NetBSD.org | ||
| Tsubai Masanari | tsubai@NetBSD.org | ||
| Izumi Tsutsui | tsutsui@NetBSD.org | ||
| UCHIYAMA Yasushi | uch@NetBSD.org | ||
| Masao Uebayashi | uebayasi@NetBSD.org | ||
| Shuichiro URATA | ur@NetBSD.org | ||
| Todd Vierling | tv@NetBSD.org | ||
| Aymeric Vincent | aymeric@NetBSD.org | ||
| Paul Vixie | vixie@NetBSD.org | ||
| Krister Walfridsson | kristerw@NetBSD.org | ||
| Lex Wennmacher | wennmach@NetBSD.org | ||
| Leo Weppelman | leo@NetBSD.org | ||
| Assar Westerlund | assar@NetBSD.org | ||
| Todd Whitesel | toddpw@NetBSD.org | ||
| Nathan Williams | nathanw@NetBSD.org | ||
| Rob Windsor | windsor@NetBSD.org | ||
| Dan Winship | danw@NetBSD.org | ||
| Jim Wise | jwise@NetBSD.org | ||
| Michael Wolfson | mbw@NetBSD.org | ||
| Steve Woodford | scw@NetBSD.org | ||
| Colin Wood | ender@NetBSD.org | ||
| YAMAMOTO Takashi | yamt@NetBSD.org | ||
| Yuji Yamano | yyamano@NetBSD.org | ||
| Reinoud Zandijk | reinoud@NetBSD.org | ||
| Maria Zevenhoven | maria7@NetBSD.org | ||
| Christos Zoulas | christos@NetBSD.org | ||
|
| |||
| Other contributors: | |||
| Dave Burgess | burgess@cynjut.infonet.net | ||
| Brian R. Gaeke | brg@dgate.org | ||
| Brad Grantham | grantham@tenon.com | ||
| Lawrence Kesteloot | kesteloo@cs.unc.edu | ||
| Waldi Ravens | waldi@moacs.indiv.nl.net |
All product names mentioned herein are trademarks or registered trademarks of their respective owners.
The following notices are required to satisfy the license terms of the software that we have mentioned in this document:
This product includes software developed by the University of
California, Berkeley and its contributors.