INSTALL.ext,
where
ext
is one of
.ps, .html, .more,
or .txt.
.ps.html.moremore(1)
and
less(1)
pager utility programs. This is the format in which the on-line
man
pages are generally presented.
.txtYou are reading the HTML version.
NetBSD is a completely integrated system. In addition to its highly portable, high performance kernel, NetBSD features a complete set of user utilities, compilers for several languages, The X Window System, and numerous other tools, all accompanied by full source code.
NetBSD is a creation of the members of the Internet community. Without the unique cooperation and coordination the net makes possible, it's likely that NetBSD wouldn't exist.
NetBSD 1.4.2 is an upgrade of NetBSD 1.4.1, NetBSD 1.4 and earlier releases of NetBSD such as versions 1.3.3, 1.2 etc.
The intermediate development versions of code available on the main trunk in our CVS repository (also known as ``NetBSD-current'') from after the point where the release cycle for 1.4 was started are designated by version identifiers such as 1.4A, 1.4B, 1.4P etc. These identifiers do not designate releases, but indicate major changes in internal kernel APIs. Note that the kernel from NetBSD 1.4.2 can not be used to upgrade a system running one of those intermediate development versions. Trying to use the NetBSD1.4.2 kernel on such a system will in all probability result in problems.
Please also note that it is not possible to do a direct ``version'' comparison between any of the intermediate development versions mentioned above and 1.4.2 to determine if a given feature is present or absent in 1.4.2. The development of 1.4, 1.4.1 and 1.4.2 is done on a separate branch in the CVS repository which was created when the release cylcle for 1.4 was started, and during the release cycles for all these versions selective fixes (with minor impact on the stability of the code on the release branch) have been imported from the main development trunk. So, there are features in 1.4.2 which were not in e.g. 1.4H, but the reverse is also true.
ti(4).
rl(4).
dpt(4).
ioat(4).
mktemp(1).
amd(8)
has been updated to fix a security problem.
In addition, many, many bugs have been fixed -- more than 100 problems reported through our problem tracking system have been fixed, and many other non-reported problems have also been found and fixed. See the CHANGES-1.4.2 file for the complete list.
ipf(8)
caused a change of the kernel API. Thus, if you are using
ipf(8)
you need to upgrade both the kernel and the user-land utilities to
control that feature in order for it to work.
It is impossible to completely summarize the nearly two years of development that went into the NetBSD1.4 release. Some highlights include:
ftp(1)
client has been improved even further. See the man page for details.
wscons(4),
has been integrated into many ports.
usb(4)
for an overview.
nsswitch.conf(5)
functionality to the system to specify the search order for system databases.
syslogd(8)
now supports listening on multiple sockets, to make the
chrooting of servers easier.
As has been noted, there have also been innumerable bug fixes.
Kernel interfaces have continued to be refined, and more subsystems and device drivers are shared among the different ports. You can look for this trend to continue.
This is the fifth public release of NetBSD for the mvme68k series of boards, and the first to support MVME167.
The NetBSD Foundation will help improve the quality of NetBSD by:
We intend to begin narrowing the time delay between releases. Our ambition is to provide a full release every six to eight months.
We hope to support even more hardware in the future, and we have a rather large number of other ideas about what can be done to improve NetBSD.
We intend to continue our current practice of making the NetBSD-current development source available on a daily basis. In addition, Anonymous CVS access to the NetBSD source tree has been added since NetBSD 1.4.1; see http://www.netbsd.org/Changes/#anoncvs-available We have also added a browsable CVS repository on the web at http://cvsweb.netbsd.org/cgi-bin/cvsweb.cgi/
We intend to integrate free, positive changes from whatever sources submit them, providing that they are well thought-out and increase the usability of the system.
Above all, we hope to create a stable and accessible system, and to be
responsive to the needs and desires of
NetBSD
users, because it is for
and because of them that
NetBSD
exists.
.../NetBSD-1.4.2/
BUGSCHANGESLAST_MINUTEMIRRORSREADME.filesTODOpatches/source/In addition to the files and directories listed above, there is one directory per architecture, for each of the architectures for which NetBSD1.4.2 has a binary distribution. There are also 'README.export-control' files sprinkled liberally throughout the distribution tree, which point out that there are some portions of the distribution (i.e. the `domestic' portion) that may be subject to export regulations of the United States. It is your responsibility to determine whether or not it is legal for you to export these portions and to act accordingly. The NetBSD project maintains a web page at
http://www.NetBSD.ORG/Misc/crypto-export.html
which should contain up-to-date information on this issue.
The source distribution sets can be found in subdirectories of the "source" subdirectory of the distribution tree. They contain the complete sources to the system. The source distribution sets are as follows:
Most of the above source sets are located in the
source/sets
subdirectory of the distribution tree. The secrsrc.tgz set is
contained in the
source/security
subdirectory. This set, which may only be
available to users in the United States and Canada, contains the
sources normally found in
/usr/src/domestic
- primarily Kerberos and
other cryptographic security related software. (Remember, because of
United States law, it may not be legal to distribute this set to
locations outside of the United States and Canada. Again, see
http://www.NetBSD.ORG/Misc/crypto-export.html
for updated information on this issue.)
The source sets are distributed as compressed tar files. They may be
unpacked into
/usr/src
with the command:
cat set_name.tgz | gunzip | (cd /; tar xpf - )
The sets/Split/
and security/Split/
subdirectories contain split
versions of the source sets for those users who need to load the
source sets from floppy or otherwise need a split distribution. The
split sets are are named "set_name.xx" where "set_name" is the
distribution set name, and "xx" is the sequence number of the file,
starting with "aa" for the first file in the distribution set, then
"ab" for the next, and so on. All of these files except the last one
of each set should be exactly 240,640 bytes long. (The last file is
just long enough to contain the remainder of the data for that
distribution set.)
The split distributions may be reassembled and extracted with
cat as follows:
cat set_name.?? | gunzip | (cd /; tar xpf - )
In each of the source distribution set directories, there is a file
named
CKSUMS
which contains the checksums of the files in that
directory, as generated by the
cksum(1)
utility. You can use cksum to
check the integrity of the archives, if you suspect that one of the
files is corrupt and have access to a cksum binary. Checksums based on
other algorithms may also be present - see the
release(7)
man page for details.
mvme68k
subdirectory of the distribution:
.../NetBSD-1.4.2/mvme68k/
INSTALL.htmlINSTALL.psINSTALL.txtINSTALL.more.more file contains underlined text using the
more(1)
conventions for indicating italic and bold display.
binary/sets/security/installation/miniroot/netboot/tapeimage/The NetBSD/mvme68k install distribution contains files that can be used to install NetBSD onto completely "bare" MVME147 and MVME167 boards. The files in the "mvme68k/installation/*" directories are described below.
miniroot.gznetbsd-rd.gzstbootbootstsbootnetbootThese files can be used to make a boot tape suitable for installing NetBSD/mvme68k. These files can also be used to configure an NFS server to support installation "over the network". See the section Getting the NetBSD System onto Useful Media for instructions on either method.
mvme68k/binary/sets
subdirectory
of the
NetBSD1.4.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. (If you are upgrading,
it's recommended that you get a copy of this set and
carefully
upgrade your configuration files by hand.)
/netbsd.
You must
install this distribution set.
/usr/share.
groff(1),
all related programs, and their manual pages.
The mvme68k security distribution set is named
secr and can be found in the
mvme68k/binary/security
subdirectory of the
NetBSD1.4.2
distribution tree. It contains security-related binaries
which depend on cryptographic source code. You do not need this
distribution set to use encrypted passwords in your password file; the
base
distribution includes a crypt library which can perform
only the one-way encryption function. The security distribution
includes a version of the Kerberos IV network security system, and
a Kerberized version of
telnet(1)
program. The secr
distribution set can be found only on those sites which carry the complete
NetBSD
distribution and which can legally obtain it. Because
of United States law, it may not be legal to distribute this set
to locations outside of the United States and Canada. See
http://www.NetBSD.ORG/Misc/crypto-export.html
for updated information on this issue.
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.
base.tgz.
The instructions given for extracting the source sets work equally well for the binary sets, but it is worth noting that if you use that method, the files are /-relative and therefore are extracted below the current directory. That is, if you want to extract the binaries into your system, i.e. replace the system binaries with them, you have to run the tar xfp command from /.
All BSDSUM
files are historic
BSD checksums for the various files
in that directory, in the format produced by the command:
cksum -o 1 file
All CKSUM files are
POSIX
checksums for the various files in that
directory, in the format produced by the command:
cksum file.
All MD5 files are
MD5
digests for the various files in that
directory, in the format produced by the command:
cksum -m file.
All SYSVSUM
files are historic AT&T System V
UNIX
checksums for the various files in that directory, in the format produced by
the command:
cksum -o -2 file.
The MD5 digest is the safest checksum, followed by the POSIX
checksum. The other two checksums are provided only to ensure
that the widest possible range of system can check the integrity
of the release files.
NetBSD/mvme68k 1.4.2 runs on Motorola
MVME147 and MVME167 Single Board Computers.
The minimal configuration requires 4M of RAM and ~100MB of disk space.
To install the entire system requires much more disk space (approx.
200MB 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 8MB of RAM, or 16 MB
when running the X Window System.
Here is a table of recommended HD partition sizes for a full install:
Note that the 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 (> 6Mb).
The following
VME147 hardware is supported:
The following
VME167 hardware is supported:
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:
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:
The boot tape is created as follows:
The installation set tape is created as follows:
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 entitiled
"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 ".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.
The MVME167 boot ROM has code builtin to boot over ethernet from a
TFTP server. You should configure it to download the same "netboot"
program as is used for MVME147.
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 /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.
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 6Mb 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 following instructions should make your machine "NetBSD Ready".
Power-up your MVME147 board. You should have the
bug prompt:
COLD Start
Onboard RAM start = $00000000, stop = $007FFFFF
147-Bug>
MVME167 Debugger/Diagnostics Release Version 2.3 - 02/25/94
COLD Start
Local Memory Found =02000000 (&33554432)
MPU Clock Speed =33Mhz
167-Bug>
Note that
NetBSD
bases its year at 1968, and adds the year offset in
the MVME1x7's real-time clock to get the current year. So the '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,
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 !
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 MVME167.
On the MVME147, enter the last five digits of the address
using the 'lsad' command. On the MVME167, you should use the 'cnfg' command.
To install successfully to a local SCSI disk, you need to ensure that
1x7Bug is aware of what targets are connected to the SCSI bus. This
can be done by issueing the following command:
At this point, 1x7Bug 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. 167Bug 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 'sd0' and 'rst0'
respectively. You may wish to note these down; you'll be using them
a lot. :-)
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; here it's
304605. You will need this number when you come to create a disklabel
for that drive.
Booting from: VME147, Controller 5, Device 0
Loading: Operating System
Volume: NBSD
IPL loaded at: $003F0000
>> BSD MVME147 tapeboot [$Revision: 1.5.2.1 $]
578616+422344+55540+[46032+51284]=0x11a6e4
Start @ 0x8000 ...
Copyright (c) 1996, 1997 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.3 (RAMDISK) #1: Sun Dec 21 16:19:04 GMT 1997
steve@soapy.mctavish.demon.co.uk:/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 filesystem. This will usually be
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 filesystem 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 'a', starting at block zero
and with a size of 38000 blocks. Note that the usual size of a block is
512 bytes, so this creates a 19Mb partition.
The 'type' of the partition should be "4.2BSD", otherwise you won't
be able to create a filesystem on it.
Next, create a swap partition (b). Note that the minimum size of this
swap partition should be 8Mb, otherwise you won't be able to use a
miniroot to complete the
NetBSD
installation!
Here, we specify a value for 'start' such that the swap partition follows
immediately after partition 'a', i.e. 38000. The length of the swap
partition should be a multiple of the amount of RAM you have in your
system. Here, I've chosen 32768, or 16Mb. The next available block on the
drive is thus 38000 + 32768. We will use this to create partition 'd' for
our /usr filesystem. (Note that for a busy system, or a system with more
than 8Mb of RAM, you'll be better off with a 32 or 64Mb swap partition.)
As you can see, I've chosen to assign the remainder of the disk to
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) 38000 (120/05/25)* 4.2BSD
b (swap) 38000 (120/05/25)* 32768 (104/00/08)* swap
c (disk) 0 (0/00/00) 304605 (967/00/00) unused
d (user) 70768 (224/05/33)* 233837 (742/03/02)* 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 MVME167 board is 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 "sboot" into RAM
(you will find
sboot
in the
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 ">>> " prompt, you can boot the RAMDISK kernel
from the server:
See below for the next step in booting MVME147.
The MVME167 is 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 MVME167, all you need
to type is:
For both boards, the boot messages are very similar:
NetBSD 1.3 (RAMDISK) #1: Sun Dec 21 16:19:04 GMT 1997
steve@soapy.mctavish.demon.co.uk:/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 RAMDISK kernel, you should see the
welcome screen as shown in the "tape boot" section above.
You now need to create a disklabel with partition information on the
SCSI disk on which you intend to create your root filesystem. 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.)
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 'le0' with that address.
The command:
will bring up the MVME167 network interface '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:
You can look at the route table using:
Now mount the NFS filesystem 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 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:
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 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 RAMDISK kernel booted.
You will then be prompted to enter the root device. Since the miniroot
was booted from the swap partition, you should enter 'sd0b'. You will
then be asked for the swap device and filesystem 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:
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 filesystem parameters.
If you're unsure what the these values should be, use the
following defaults:
If the partition will be a swap partition, use the following:
Note that partition 'c' is special; it covers then entire
disk and should not be assigned to a filesystem.
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 propperly
configured state, with the most important ones described below.
If you haven't done any configuration of
Other values that need to be set in
Other files in
After reboot, you can log in as
Use the
If you have installed the X window system, look at the files in
Don't forget to add
There is a lot of software freely available for Unix-based systems,
almost all of which can run on
NetBSD.
Modifications are usually needed to
when transferring programs between different Unix-like systems, so
the
NetBSD
packages collection incorporates any such
changes necessary to make that software run on
NetBSD,
and makes
the installation (and deinstallation) of the software packages
easy. There's also the option of building a package from source, in
case there's no precompiled binary available.
Precompiled binaries can be found at
ftp://ftp.netbsd.org/pub/NetBSD/packages/
Package sources for compiling packages can be obtained by
retrieving the file
ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-current/tar_files/pkgsrc.tar.gz
and extracting it into
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:
(root-disk might be, e.g., /dev/rsd0a)
Documentation is available if you first install the manual
distribution set. Traditionally, the
``man pages''
(documentation) are denoted by
``
The section numbers group the topics into several categories, but three
are of primary interest: user commands are in section 1, file formats
are in section 5, and administrative information is in section 8.
The man
command is used to view the documentation on a topic, and is
started by entering
man[ section]
topic.
The brackets
[]
around the
section should not be entered, but rather indicate that the section is
optional. If you don't ask for a particular section, the topic with the
lowest numbered section name will be displayed. For instance, after
logging in, enter
If you are unsure of what man page you are looking for, enter
apropos subject-word
where
subject-word
is your topic of interest; a list of possibly
related man pages will be displayed.
There are various mailing lists set up to deal with comments and
questions about this release. Please send comments to:
netbsd-comments@NetBSD.ORG.
To report bugs, use the
Use of
There are also port-specific mailing lists, to discuss aspects of
each port of
NetBSD.
Use majordomo to find their addresses. If
you're interested in doing a serious amount of work on a specific
port, you probably should contact the "owner" of that port (listed
below).
If you'd like to help with this effort, and have an idea as to how
you could be useful, send us mail or subscribe to:
netbsd-help@NetBSD.ORG.
As a favor, please avoid mailing huge documents or files to these
mailing lists. Instead, put the material you would have sent up
for FTP somewhere, then mail the appropriate list about it, or, if
you'd rather not do that, mail the list saying you'll send the data
to those who want it.
for their ongoing work on BSD systems, support, and encouragement.
for answering lots of questions, fixing bugs, and doing the various work
they've done.
(in alphabetical order)
partition: advise needed
root (/) 20M 12M
user (/usr) 100M 80M
swap (2 or 3 * RAM) 8M
Anything else is up to you!
Getting the NetBSD System on to Useful Media
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.
.../NetBSD-1.4.2/mvme68k/installation
.../NetBSD-1.4.2/mvme68k/binary
Creating boot/install tapes:
Installing from tape is the simplest method of all. This method uses two
tapes, one containing a bootable ramdisk and miniroot, the other containing
the installation sets.
cd .../NetBSD-1.4.2/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
cd .../NetBSD-1.4.2/mvme68k/binary/sets
set T = /dev/nrst0
mt -f $T rewind
foreach f (base etc comp games man misc text)
gzip -d < $f.tgz | dd of=$T bs=8k
end
mt -f $T rewind
Boot/Install from NFS server:
If your machine has a disk and network connection, but no tape drive,
it may be convenient for you to install
NetBSD
over the network. This
involves temporarily booting your machine over NFS, just long enough
so you can initialize its disk. This method requires that you have
access to an NFS server on your network so you can configure it to
support diskless boot for your machine. Configuring the NFS server
is normally a task for a system administrator, and is not trivial.
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).
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.
IP Address: ftp.NetBSD.ORG
Login: anonymous
Password: your e-mail address
Server path: /pub/NetBSD/NetBSD-1.4.2/mvme68k/binary
Preparing your System for NetBSD Installation
Or, if you have an MVME167 board:
Make sure the RAM size looks ok (if you've got an 8Mb MVME147 or a
32Mb MVME167 you should
have the same value as I do). Also make sure the clock is ticking:
1x7-Bug>time
Sunday 12/21/31 16:25:14
1x7-Bug>time
Sunday 12/21/31 16:25:15
1x7-Bug>
1x7-Bug> iot;t
Installing the NetBSD System
Installing from tape:
Create the NetBSD/mvme68k _VER boot tape as described in the section
entitled "Preparing a boot tape". Then, with the tape in the drive,
type the following at the 1x7Bug prompt:
147-Bug> bo 5
167-Bug> bo 0,50
sd0 at scsibus0 targ 0 lun 0: <CDC, 94161-9, 2506> SCSI1 0/direct fixed
sd0: 148MB, 967 cyl, 9 head, 35 sec, 512 bytes/sect x 304605 sectors
RAM address from VMEbus = $00000000
Welcome to the NetBSD/mvme68k RAMDISK root!
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:
sd0asd0bsd0c/usr on a different partition
than / (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 /,
/usr and swap
partitions.
sd0d, but if you
have a large disk drive, you might want to create several other partitions
for filesystems 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>: 38000
type: 4.2BSD
edlabel/modify>
edlabel/modify> b
b (swap) 0 (0/00/00) 0 (0/00/00) unused
start as <blkno> or <cyls/trks/sects>: 38000
length as <nblks> or <cyls/trks/sects>: 32768
type: swap
edlabel/modify>
edlabel/modify> d
d (user) 0 (0/00/00) 0 (0/00/00) unused
start as <blkno> or <cyls/trks/sects>: 70768
length as <nblks> or <cyls/trks/sects>: 233837
type: 4.2BSD
edlabel/modify> q
edlabel>
/usr.
Since there are 304605 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 70768, a simple bit of arithmetic (304605 - 70768)
gives
d a size of 233837.
edlabel> p
type_num: 4
sub_type: 0
type_name: SCSI disk
pack_name: fictitious
bytes/sector: 512
sectors/track: 35
tracks/cylinder: 9
cylinders: 967
sectors/cylinder: 315
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 /mnt (/dev/sd1b)...
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.
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 hit "^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.
>>> 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!
167-Bug> nbo
Start @ 0x8000 ...
>> BSD MVME147 netboot (via sboot) [$Revision: 1.5.2.1 $]
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 The NetBSD Foundation, Inc. All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
ssh: ifconfig le0 inet 192.168.1.4 up
ssh: ifconfig ie0 inet 192.168.1.4 up
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
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:
167-Bug> bo 0,,,b:
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.
fstype: 4.2BSD
fsize: 1024
bsize: 4096
cpg: 16
fstype: swap
fsize: 0 (or blank)
bsize: 0 (or blank)
cpg: 0 (or blank)
Post installation steps
/etc/rc.conf
/etc/rc.conf,
the system will drop you into single user mode on first reboot with the
message
/etc/rc.conf is not configured. Multiuser boot aborted.
and with the root filesystem mounted read-write. When the system
asks you to choose a shell, simply hit return to get to a
prompt. If you are asked for a terminal type, respond with
vt220
(or whatever is appropriate for your terminal type)
and hit return. At this point, you need to configure at least
one file in the
/etc directory. Change to the
/etc
directory and take a look at the
/etc/rc.conf
file. Modify it to your tastes, making sure that you set
rc_configured=YES
so that your changes will be enabled and a multi-user boot can
proceed. If your
/usr directory is on a separate partition
and you do not know how to use 'ed' or 'ex', you will have to mount your
/usr
partition to gain access to 'vi'. Do the following:
mount /usr
export TERM=vt220
If you have
/var
on a seperate partition, you need to repeat
that step for it. After that, you can edit
/etc/rc.conf
with
vi(1).
When you have finished, type
exit
at the prompt to
leave the single-user shell and continue with the multi-user boot.
/etc/rc.conf
for a networked environment are
hostname and possibly
defaultroute,
furthermore add an
ifconfig_int
for your interface
<int>,
along the lines of
ifconfig_de0="inet 123.45.67.89 netmask 255.255.255.0"
or, if you have
myname.my.dom in /etc/hosts:
ifconfig_de0="inet myname.my.dom netmask 255.255.255.0"
To enable proper hostname resolution, you will also want to add an
/etc/resolv.conf
file or (if you are feeling a little more adventurous) run
named(8).
See
resolv.conf(5)
or
named(8)
for more information.
/etc
that are new to NetBSD 1.4 and may require modification or
setting up include
/etc/mailer.conf,
/etc/nsswitch.conf
and
/etc/wscons.conf.
root
at the login prompt. There
is no initial password, but if you're using the machine in a
networked environment, you should create an account for yourself
(see below) and protect it and the "root" account with good
passwords.
vipw(8)
command to add accounts to your system,
do not edit /etc/passwd
directly. See
adduser(8)
for more information on the process of how to add a new user to the system.
/usr/X11R6/lib/X11/doc
for information.
/usr/X11R6/bin
to your path in your shell's dot file so that you have access to the X binaries.
/usr/pkgsrc.
See
/usr/pkgsrc/README
then for more information.
/etc/localtime
symlink to the appropriate file under
/usr/share/zoneinfo.
/etc/aliases
to forward root mail to the right place (run
newaliases(1)
afterwards.)
/etc/sendmail.cf
file will almost definitely need to be adjusted;
files aiding in this can be found in
/usr/share/sendmail.
See the
README
file there for more information.
/etc/rc.local
to run any local daemons you use.
/etc
files are documented in section 5 of the manual; so just invoking
man filename
is likely to give you more information on these files.
Upgrading a previously-installed NetBSD System
/sbin/fsck -pf
/sbin/mount -a -t nonfs
sh /etc/netstart
update(8)
daemon, to ensure that new programs are actually stored on disk.
update
cd /
pax -zrvpe -f /path/to/base.tgz
cd /sbin
rm -f mountd rtquery quotacheck dumpfs dumplfs
cd /usr/mdec
cp bootsd /.bootsd
./installboot /.bootsd bootxx < root-disk
sync
cd /
pax -zrvpe -f path_to_set
Compatibility Issues With Previous NetBSD Releases
Users upgrading from previous versions of
NetBSD
may wish to bear the
following problems and compatibility issues in mind when upgrading to
NetBSD1.4.2
/usr/include/machine
directory changed to a symbolic link in NetBSD 1.4.
# rm -r /usr/include/machine
to remove the old directory and it contents and reinstall the
comp
set.
Using online NetBSD documentation
name(section)''.
Some examples of this are
intro(1),
man(1),
apropros(1),
passwd(1),
and
passwd(5).
man passwd
to read the documentation for
passwd(1).
To view the documentation for
passwd(5)m
enter
man 5 passwd
instead.
Administrivia
If you've got something to say, do so! We'd like your input.
There are various mailing lists available via the mailing list
server at
majordomo@NetBSD.ORG.
To get help on using the mailing
list server, send mail to that address with an empty body, and it will
reply with instructions.
send-pr(1)
command shipped with
NetBSD,
and fill in as much information about the problem as you can. Good
bug reports include lots of details. Additionally, bug reports can
be sent by mail to:
netbsd-bugs@NetBSD.ORG.
send-pr(1)
is encouraged, however, because bugs reported with it
are entered into the
NetBSD
bugs database, and thus can't slip through
the cracks.
Thanks go to
Keith Bostic
Ralph Campbell
Mike Karels
Marshall Kirk McKusick
Mike Hibler
Rick Macklem
Jan-Simon Pendry
Chris Torek
Steve Allen
Jason Birnschein
Mason Loring Bliss
Jason Brazile
Mark Brinicombe
David Brownlee
Simon Burge
Dave Burgess
Ralph Campbell
Brian Carlstrom
James Chacon
Bill Coldwell
Charles Conn
Tom Coulter
Charles D. Cranor
Christopher G. Demetriou
Scott Ellis
Hubert Feyrer
Castor Fu
Greg Gingerich
William Gnadt
Michael Graff
Guenther Grau
Ross Harvey
Charles M. Hannum
Michael L. Hitch
Kenneth Alan Hornstein
Jordan K. Hubbard
Soren Jorvang
Scott Kaplan
Noah M. Keiserman
John Kohl
Chris Legrow
Ted Lemon
Neil J. McRae
Perry E. Metzger
Herb Peyerl
Mike Price
Dave Rand
Michael Richardson
Heiko W. Rupp
Brad Salai
Chuck Silvers
Thor Lancelot Simon
Bill Sommerfeld
Paul Southworth
Ted Spradley
Kimmo Suominen
Jason R. Thorpe
Steve Wadlow
Krister Walfridsson
Jim Wise
Christos Zoulas
(If you're not on that list and should be, tell us! We probably were
not able to get in touch with you, to verify that you wanted to be
listed.)
AboveNet Communications, Inc.
Advanced System Products, Inc.
Avalon Computer Systems
Bay Area Internet Solutions
Brains Corporation, Japan
Canada Connect Corporation
Co-operative Research Centre for Enterprise Distributed Systems Technology
Demon Internet, UK
Digital Equipment Corporation
Easynet, UK
Free Hardware Foundation
Innovation Development Enterprises of America
Internet Software Consortium
MS Macro System GmbH, Germany
Numerical Aerospace Simulation Facility, NASA Ames Research Center
Piermont Information Systems Inc.
VMC Harald Frank, Germany
Warped Communications, Inc.
We are...
| The NetBSD core group: | ||||||||
| Alistair Crooks | agc@NetBSD.ORG | |||||||
| Jun-ichiro itojun Hagino | itojun@NetBSD.ORG | |||||||
| Frank van der Linden | fvdl@NetBSD.ORG | |||||||
| Luke Mewburn | lukem@NetBSD.ORG | |||||||
| Christos Zoulas | christos@NetBSD.ORG | |||||||
|
| ||||||||
| The portmasters (and their ports): | ||||||||
| Mark Brinicombe | mark@NetBSD.ORG | arm32 | ||||||
| Jeremy Cooper | jeremy@NetBSD.ORG | sun3x | ||||||
| Ross Harvey | ross@NetBSD.ORG | alpha | ||||||
| Ignatios Souvatzis | is@NetBSD.ORG | amiga | ||||||
| Jun-ichiro itojun Hagino | itojun@NetBSD.ORG | sh3 | ||||||
| Eduardo Horvath | eeh@NetBSD.ORG | sparc64 | ||||||
| Paul Kranenburg | pk@NetBSD.ORG | sparc | ||||||
| Anders Magnusson | ragge@NetBSD.ORG | vax | ||||||
| Tsubai Masanari | tsubai@NetBSD.ORG | macppc | ||||||
| Tsubai Masanari | tsubai@NetBSD.ORG | newsmips | ||||||
| Minoura Makoto | minoura@NetBSD.ORG | x68k | ||||||
| Phil Nelson | phil@NetBSD.ORG | pc532 | ||||||
| Scott Reynolds | scottr@NetBSD.ORG | mac68k | ||||||
| Darrin Jewell | dbj@NetBSD.ORG | next68k | ||||||
| Kazuki Sakamoto | sakamoto@NetBSD.ORG | bebox | ||||||
| Wolfgang Solfrank | ws@NetBSD.ORG | ofppc | ||||||
| Jonathan Stone | jonathan@NetBSD.ORG | pmax | ||||||
| Shin Takemura | takemura@NetBSD.ORG | hpcmips | ||||||
| Jason Thorpe | thorpej@NetBSD.ORG | hp300 | ||||||
| Frank van der Linden | fvdl@NetBSD.ORG | i386 | ||||||
| Leo Weppelman | leo@NetBSD.ORG | atari | ||||||
| Nathan Williams | nathanw@NetBSD.ORG | sun3 | ||||||
| Steve Woodford | scw@NetBSD.ORG | mvme68k | ||||||
|
| ||||||||
| The NetBSD 1.4.2 Release Engineering team: | ||||||||
| Chris G. Demetriou | cgd@NetBSD.ORG | |||||||
| Havard Eidnes | he@NetBSD.ORG | |||||||
| Ted Lemon | mellon@NetBSD.ORG | |||||||
| Perry Metzger | perry@NetBSD.ORG | |||||||
| Curt Sampson | cjs@NetBSD.ORG | |||||||
|
| ||||||||
| Developers and other contributors: | ||||||||
| Steve Allen | wormey@NetBSD.ORG | |||||||
| Julian Assange | proff@NetBSD.ORG | |||||||
| Lennart Augustsson | augustss@NetBSD.ORG | |||||||
| Christoph Badura | bad@NetBSD.ORG | |||||||
| Robert V. Baron | rvb@NetBSD.ORG | |||||||
| Erik Berls | cyber@NetBSD.ORG | |||||||
| John Birrell | jb@NetBSD.ORG | |||||||
| Mason Loring Bliss | mason@NetBSD.ORG | |||||||
| Manuel Bouyer | bouyer@NetBSD.ORG | |||||||
| John Brezak | brezak@NetBSD.ORG | |||||||
| Allen Briggs | briggs@NetBSD.ORG | |||||||
| Aaron Brown | abrown@NetBSD.ORG | |||||||
| David Brownlee | abs@NetBSD.ORG | |||||||
| Frederick Bruckman | fredb@NetBSD.ORG | |||||||
| Jon Buller | jonb@NetBSD.ORG | |||||||
| Simon Burge | simonb@NetBSD.ORG | |||||||
| Dave Burgess | burgess@cynjut.infonet.net | |||||||
| Robert Byrnes | byrnes@NetBSD.org | |||||||
| D'Arcy J.M. Cain | darcy@NetBSD.ORG | |||||||
| Dave Carrel | carrel@NetBSD.ORG | |||||||
| Bill Coldwell | billc@NetBSD.ORG | |||||||
| Julian Coleman | jdc@NetBSD.ORG | |||||||
| Chuck Cranor | chuck@NetBSD.ORG | |||||||
| Aidan Cully | aidan@NetBSD.ORG | |||||||
| Johan Danielsson | joda@NetBSD.ORG | |||||||
| Matt DeBergalis | deberg@NetBSD.ORG | |||||||
| Rob Deker | deker@NetBSD.ORG | |||||||
| Chris G. Demetriou | cgd@NetBSD.ORG | |||||||
| Jaromir Dolecek | jdolecek@NetBSD.ORG | |||||||
| Andy Doran | ad@NetBSD.ORG | |||||||
| Roland Dowdeswell | elric@NetBSD.ORG | |||||||
| Matthias Drochner | drochner@NetBSD.ORG | |||||||
| Jun Ebihara | jun@NetBSD.ORG | |||||||
| Havard Eidnes | he@NetBSD.ORG | |||||||
| Enami Tsugutomo | enami@NetBSD.ORG | |||||||
| Bernd Ernesti | veego@NetBSD.ORG | |||||||
| Erik Fair | fair@NetBSD.ORG | |||||||
| Hubert Feyrer | hubertf@NetBSD.ORG | |||||||
| Thorsten Frueauf | frueauf@NetBSD.ORG | |||||||
| Castor Fu | castor@NetBSD.ORG | |||||||
| Brian R. Gaeke | brg@dgate.org | |||||||
| Thomas Gerner | thomas@NetBSD.ORG | |||||||
| Simon J. Gerraty | sjg@NetBSD.ORG | |||||||
| Justin Gibbs | gibbs@NetBSD.ORG | |||||||
| Adam Glass | glass@NetBSD.ORG | |||||||
| Michael Graff | explorer@NetBSD.ORG | |||||||
| Brian C. Grayson | bgrayson@NetBSD.ORG | |||||||
| Brad Grantham | grantham@tenon.com | |||||||
| Matthew Green | mrg@NetBSD.ORG | |||||||
| Juergen Hannken-Illjes | hannken@NetBSD.ORG | |||||||
| Charles M. Hannum | mycroft@NetBSD.ORG | |||||||
| Eric Haszlakiewicz | erh@NetBSD.ORG | |||||||
| HAYAKAWA Koichi | haya@NetBSD.ORG | |||||||
| Rene Hexel | rh@NetBSD.ORG | |||||||
| Michael L. Hitch | mhitch@NetBSD.ORG | |||||||
| Christian E. Hopps | chopps@NetBSD.ORG | |||||||
| Ken Hornstein | kenh@NetBSD.ORG | |||||||
| Marc Horowitz | marc@NetBSD.ORG | |||||||
| Dean Huxley | dean@netbsd.org | |||||||
| ITOH Yasufumi | itohy@NetBSD.ORG | |||||||
| Matthew Jacob | mjacob@NetBSD.ORG | |||||||
| Lonhyn T. Jasinskyj | lonhyn@NetBSD.ORG | |||||||
| Chris Jones | cjones@NetBSD.ORG | |||||||
| Soren Jorvang | soren@NetBSD.ORG | |||||||
| Antti Kantee | pooka@NetBSD.ORG | |||||||
| Lawrence Kesteloot | kesteloo@cs.unc.edu | |||||||
| Thomas Klausner | wiz@NetBSD.ORG | |||||||
| Klaus Klein | kleink@NetBSD.ORG | |||||||
| John Kohl | jtk@NetBSD.ORG | |||||||
| Kevin Lahey | kml@NetBSD.ORG | |||||||
| Johnny C. Lam | jlam@NetBSD.ORG | |||||||
| Martin J. Laubach | mjl@NetBSD.ORG | |||||||
| Ted Lemon | mellon@NetBSD.ORG | |||||||
| Joel Lindholm | joel@NetBSD.ORG | |||||||
| Mike Long | mikel@NetBSD.ORG | |||||||
| Warner Losh | imp@NetBSD.ORG | |||||||
| Brett Lymn | blymn@NetBSD.ORG | |||||||
| Paul Mackerras | paulus@NetBSD.ORG | |||||||
| Dan McMahill | dmcmahill@NetBSD.ORG | |||||||
| Neil J. McRae | neil@NetBSD.ORG | |||||||
| Perry Metzger | perry@NetBSD.ORG | |||||||
| der Mouse | mouse@NetBSD.ORG | |||||||
| Joseph Myers | jsm@NetBSD.ORG | |||||||
| Ken Nakata | kenn@NetBSD.ORG | |||||||
| Bob Nestor | rnestor@NetBSD.ORG | |||||||
| Tohru Nishimura | nisimura@NetBSD.ORG | |||||||
| Masaru Oki | oki@NetBSD.ORG | |||||||
| Greg Oster | oster@NetBSD.ORG | |||||||
| Herb Peyerl | hpeyerl@NetBSD.ORG | |||||||
| Matthias Pfaller | matthias@NetBSD.ORG | |||||||
| Dante Profeta | dante@NetBSD.ORG | |||||||
| Chris Provenzano | proven@NetBSD.ORG | |||||||
| Waldi Ravens | waldi@moacs.indiv.nl.net | |||||||
| Darren Reed | darrenr@NetBSD.ORG | |||||||
| Michael Richardson | mcr@NetBSD.ORG | |||||||
| Tim Rightnour | garbled@NetBSD.ORG | |||||||
| Gordon Ross | gwr@NetBSD.ORG | |||||||
| Heiko W. Rupp | hwr@NetBSD.ORG | |||||||
| SAITOH Masanobu | msaitoh@NetBSD.ORG | |||||||
| Curt Sampson | cjs@NetBSD.ORG | |||||||
| Wilfredo Sanchez | wsanchez@NetBSD.ORG | |||||||
| Ty Sarna | tsarna@NetBSD.ORG | |||||||
| SATO Kazumi | sato@NetBSD.ORG | |||||||
| Matthias Scheler | tron@NetBSD.ORG | |||||||
| Karl Schilke (rAT) | rat@NetBSD.ORG | |||||||
| Konrad Schroder | perseant@NetBSD.ORG | |||||||
| Tim Shepard | shep@NetBSD.ORG | |||||||
| Takao Shinohara | shin@NetBSD.ORG | |||||||
| Chuck Silvers | chs@NetBSD.ORG | |||||||
| Thor Lancelot Simon | tls@NetBSD.ORG | |||||||
| Noriyuki Soda | soda@NetBSD.ORG | |||||||
| Bill Sommerfeld | sommerfeld@NetBSD.ORG | |||||||
| Bill Studenmund | wrstuden@NetBSD.ORG | |||||||
| Kevin Sullivan | sullivan@NetBSD.ORG | |||||||
| Kimmo Suominen | kim@NetBSD.ORG | |||||||
| Matt Thomas | matt@NetBSD.ORG | |||||||
| Christoph Toshok | toshok@NetBSD.ORG | |||||||
| Izumi Tsutsui | tsutsui@NetBSD.ORG | |||||||
| UCHIYAMA Yasushi | uch@NetBSD.ORG | |||||||
| Todd Vierling | tv@NetBSD.ORG | |||||||
| Aymeric Vincent | aymeric@NetBSD.ORG | |||||||
| Paul Vixie | vixie@NetBSD.ORG | |||||||
| Krister Walfridsson | kristerw@NetBSD.ORG | |||||||
| Lex Wennmacher | wennmach@NetBSD.ORG | |||||||
| Assar Westerlund | assar@NetBSD.ORG | |||||||
| Rob Windsor | windsor@NetBSD.ORG | |||||||
| Dan Winship | danw@NetBSD.ORG | |||||||
| Jim Wise | jwise@NetBSD.ORG | |||||||
| Colin Wood | ender@NetBSD.ORG | |||||||
This product includes software developed by the University of
California, Berkeley and its contributors.
This product includes software developed by the Computer
Systems Engineering Group at Lawrence Berkeley Laboratory.
This product includes software developed by the NetBSD
Foundation, Inc. and its contributors.
This product includes software developed by Adam Glass
and Charles Hannum.
This product includes software developed by Adam Glass.
This product includes software developed by Berkeley Software
Design, Inc.
This product includes software developed by Charles D. Cranor
and Washington University.
This product includes software developed by Charles D. Cranor.
This product includes software developed by Charles Hannum,
by the University of Vermont and State Agricultural College
and Garrett A. Wollman, by William F. Jolitz, and by the
University of California, Berkeley, Lawrence Berkeley Laboratory,
and its contributors.
This product includes software developed by Charles Hannum.
This product includes software developed by Charles M. Hannum.
This product includes software developed by Chris Provenzano.
This product includes software developed by Christian E. Hopps.
This product includes software developed by Christopher G. Demetriou
for the NetBSD Project.
This product includes software developed by Christopher G. Demetriou.
This product includes software developed by Christos Zoulas.
This product includes software developed by David Jones and Gordon Ross.
This product includes software developed by Dean Huxley.
This product includes software developed by Eric S. Hvozda.
This product includes software developed by Ezra Story.
This product includes software developed by Gordon Ross.
This product includes software developed by Gordon W. Ross
and Leo Weppelman.
This product includes software developed by Gordon W. Ross.
This product includes software developed by Herb Peyerl.
This product includes software developed by Ian W. Dall.
This product includes software developed by Ignatios Souvatzis
for the NetBSD Project.
This product includes software developed by Jason R. Thorpe
for And Communications, http://www.and.com/.
This product includes software developed by Joachim Koenig-Baltes.
This product includes software developed by Jochen Pohl
for The NetBSD Project.
This product includes software developed by John Polstra.
This product includes software developed by Jonathan Stone
and Jason R. Thorpe for the NetBSD Project.
This product includes software developed by Jonathan Stone
for the NetBSD Project.
This product includes software developed by Jonathan Stone.
This product includes software developed by Julian Highfield.
This product includes software developed by Kenneth Stailey.
This product includes software developed by Leo Weppelman.
This product includes software developed by Lloyd Parkes.
This product includes software developed by Mark Brinicombe.
This product includes software developed by Markus Wild.
This product includes software developed by Martin Husemann
and Wolfgang Solfrank.
This product includes software developed by Mats O Jansson
and Charles D. Cranor.
This product includes software developed by Mats O Jansson.
This product includes software developed by Matthias Pfaller.
This product includes software developed by Paul Kranenburg.
This product includes software developed by Paul Mackerras.
This product includes software developed by Peter Galbavy.
This product includes software developed by Philip A. Nelson.
This product includes software developed by Rodney W. Grimes.
This product includes software developed by Scott Bartram.
This product includes software developed by SigmaSoft, Th. Lockert.
This product includes software developed by Terrence R. Lambert.
This product includes software developed by Theo de Raadt
and John Brezak.
This product includes software developed by Theo de Raadt.
This product includes software developed by TooLs GmbH.
This product includes software developed by Winning Strategies, Inc.
This product includes software developed by the Center for
Software Science at the University of Utah.
This product includes software developed by the University of Calgary
Department of Computer Science and its contributors.
This product includes software developed by the University of Vermont
and State Agricultural College and Garrett A. Wollman.
This product includes software developed for the FreeBSD project.
This product includes software developed for the Internet
Software Consortium by Ted Lemon.
This product includes software developed for the NetBSD Project
by Frank van der Linden.
This product includes software developed for the NetBSD Project
by Jason R. Thorpe.
This product includes software developed for the NetBSD Project
by John M. Vinopal.
This product includes software developed for the NetBSD Project
by Matthias Drochner.
This product includes software developed for the NetBSD Project
by Matthieu Herrb.
This product includes software developed for the NetBSD Project
by Perry E. Metzger.
This product includes software developed for the NetBSD Project
by Piermont Information Systems Inc.
This product includes software developed for the NetBSD Project
by Ted Lemon.
This product includes software developed by LAN Media Corporation
and its contributors.
This product includes software developed by Michael Graff for
the NetBSD Project.
This product includes software developed by Niklas Hallqvist,
C Stone and Job de Haas.
This product includes software developed by the Computer
Systems Laboratory at the University of Utah.
This product includes software developed by the University of
Vermont and State Agricultural College and Garrett A. Wollman.
This product includes software developed by Charles D. Cranor.
This product includes software developed by Adam Glass.
This product includes software developed by Charles Hannum.
This product includes software developed by David Jones.
This product includes software developed by Gordon W. Ross.
This product includes software developed by Steve C. Woodford.