This document describes the installation procedure for
NetBSD1.5
on the
mvme68k
platform. It is available in four different formats titled
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.
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 thirty-one different system architectures featuring twelve distinct
families of CPUs, and is being ported to more. The
NetBSD1.5
release contains complete binary releases for fifteen different
machine types. (The sixteen remaining are not fully supported at this time
and are thus not part of the binary distribution. For information on
them, please see the
NetBSD
web site at
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
NetBSD1.5
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 userland 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 one year of
development that went into the
NetBSD1.5
release. Some highlights include:
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.
This is the fifth major release of
NetBSD
for the mvme68k series of boards.
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
NetBSD1.5
release is organized as follows:
In addition to the files and directories listed above, there is one
directory per architecture, for each of the architectures for which
NetBSD1.5
has a binary distribution.
There are also
The source distribution sets can be found in subdirectories of the
All the above source sets are located in the
The source sets are distributed as compressed tar files. They may be
unpacked into
The
The split distributions may be reassembled and extracted with
cat
as follows:
In each of the source distribution set directories, there are
files which contain the checksums of the files in the directory:
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
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 mvme68k binary distribution sets are distributed as gzipped tar files
named with the extension
.tgz, e.g.
The instructions given for extracting the source sets work equally
well for the binary sets, but it is worth noting that if you use that
method, the files are
The following are included in the
NetBSD/mvme68k
1.5 runs on Motorola
MVME147
,
MVME162-LX
and
MVME167
Single Board Computers.
The minimal configuration requires 8 MB of RAM and ~200 MB of disk space.
To install the entire system requires much more disk space (approx.
600 MB additional space is necessary for full sources. Double that if you
want to recompile it all!). To run X (clients only) or compile the system,
more RAM is recommended. Good performance requires 16 MB of RAM, or 32 MB
when running the X Window System.
Note that you can install
NetBSD
1.5
on a system with only 4 MB of onboard RAM, but you will need to use a
VMEbus RAM card with at least another 4 MB to augment the onboard
memory in order to actually install the system.
Here is a table of recommended HD partition sizes for a full install:
Changes Since The Last Release
Kernel
ktruss(1)
.
swapctl(8)
.
Networking
pcap(3)
is incremented and you may need to recompile userland tools.
The KAME IPv6 part includes results from the unified-ipv6 effort.
File system
/
)
on a RAID set.
rpc.lockd(8)
)
now works.
Security
sysctl(3)
interfaces to various elements of process and system information,
allowing programs such as
ps(1)
,
dmesg(1)
and the like to operate without recompilation after kernel upgrades,
and remove the necessity to run setgid kmem (thus improving system
security).
System administration and user tools
rc(8)
system startup and shutdown scripts to an
`rc.d'
mechanism, with separate control scripts for each service, and
appropriate dependency ordering provided by
rcorder(8)
.
postfix(1)
provided as alternative mail transport agent to
sendmail(8)
.
useradd(8)
,
usermod(8)
,
userdel(8)
,
groupadd(8)
,
groupmod(8)
,
and
groupdel(8)
added to the system.
/etc/login.conf
)
from
BSD/OS.
at(1)
and
w(1)
.
ftpd(8)
providing features found in larger and less secure FTP daemons,
such as user classes, connection limits, improved support for
virtual hosting, transfer statistics, transfer rate throttling,
and support for various IETF ftpext working group extensions.
ftp(1)
client has been improved even further, including
transfer rate throttling, improved URL support, command line uploads.
See the man page for details.
Miscellaneous
/usr/share/misc/style
)
to use ANSI C only (instead of K&R) and reflect current (best) practice,
and begin migrating the
NetBSD
source code to follow it.
curses(3)
library, including support for color.
file(1)
,
ipfilter(4)
,
ppp(4)
,
and
sendmail(8)
to the latest stable release.
The Future of NetBSD
Sources of NetBSD
NetBSD 1.5 Release Contents
.../NetBSD-1.5/
CHANGES
LAST_MINUTE
MIRRORS
README.files
TODO
patches/
source/
README.export-control
files sprinkled liberally throughout the
distribution tree, which point out that there are some portions of the
distribution that may be subject to
export regulations of the United States, e.g.
code under
src/crypto
and
src/sys/crypto
.
It is your responsibility
to determine whether or not it is legal for you to export these portions
and to act accordingly.
source
subdirectory of the distribution tree. They contain the
complete sources to the system. The source distribution sets
are as follows:
22.3 MB gzipped, 98.8 MB uncompressed
5.6 MB gzipped, 57.0 MB uncompressed
3.3 MB gzipped, 13.2 MB uncompressed
24.2 MB gzipped, 120.6 MB uncompressed
config(8)
,
and
dbsym(8)
.
17.6 MB gzipped, 88.6 MB uncompressed
35.2 MB gzipped, 176.8 MB uncompressed
source/sets
subdirectory of the distribution tree.
/usr/src
with the command:
#
( cd / ; tar -zxpf - ) < set_name.tgz
sets/Split/
subdirectory contains split
versions of the source sets for those users who need to load the
source sets from floppy or otherwise need a split distribution. The
split sets are named
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.)
#
cat set_name.?? | ( cd / ; tar -zxpf - )
BSDSUM
CKSUM
MD5
SYSVSUM
NetBSD/mvme68k subdirectory structure
The mvme68k-specific portion of the
NetBSD1.5
release is found in the
mvme68k
subdirectory of the distribution:
.../NetBSD-1.5/mvme68k/
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/
kernel/
netbsd.GENERIC.gz
netbsd.VME147.gz
netbsd.VME162.gz
netbsd.VME167.gz
sets/
installation/
miniroot/
netboot/
tapeimage/
Binary distribution sets
The
NetBSD
mvme68k
binary distribution sets contain the binaries which
comprise the
NetBSD1.5
release for the mvme68k. There are eight binary distribution sets.
The binary distribution sets can be found in the
mvme68k/binary/sets
subdirectory
of the
NetBSD1.5
distribution tree, and are as follows:
15.5 MB gzipped, 41.2 MB uncompressed
/usr/include
)
and the various system libraries (except the shared
libraries, which are included as part of the
base
set). This set also includes the manual pages for
all of the utilities it contains, as well as the
system call and library manual pages.
11.8 MB gzipped, 39.5 MB uncompressed
/etc
and in several other places. This set
must
be installed if you are installing the system from scratch, but should
not
be used if you are upgrading. (If you are upgrading,
it's recommended that you get a copy of this set and
carefully
upgrade your configuration files by hand.)
0.1 MB gzipped, 0.6 MB uncompressed
3.0 MB gzipped, 7.4 MB uncompressed
GENERIC
kernel, named
/netbsd
.
You must
install this distribution set.
0.7 MB gzipped, 1.4 MB uncompressed
5.0 MB gzipped, 19.9 MB uncompressed
/usr/share
.
2.6 MB gzipped, 10.1 MB uncompressed
groff(1)
,
all related programs, and their manual pages.
1.3 MB gzipped, 4.7 MB uncompressed
2.6 MB gzipped, 8.2 MB uncompressed
1.7 MB gzipped, 7.2 MB uncompressed
0.2 MB gzipped, 0.7 MB uncompressed
6.2 MB gzipped, 7.5 MB uncompressed
base.tgz
.
/
-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 -xpf
command from
/
.
mvme68k/installation
directory:
miniroot/
miniroot.gz
netboot/
sboot
netboot
tapeimage/
stboot
bootst
netbsd-rd.gz
GENERIC
kernel and a built in RAMDISK
with just enough tools to partition a disk, dump the miniroot kernel
to it and make the disk bootable. This must be the third file written
to the tape.
NetBSD/mvme68k System Requirements and Supported Devices
Partition | Suggested | Needed |
/ (root) | 32 MB | 26 MB |
/usr | 200 MB | 150 MB |
/var | 32 MB | 6 MB |
swap | 2-3 *RAM 16 MB
| |
Note that the NetBSD/mvme68k installation procedure uses a miniroot image which is placed into the swap area of the disk. The swap partition must be large enough to hold this miniroot image (> 7.5 MB).
If it's not on the above lists, there is no support for it in this release.
Installation is supported from several media types, including:
Note that installing on a `bare' machine requires either a bootable tape drive or an ethernet to a compatible NFS server. MVME147 may also need to be booted over an RS232 connection.
The procedure for transferring the distribution sets onto installation media depends on the type of media. Instructions for each type of media are given below.
In order to create installation media, you will need all the files and subdirectories in these two directories:
.../NetBSD-1.5/mvme68k/installation
.../NetBSD-1.5/mvme68k/binary
The boot tape is created as follows:
#
cd .../NetBSD-1.5/mvme68k/installation
#
set T = /dev/nrst0
#
mt -f $T rewind
#
dd if=tapeimage/stboot of=$T
#
dd if=tapeimage/bootst of=$T obs=8k conv=osync
#
gzip -dc tapeimage/netbsd-rd.gz | dd of=$T obs=8k conv=osync
#
gzip -dc miniroot/miniroot.gz | dd of=$T obs=8k conv=osync
#
mt -f $T rewind
The installation set tape is created as follows:
#
cd .../NetBSD-1.5/mvme68k/binary/sets
#
set T = /dev/nrst0
#
mt -f $T rewind
#
for f in base etc comp games man misc text; do
gzip -d < $f.tgz | dd of=$T bs=8k
#
done
#
mt -f $T rewind
If the tape does not work as expected, you may need to explicitly set the EOF mark at the end of each tape segment. Consult the tape-related manual pages on the system where the tapes are created for more details.
If you are using a
NetBSD
system as the boot-server, have a look at
the
Booting an MVME147 from ethernet is not possible without first downloading
a small bootstrap program (sboot) via RS232. See the section entitled
Installing from NFS
for details on how to accomplish this.
sboot expects to be able to download a second stage bootstrap
program via TFTP after having acquired its IP address through RARP
It will look for a filename derived from the machine's IP address
expressed in hexadecimal, with an extension of
`
The
MVME162-LX
and
MVME167
boot ROMs have code builtin to boot over ethernet from a
TFTP server. You should configure it to download the same
The netboot program will query a bootparamd server to find the NFS
server address and path name for its root, and then load a kernel from
that location. The server should have a copy of the netbsd-rd kernel in
the root area for your client (no other files are needed in the client
root, although it might be a convenient place to put the uncompressed
miniroot image) and
The client will need access to the miniroot image, which can be
provided using NFS or remote shell. If using NFS, miniroot.gz should be
expanded on the server, because doing so from the RAMDISK shell is not
so easy. The unzipped miniroot takes about 7.5 MB of space.
If you will be installing
NetBSD
on several clients, it may be useful
to know that you can use a single NFS root for all the clients as long
as they only use the netbsd-rd kernel. There will be no conflict
between clients because the RAM-disk kernel will not use the NFS root.
No swap file is needed; the RAM-disk kernel does not use that either.
This method, of course, requires network access to an FTP server.
This might be a local system, or it might even be ftp.netbsd.org
itself. If you wish to use ftp.netbsd.org as your FTP file
server, you may want to keep the following information handy:
mvme68k machines usually need little or no preparation before installing
NetBSD,
other than the usual, well advised precaution of
backing up all data
on any attached storage devices.
The exception to the above is that
MVME162-LX
and
MVME167
boards require a jumper to be removed before
NetBSD
can be installed.
On
MVME162-LX
pins 1-2 of jumper J11
must
be removed.
On
MVME167
pins 1-2 of jumper J1
must
be removed.
Once you've made any necessary jumper changes,
the following instructions should make your machine
``NetBSD Ready''.
Power-up your MVME147 board. You should have the
bug prompt:
Onboard RAM start = $00000000, stop = $007FFFFF
147-Bug>
Or, if you have an MVME162-LX or MVME167 board (the following boot
message is from MVME167; MVME162-LX is similar):
Local Memory Found =02000000 (&33554432)
MPU Clock Speed =33Mhz
167-Bug>
Make sure the RAM size looks ok (if you've got an 8 MB MVME147 or a
32 MB MVME167 you should
have the same value as we do). Also make sure the clock is ticking:
Note that
NetBSD
bases its year at 1968, and adds the year offset in
the system's real-time clock to get the current year. So the
Also make sure that your board's ethernet address is initialised to
the correct value. You'll find the address on a label on the inside of
the MVME147's front panel, and on the VMEbus P2 connector of the MVME162-LX
and MVME167.
On the MVME147, enter the last five digits of the address
using the
lsad
command. On the MVME162-LX and MVME167, you should use the
cnfg
command.
To install successfully to a local SCSI disk, you need to ensure that
the system is aware of what targets are connected to the SCSI bus. This
can be done by issueing the following command:
At this point, Bug will scan for any attached SCSI devices. After
a short delay, a list of SCSI devices will be displayed. 147Bug will
ask if LUNs should be assigned from SCSI ids, to which you should
answer Y. You should also answer Y when asked if the information is
to be saved to NVRAM. 16xBug does not prompt for this information.
The following installation instructions will assume that your target
SCSI disk drive appears at SCSI-ID 0. If you have a tape drive, the
instructions assume is is configured for SCSI-ID 5. When the RAMDISK
root boots,
NetBSD
will refer to these devices as
Installing
NetBSD
is a relatively complex process, but if you have
this document in hand it should not be too difficult.
There are several ways to install
NetBSD
onto your disk. If your
machine has a tape drive the easiest way is
Installing from tape
(details below). If your machine is on a network with a suitable
NFS server, then
Installing from NFS
is the next best method.
Otherwise, if you have another mvme68k machine running
NetBSD
you can
initialize the disk on that machine and then move the disk.
As mentioned earlier, this assumes your tape is jumpered for SCSI-ID 5.
As the tape loads (which may take 20 to 30 seconds), you will see a
series of status messages. It may be useful if you can capture these
messages to a file, or a scrollable xterm window. In particular, you
should make a note of the lines which describe the geometry of the
SCSI disks detected by
NetBSD.
They are of the form:
The information of most interest is the number of sectors; for the ficticious
disk above, it's 1638400. You will need this number when you come to create
a disklabel for that drive.
Here is an example of an MVME147 system booting from tape:
Booting from: VME147, Controller 5, Device 0
Loading: Operating System
Volume: NBSD
IPL loaded at: $003F0000
>> BSD MVME147 tapeboot
578616+422344+55540+[46032+51284]=0x11a6e4
Start @ 0x8000 ...
Copyright (c) 1996, 1997, 1998, 1999, 2000
The NetBSD Foundation, Inc. All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
NetBSD 1.5 (RAMDISK) #1: Sun Oct 29 16:19:04 GMT 2000
steve@fatbob:/usr/src/sys/arch/mvme68k/compile/RAMDISK
Motorola MVME-147S: 25MHz MC68030 CPU+MMU, MC68882 FPU
real mem = 7237632
avail mem = 6381568
using 88 buffers containing 360448 bytes of memory
mainbus0 (root)
pcc0 at mainbus0: Peripheral Channel Controller, rev 0, vecbase 0x40
clock0 at pcc0 offset 0x0 ipl 5: Mostek MK48T02, 2048 bytes of NVRAM
.
.
Finally, you will see the following "welcome" message:
This environment is designed to do only four things:
1: Partititon your disk (use the command: edlabel /dev/rsd0c)
2: Copy a miniroot image into the swap partition (/dev/rsd0b)
3: Make that partition bootable (using 'installboot')
4: Reboot (using the swap partition, i.e. /dev/sd0b).
Copying the miniroot can be done several ways, allowing the source
of the miniroot image to be on any of these:
boot tape, NFS server, TFTP server, rsh server
The easiest is loading from tape, which is done as follows:
mt -f /dev/nrst0 rewind
mt -f /dev/nrst0 fsf 3
dd bs=8k if=/dev/nrst0 of=/dev/rsd0b
(For help with other methods, please see the install notes.)
To reboot using the swap partition after running installboot, first
use
halt,
then at the Bug monitor prompt use a command like:
1x7Bug> bo 0,,b:
To view this message again, type: cat /.welcome
ssh:
You must now create a disklabel on the disk you wish to use for the
root file system
(
Partitions are named
The
raw partition is special;
NetBSD
is able to use it even if the
disk has no label. You should never create a file system on the Raw
Partition, even on a non-boot disk.
It is good practice to put
You are not required to define any partitions beyond
To create the disklabel and partitions, use the
The program shows what commands it recognizes;
print,
modify,
write,
and
quit.
It will accept the first letter of a command if
you don't feel like typing each one in full.
To start creating the basic partitions, you should enter
m (modify)
at the edlabel prompt, then enter the letter corresponding to the first
partition, a.
When you enter the start and length of a partition, you can use either
blocks or cylinder/track/sector notation. If this is the first time
you've partitioned a disk for
NetBSD,
it's probably easiest to use block
notation. The above example creates partition
`
The
Next, create a swap partition (b). Note that the minimum size of this
swap partition should be 8 MB, otherwise you won't be able to use a
miniroot to complete the
NetBSD
installation!
Here, we specify a value for
As you can see, we've chosen to assign the remainder of the disk to
Note that the above partition sizes are just guidelines. If your disk is
large enough, you should resize the partitions appropriately and
perhaps also create a /var partition as well.
You now need to write this new disklabel, together with the partition
details you've just entered, to disk. You might also try the
`p'
command
to view the partitions. Once written, you can quit back to ssh using
`q'.
a (root) 0 (0/00/00) 65536 (32/00/00) 4.2BSD
b (swap) 65536 (32/00/00) 32768 (48/00/00) swap
c (disk) 0 (0/00/00) 1638400 (800/00/00) unused
d (user) 98304 (48/00/00) 1540096 (752/00/00) 4.2BSD
Now that your disk's partitioned, you need to get the proper installation
miniroot image onto it. The miniroot image is designed to be copied into
the swap partition of your disk. This is a safe place which won't be
overwritten by the installation procedure. From the ssh prompt, use the
following commands to copy the miniroot image from tape to swap (b).
The disk and the miniroot must now be made bootable using the
You can now shutdown the system.
Resetting the MVME162-LX and MVME167 boards are very similar.
You should now reboot from that just installed miniroot. See the section
entitled
Booting the miniroot
for details.
To get started on the MVME147, you need to download
Which will look like this:
away for 11 seconds
Now, if you want to do it through serial line 1, then connect serial
line one to a machine. At the
Once you've got the
See below for the next step in booting MVME147.
The MVME162-LX and MVME167 boards are able to download netboot
directly using TFTP.
To enable this, you must first configure the networking parameters
on the board as described in the section entitled "Preparing your System
for
NetBSD
Installation. On a properly configured MVME162-LX or MVME167, all you need
to type is:
For all board types, the boot messages are very similar:
NetBSD 1.5 (RAMDISK) #1: Sun Oct 29 16:19:04 GMT 2000
steve@fatbob:/usr/src/sys/arch/mvme68k/compile/RAMDISK
Motorola MVME-147S: 25MHz MC68030 CPU+MMU, MC68882 FPU
real mem = 7237632
avail mem = 6381568
using 88 buffers containing 360448 bytes of memory
mainbus0 (root)
pcc0 at mainbus0: Peripheral Channel Controller, rev 0, vecbase 0x40
clock0 at pcc0 offset 0x0 ipl 5: Mostek MK48T02, 2048 bytes of NVRAM
.
.
After the boot program loads the
You now need to create a disklabel with partition information on the
SCSI disk on which you intend to create your root file system
(
You must now configure the network interface before you can access the
NFS server containing the miniroot image. For example the command:
will bring up the MVME147 network interface
will bring up the MVME162-LX or MVME167 network interface
You can look at the route table using:
Now mount the NFS file system containing the miniroot image:
The procedure is simpler if you have space for an expanded (not
compressed) copy of the miniroot image. In that case:
Otherwise, you will need to use
zcat
to expand the miniroot image while copying.
This is tricky because the
ssh
program (small shell) does not handle
To load the miniroot using rsh to the server, you would use a pair
of commands similar to the above. Here is another example:
You must now make the disk bootable. Refer to the previous section on
installing from tape, where it describes how to run
installboot.
This is immediately following the part which explains how to copy the
miniroot from tape.
The corresponding 162Bug or 167Bug boot command is:
The command line parameters above are:
You should see a bunch of boot messages, followed by messages from
the miniroot kernel just as you did when the
You will then be prompted to enter the root device. Since the miniroot
was booted from the swap partition, you should enter
Congratulations! The system should now be running the miniroot
installation program.
The miniroot's install program will:
Note that partition sizes and offsets are expressed
in sectors. When you fill out the disklabel, you will
need to specify partition types and file system parameters.
If you're unsure what these values should be, use the
following defaults:
If the partition will be a swap partition, use the following:
Note that partition
`
The number of partitions is currently fixed at 8.
First-time installation on a system through a method other than the
installation program is possible, but strongly discouraged.
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.
If you or the installation software haven't done any configuration of
and with the root file system
(
If your
If you have
Other values that need to be set in
or, if you have
myname.my.dom
in
To enable proper hostname resolution, you will also want to add an
Other files in
After reboot, you can log in as
Use the
If you have installed the X window system, look at the files in
Don't forget to add
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.
After extracting, then see the
is likely to give you more information on these files.
It is possible to easily upgrade your existing
NetBSD/mvme68k
system
using the upgrade program in the miniroot. If you wish to upgrade
your system by this method, simply select the
upgrade
option once the miniroot has booted.
The upgrade program with then guide you through the procedure.
The upgrade program will:
While using the miniroot's upgrade program is the preferred method
of upgrading your system, it is possible to upgrade your system
manually. To do this, follow the following procedure:
E.g.:
root-disk
could be
Users upgrading from previous versions of
NetBSD
may wish to bear the
following problems and compatibility issues in mind when upgrading to
NetBSD1.5.
In previous releases of
NetBSD,
At system startup,
At system shutdown,
Local and third-party scripts may be installed into
Previous releases of
NetBSD
disabled a feature of
Due to
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
to read the documentation for
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
[email protected].
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:
[email protected].
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, 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:
[email protected].
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.
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)
diskless(8)
manual page for guidelines on how to proceed with
this. If the server runs another operating system, consult the
documentation that came with it (i.e.
add_client(8)
on
SunOS).
.147
'.
For example, an MVME147 with IP address 130.115.144.11 will make an TFTP
request for
8273900B.147
.
Normally, this file is just a symbolic link to the
NetBSD/mvme68k
netboot
program, which should be located in a place
where the TFTP daemon can find it (remember, many TFTP daemons run in
a chroot'ed environment). The netboot program may be found in the
install directory of this distribution.
netboot
program as is used for
MVME147.
/etc/bootparams
on the server should have an entry for your client and its root directory.
Note that you should rename the
netbsd-rd
kernel to just
netbsd
in the client's root directory before trying to netboot the client.
Install/Upgrade from CD-ROM
This method requires that you boot from another device (i.e. tape
or network, as described above). You may need to make a boot tape
on another machine using the files provided on the CD-ROM. Once
you have booted netbsd-rd (the RAMDISK kernel) and loaded the
miniroot, you can load any of the distribution sets directly from
the CD-ROM. The
install
program in the miniroot automates the
work required to mount the CD-ROM and extract the files.
Install/Upgrade via FTP
This method requires that you boot from another device (i.e. tape
or network, as described above). You may need to make a boot tape
on another machine using the files in .../install (which you get
via FTP). Once you have booted netbsd-rd (the RAM-disk kernel)
and loaded the miniroot, you can load any of the distribution sets
over the net using FTP. The
install
program in the miniroot
automates the work required to configure the network interface and
transfer the files.
No IP Address: ftp.netbsd.org
Login: anonymous
Password: <your e-mail address>
Server path: /pub/NetBSD/NetBSD-1.5/mvme68k/binary
Preparing your System for NetBSD installation
COLD Start
MVME167 Debugger/Diagnostics Release Version 2.3 - 02/25/94
COLD Start
1xx-Bug>
time
Sunday
12/21/31
16:25:14
1xx-Bug>
time
Sunday
12/21/31
16:25:15
1xx-Bug>
31
here
equates to 1999. You may have to adjust your clock using the
set
command to comply with
NetBSD 's
requirements. Don't worry if the
`Day of the week'
is not correct, as
NetBSD
doesn't use it.
Motorola has acknowledged a year 2000 bug in some versions of the MVME147
whereby the day of the week
doesn't get set correctly by the 147Bug PROM.
does not affect
NetBSD !
1xx-Bug>
iot;t
sd0
and
rst0
respectively. You may wish to note these down; you'll be using them
a lot. :-)
Installing the NetBSD System
Installing from tape
Create the
NetBSD/mvme68k
1.5 boot tape as described in the section
entitled
Preparing a boot tape.
Then, with the tape in the drive, type the following at the Bug prompt:
147-Bug>
bo 5
16x-Bug>
bo 0,50
sd0 at scsibus0 targ 0 lun 0: <Maker, Disk, Foo> SCSI1 0/direct fixed
sd0: 800 MB, 800 cyl, 16 head, 128 sec, 512 bytes/sect x 1638400 sectors
RAM address from VMEbus = $00000000
Welcome to the NetBSD/mvme68k RAMDISK root!
/
).
This will usually be
sd0
.
The disklabel is used by
NetBSD to identify the starting block and size of each partition on
the disk.
sd0a
,
sd0b
,
sd0c
,
etc,
up to
sd0h
.
The mvme68k port of
NetBSD
makes some assumptions about the first three partitions on a boot disk:
sd0a
/
).
sd0b
sd0c
/usr
on a different partition than
/
(root, AKA
sd0a
).
So, the first available partition for
/usr
is
sd0d
.
Refer to the section entitled
NetBSD System Requirements and Supported Devices
for information on the recommended sizes of the
/
(root),
/usr
and swap partitions.
sd0d
,
but if you
have a large disk drive, you might want to create several other partitions
for file systems such as
/home
or
/usr/src
.
Note that at this time you
are only required to partition the root/boot disk; you will get the
opportunity to partition any other disks in your system from the main
miniroot
installation program.
edlabel
program, passing it the name of the Raw Partition of your root/boot disk.
ssh:
edlabel /dev/rsd0c
edlabel
menu:
print
-
display
the
current
disk
label
modify
-
prompt
for
changes
to
the
label
write
-
write
the
new
label
to
disk
quit
-
terminate
program
edlabel>
edlabel>
m
modify
subcommands:
@
: modify
disk
parameters
a-h
: modify
partition
s
: standarize
geometry
q
: quit
this
subcommand
edlabel/modify>
a
a
(root)
0
(0/00/00)
0
(0/00/00)
unused
start
as
<blkno>
or
<cyls/trks/sects>
: 0
length
as
<nblks>
or
<cyls/trks/sects>
: 65536
type:
4.2BSD
edlabel/modify>
a
',
starting at block zero
and with a size of 65536 blocks. Note that the usual size of a block is
512 bytes, so this creates a 32 MB partition.
type
of the partition should be
4.2BSD
,
otherwise you won't be able to create a file system on it.
edlabel/modify>
b
b
(swap)
0
(0/00/00)
0
(0/00/00)
unused
start
as
<blkno>
or
<cyls/trks/sects>
: 65536
length
as
<nblks>
or
<cyls/trks/sects>
: 32768
type:
swap
edlabel/modify>
start
such that the swap partition follows immediately after partition
`a
',
i.e. 65536. The length of the swap
partition should be a multiple of the amount of RAM you have in your
system. Here, we've chosen 32768, or 16 MB. The next available block on the
drive is thus 65536 + 32768. We will use this to create partition
`d
'
for our
/usr
file system. (Note that for a busy system, or a system with more
than 8 MB of RAM, you'll be better off with a 32 or 64 MB swap partition.)
edlabel/modify>
d
d
(user)
0
(0/00/00)
0
(0/00/00)
unused
start
as
<blkno>
or
<cyls/trks/sects>
: 98304
length
as
<nblks>
or
<cyls/trks/sects>
: 1540096
type:
4.2BSD
edlabel/modify>
q
edlabel>
/usr
.
Since there are 1638400 sectors on the example disk (did you remember to
note down the number of sectors on your disk during boot?), and partition
d
starts at sector 98304, a simple bit of arithmetic (1638400 - 98304)
gives
d a size of 1540096.
edlabel>
p
type_num: 4
sub_type: 0
type_name: SCSI disk
pack_name: fictitious
bytes/sector: 512
sectors/track: 128
tracks/cylinder: 16
cylinders: 800
sectors/cylinder: 2048
partition start (c/t/s) nblks (c/t/s) type
edlabel>
w
edlabel>
q
ssh:
ssh:
mt -f /dev/nrst0 rewind
ssh:
mt -f /dev/nrst0 fsf 3
ssh:
dd bs=8k if=/dev/nrst0 of=/dev/rsd0b
installboot(8)
command. To do this, issue the following commands:
ssh:
mount /dev/sd0b /mnt
ssh:
installboot /mnt/usr/mdec/bootsd /bootxx /dev/rsd0b
ssh:
umount /dev/sd0b
ssh:
halt
signal
15
ssh:
syncing
disks...
done
unmounting
/
(root_device)...
halted
147-Bug>
reset
Reset
Local
SCSI
Bus
[Y,N]
N?
y
Automatic
reset
of
known
SCSI
Buses
on
RESET
[Y,N]
Y?
Cold/Warm
Reset
flag
[C,W]
=
C?
Execute
Soft
Reset
[Y,N]
N?
y
Installing from NFS
Before you can install from NFS, you must have already configured
your NFS server to support your machine as a bootable client.
Instructions for configuring the server are found in the section
entitled
Getting the NetBSD System onto Useful Media
above.
sboot
into RAM (you will find
sboot
in the
install
directory of the mvme68k distribution).
You can either do that through the console line or through a 2nd serial
connection. For example, an MVME147 connected to a sun4/110 and accessed via
tip(1)
can be loaded as follows:
lo 0
~Ccat sboot
go 4000
147-Bug>
lo 0
~CLocal
command?
cat sboot
!
147-Bug>
g 4000
Effective
address:
00004000
sboot:
serial
line
bootstrap
program
(end
=
6018)
>>>
147-Bug>
prompt type tm 1
You should then login to the machine it is connected to.
Then press
CONTROL-A
to escape to Bug. do
lo 1;x=cat sboot ...
then when that is done you can reconnect
tm 1 and logout.
Then do go 4000
and you've got the
>>>
prompt of
sboot.
>>>
prompt, you can boot the
RAMDISK
kernel from the server:
>>>
b
le0: ethernet address: 8:0:3e:20:cb:87
My ip address is: 192.168.1.4
Server ip address is: 192.168.1.1
4800
Download was a success!
16x-Bug>
nbo
Start @ 0x8000 ...
>> BSD MVME147 netboot (via sboot)
device: le0 attached to 08:00:3e:20:cb:87
boot: client IP address: 192.168.1.4
boot: client name: soapy
root addr=192.168.1.1 path=/export/soapy
578616+422344+55540+[46032+51284]=0x11a6e4
Start @ 0x8000 ...
Copyright (c) 1996, 1997, 1998, 1999, 2000
The NetBSD Foundation, Inc. All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
RAMDISK
kernel, you should see the
welcome screen as shown in the "tape boot" section above.
/
).
Follow the instructions in the previous section entitled
Installing from tape
to do this. (But stop short of the part which describes how to
copy the miniroot from tape.)
ssh:
ifconfig le0 inet 192.168.1.4 up
le0
with that address.
The command:
ssh:
ifconfig ie0 inet 192.168.1.4 up
ie0
with that address.
The next
step is to copy the miniroot from your server. This can be done using
either NFS or remote shell. (In the examples that follow, the server has
IP address 192.168.1.1) You may then need to add a default route if the
server is on a different subnet:
ssh:
route add default 192.168.1.2 1
ssh:
route show
ssh:
mount -r 192.168.1.1:/export/soapy /mnt
ssh:
dd bs=8k if=/mnt/miniroot of=/dev/rsd0b
sh(1)
pipeline syntax. Instead, you first run the reader
in the background with its input set to
/dev/pipe
and then run the other program in the foreground with its output to
/dev/pipe
.
The result looks like this:
ssh:
run -bg dd obs=8k if=/dev/pipe of=/dev/rsd0b
ssh:
run -o /dev/pipe zcat /mnt/install/miniroot.gz
ssh:
run -b dd obs=8k if=/dev/pipe of=/dev/rsd0b
ssh:
run -o /dev/pipe rsh 192.168.1.1 zcat miniroot.gz
Booting the miniroot
Assuming the miniroot is installed on partition
`b
'
of the disk with
SCSI-ID 0, then the 147Bug boot command is:
147-Bug>
bo 0,,b:
16x-Bug>
bo 0,,,b:
b
RAMDISK
kernel booted.
sd0b
.
You will
then be asked for the swap device and file system type. Just press
RETURN
twice to accept the defaults. When asked to enter a terminal
type, either accept the default, or use whatever the TERM environment
variable is set to in the shell of your host system:
boot
device:
sd0
root
device
(default
sd0a):
sd0b
dump
device
(default
sd0b):
(return)
file
system
(default
generic):
(return)
root
on
sd0b
dumps
on
sd0b
mountroot:
trying
ffs...
root
file
system
type:
ffs
init:
copying
out
path
`/sbin/init'
11
erase
^H,
werase
^W,
kill
^U,
intr
^C
Terminal
type?
[vt100]
return
Miniroot install program:
The miniroot's install program is very simple to use. It will guide
you through the entire process, and is well automated. Additional
improvements are planned for future releases.
RAMDISK
kernel.
fstype: 4.2BSD
fsize: 1024
bsize: 4096
cpg: 16
fstype: swap
fsize: 0 (or blank)
bsize: 0 (or blank)
cpg: 0 (or blank)
c
'
is special; it covers then entire
disk and should not be assigned to a file system.
foo
instead of
foo.bar.org
.
If, during the process of configuring
the network interfaces, you make a mistake, you will
be able to re-configure that interface by simply selecting
it for configuration again.
/etc/fstab
.
/
).
/dev
.
/
).
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.
/
)
mounted read-write. When the system
asks you to choose a shell, simply press
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 press
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.
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)
.
/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
/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.
/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"
/etc/hosts
:
ifconfig_de0="inet
myname.my.dom
netmask
255.255.255.0"
/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 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.
Unless you have connected an unusual terminal device as the console
you can just press
RETURN
when it prompts for
Terminal
type?
[...]
useradd(8)
command to add accounts to your system,
do not
edit
/etc/passwd
directly. See
useradd(8)
for more information on how to add a new user to the system.
/usr/X11R6/lib/X11/doc
for information.
/usr/X11R6/bin
to your path in your shell's dot file so that you have access to the X binaries.
/usr/pkgsrc
(though other locations work fine), as with the command:
#
mkdir /usr/pkgsrc; tar -C /usr/pkgsrc -zxpf pkgsrc.tar.gz
README
file in the extraction directory (e.g.
/usr/pkgsrc/README
)
for more information.
/etc/mail/aliases
to forward root mail to the right place (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.
/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
Upgrading a previously-installed NetBSD System
/etc/fstab
,
changing the occurrences of
ufs
to
ffs
and let you edit the resulting file.
/dev
.
/
).
#
/sbin/fsck -pf
#
/sbin/mount -a -t nonfs
/usr
or
/usr/share
on an NFS server, you will want to mount those file systems as well.
To do this, you will need to enable the network:
#
sh /etc/rc.d/network start
/
)
and extract
the
base
binary set:
#
cd /
#
pax -zrvpe -f /path/to/base.tgz
#
cd /usr/mdec
#
cp bootsd /.bootsd
#
./installboot /.bootsd bootxx < root-disk
/dev/rsd0a
.
#
sync
#
cd /
#
pax -zrvpe -f path_to_set
Compatibility Issues With Previous NetBSD Releases
General issues
/etc/rc
modified to use
/etc/rc.d/*
/etc/rc
was a traditional
BSD
style monolithic file.
As of
NetBSD1.5,
each discrete program or substem from
/etc/rc
and
/etc/netstart
has been moved into separate scripts in
/etc/rc.d/
.
/etc/rc
uses
rcorder(8)
to build a dependency list of the files in
/etc/rc.d
and then executes each script in turn with an argument of
`start'.
Many
rc.d
scripts won't start unless the appropriate
rc.conf(5)
entry in
/etc/rc.conf
is set to
`YES.'
/etc/rc.shutdown
uses
rcorder(8)
to build a dependency list of the files in
/etc/rc.d
that have a
``KEYWORD: shutdown''
line, reverses the resulting list, and then executes each script in turn
with an argument of
`stop'.
The following scripts support a specific shutdown method:
cron
,
inetd
,
local
,
and
xdm
.
/etc/rc.d
as necessary.
Refer to the other scripts in that directory and
rc(8)
for more information on implementing
rc.d
scripts.
Issues affecting an upgrading from NetBSD 1.4 or later
named(8)
leaks version information
named(8)
where the version number of the server could be determined by remote clients.
This feature has not been disabled in
NetBSD1.5,
because there is a
named.conf(5)
option to change the version string:
option {
version "newstring";
};
sysctl(8)
pathname changed
sysctl(8)
is moved from
/usr/sbin/sysctl
to
/sbin/sysctl
.
If you have hardcoded references to the full pathname
(in shell scripts, for example)
please be sure to update those.
sendmail(8)
configuration file pathname changed
sendmail(8)
upgrade from 8.9.x to 8.10.x,
/etc/sendmail.cf
is moved to
/etc/mail/sendmail.cf
.
Also, the default
sendmail.cf(5)
refers different pathnames than before.
For example,
/etc/aliases
is now located at
/etc/mail/aliases
,
/etc/sendmail.cw
is now called
/etc/mail/local-host-names
,
and so forth.
If you have customized
sendmail.cf(5)
and friends, you will need to move the files to the new locations.
See
/usr/share/sendmail/README
for more information.
Using online NetBSD documentation
name(section)
'.
Some examples of this are
intro(1)
,
man(1)
,
apropros(1)
,
passwd(1)
,
and
passwd(5)
.
#
man passwd
passwd(1)
.
To view the documentation for
passwd(5)
,
enter
#
man 5 passwd
Administrivia
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:
[email protected].
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
S�ren J�rvang
Scott Kaplan
Noah M. Keiserman
Harald Koerfgen
John Kohl
Chris Legrow
Ted Lemon
Norman R. McBride
Neil J. McRae
Perry E. Metzger
Toru Nishimura
Herb Peyerl
Mike Price
Dave Rand
Michael Richardson
Heiko W. Rupp
Brad Salai
Chuck Silvers
Thor Lancelot Simon
Bill Sommerfeld
Paul Southworth
Eric and Rosemary Spahr
Ted Spradley
Kimmo Suominen
Jason R. Thorpe
Steve Wadlow
Krister Walfridsson
Jim Wise
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
Distributed Processing Technology
Easynet, UK
Free Hardware Foundation
Innovation Development Enterprises of America
Internet Software Consortium
MS Macro System GmbH, Germany
Numerical Aerospace Simulation Facility, NASA Ames Research Center
Piermont Information Systems Inc.
Salient Systems Inc.
VMC Harald Frank, Germany
Warped Communications, Inc.
Whitecross Database Systems Ltd.
We are...
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.
This product includes software developed by The NetBSD Foundation, Inc.
This product includes software developed by the NetBSD Foundation, Inc.
and its contributors.
This product includes software developed by the Computer
Systems Engineering Group at Lawrence Berkeley Laboratory.
This product includes software developed by Adam Glass
and Charles Hannum.
This product includes software developed by Adam Glass
and Charles M. Hannum.
This product includes software developed by Adam Glass.
This product includes software developed by Alistair G. Crooks.
This product includes software developed by Amancio Hasty and
Roger Hardiman.
This product includes software developed by Berkeley Software
Design, Inc.
This product includes software developed by Bill Paul.
This product includes software developed by Charles D. Cranor
and Washington University.
This product includes software 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 Gardner Buchanan.
This product includes software developed by Gordon Ross.
This product includes software developed by Gordon W. Ross
and Leo Weppelman.
This product includes software developed by Gordon W. Ross.
This product includes software developed by Hauke Fath.
This product includes software developed by HAYAKAWA Koichi.
This product includes software developed by
Hellmuth Michaelis and Joerg Wunsch.
This product includes software developed by Herb Peyerl.
This product includes software developed by Holger Veit and Brian Moore
for use with "386BSD" and similar operating systems.
This product includes software developed by Hubert Feyrer for
the NetBSD Project.
This product includes software developed by Iain Hibbert.
This product includes software developed by Ian W. Dall.
This product includes software developed by Ignatios Souvatzis
for the NetBSD Project.
This product includes software developed by Jason R. Thorpe
for And Communications, http://www.and.com/.
This product includes software developed by Joachim Koenig-Baltes.
This product includes software 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 Manuel Bouyer.
This product includes software developed by Marc Horowitz.
This product includes software developed by Mark Brinicombe.
This product includes software developed by Mark Tinguely and Jim Lowe.
This product includes software developed by Markus Wild.
This product includes software developed by Martin Husemann
and Wolfgang Solfrank.
This product includes software developed by Mats O Jansson
and Charles D. Cranor.
This product includes software developed by Mats O Jansson.
This product includes software developed by Matthias Pfaller.
This product includes software developed by Michael L. Hitch.
This product includes software developed by Niels Provos.
This product includes software developed by Paul Kranenburg.
This product includes software developed by Paul Mackerras.
This product includes software developed by Peter Galbavy.
This product includes software developed by Philip A. Nelson.
This product includes software developed by Rodney W. Grimes.
This product includes software developed by Roland C. Dowdeswell.
This product includes software developed by Rolf Grossmann.
This product includes software developed by Scott Bartram.
This product includes software developed by SigmaSoft, Th. Lockert.
This product includes software developed by Tatoku Ogaito
for the NetBSD Project.
This product includes software developed by Terrence R. Lambert.
This product includes software developed by Theo de Raadt
and John Brezak.
This product includes software developed by Theo de Raadt.
This product includes software developed by Tohru Nishimura
for the NetBSD Project.
This product includes software developed by TooLs GmbH.
This product includes software developed by Winning Strategies, Inc.
This product includes software developed by Zembu Labs, Inc.
This product includes software developed by the Center for
Software Science at the University of Utah.
This product includes software developed by the Computer
Systems Laboratory 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 Eric Young ([email protected]).
This product includes software developed by the OpenSSL Project
for use in the OpenSSL Toolkit (http://www.openssl.org/).
This product includes software developed by the University of Oregon.
This product includes software developed by the University of Southern
California and/or Information Sciences Institute.
This product includes software developed by Internet Initiative Japan Inc.
This product includes software developed by David Jones.
This product includes software developed by Steve C. Woodford.