About this Document............................................2
Quick install notes for the impatient..........................3
What is NetBSD?................................................4
Upgrade path to NetBSD 1.5.3...................................4
Major Changes Between 1.5.2 and 1.5.3..........................5
Known Caveats with 1.5.3.......................................6
Major Changes Between 1.5.1 and 1.5.2..........................6
Major Changes Between 1.5 and 1.5.1............................6
Changes Between The NetBSD 1.4 and 1.5 Releases................9
Kernel......................................................9
Networking..................................................9
File system.................................................9
Security...................................................10
System administration and user tools.......................10
Miscellaneous..............................................11
The Future of NetBSD..........................................11
Sources of NetBSD.............................................12
NetBSD 1.5.3 Release Contents.................................12
NetBSD/macppc subdirectory structure.......................14
Binary distribution sets...................................14
NetBSD/macppc System Requirements and Supported Devices.......15
Supported models...........................................16
Unsupported models.........................................17
Supported devices..........................................17
Unsupported devices........................................19
Supported boot devices and media...........................20
Getting the NetBSD System on to Useful Media..................20
Preparing your System for NetBSD installation.................21
Prepare yourself...........................................21
Updating your BootROM......................................22
Getting to the Open Firmware Prompt on Newer Models........23
Getting to the Open Firmware Prompt on Apple Network.......23
Getting to the Open Firmware Prompt on Older Models........24
Older Open Firmware System Preparation.....................24
Getting to the Open Firmware Prompt (Recommended method using25
Getting to the Open Firmware Prompt (Harder method using...26
Getting to the Open Firmware Prompt (Without using MacOS)..26
Setting up pre-Open Firmware 3 to boot NetBSD..............27
Setting up Open Firmware 3 to boot NetBSD..................28
Available Boot Media.......................................29
Description of bootable media..............................30
Partitioning your hard drive for NetBSD....................32
Preparing the Bootable Media...............................34
Booting off an MS-DOS floppy............................34
Booting off the NetBSD install floppy...................35
Booting off an HFS or HFS+ partition....................36
Booting off the NetBSD/macppc CD-R image................36
Booting off an ISO9660 CD-ROM...........................36
Booting off a hybrid HFS/ISO9660 CD-ROM.................37
Booting over the ethernet...............................38
Booting the floppy image off a SCSI or IDE drive........40
Installing the NetBSD System..................................41
Open Firmware boot syntax..................................41
Examples of Open Firmware boot commands....................44
Booting off an MS-DOS floppy............................44
Booting off the NetBSD install floppy...................44
Booting off the NetBSD/macppc install CD-R..............45
Booting off the NetBSD/macppc install CD-R..............45
Booting off a home-made CD-ROM ISO9660 or Hybrid........45
Booting off an IDE or SCSI drive with 'partition zero'..45
Booting off an IDE or SCSI drive with an HFS partition..46
Example of a normal boot...................................46
Common Problems and Error Messages.........................47
Black screen............................................47
Grey screen with flashing question mark.................47
Information on your screen seems garbled or out of sync.48
DEFAULT CATCH!..........................................48
CLAIM failed............................................48
can't OPEN..............................................48
unrecognized Client Program formatstate not valid.......49
bad partition number, using 0no bootable HFS partition..49
TFTP timeout............................................49
Bootloader hangs before the copyright notice............49
Hang after configuring devices..........................49
Milestone..................................................50
Running the sysinst installation program...................50
Introduction............................................50
General.................................................50
Quick install...........................................50
Booting NetBSD..........................................51
Network configuration...................................51
Preparing a disk which will be used for MacOS and NetBSD52
Installation drive selection and parameters.............53
Partitioning the disk...................................53
Preparing your hard disk................................54
Getting the distribution sets...........................54
Installation using ftp..................................54
Installation using NFS..................................55
Installation from CD-ROM................................55
Installation from an unmounted file system..............55
Installation from a local directory.....................55
Extracting the distribution sets........................55
Making the device nodes.................................56
Finalizing your installation............................56
Post installation steps.......................................57
Upgrading a previously-installed NetBSD System................59
Compatibility Issues With Previous NetBSD Releases............60
General issues.............................................60
Issues affecting an upgrade from NetBSD 1.4 or prior.......60
Using online NetBSD documentation.............................61
Administrivia.................................................61
Thanks go to..................................................62
We are........................................................64
Legal Mumbo-Jumbo.............................................68
The End.......................................................70
This document describes the installation procedure for
NetBSD1.5.3
on the
macppc
platform. It is available in four different formats titled
INSTALL.ext,
where
.ext
is one of
.ps, .html, .more,
or .txt:
.ps.html.moremore(1)
and
less(1)
pager utility programs. This is the format in which the on-line
man
pages are generally presented.
.txtYou are reading the HTML version.
This section contains some brief notes describing what you need to install NetBSD1.5.3 on a machine of the macppc architecture.
installation/ofwboot.xcf
and the installation kernel
installation/netbsd.ram.gz.
Alternatively, you can fetch the CD image,
macppc_bootable.iso
or the boot floppy image
installation/boot.fs
which include the bootloader and installation kernel.
You only need the installation kernel and bootloader, or the CD image to
boot your system.
Alternatively, you may netboot the installation kernel, which requires
several local netboot services. The details are not covered here, as
setting up a netboot server is hardly
``quick''.
binary/sets/
directory.
When you boot the install
kernel from floppy, hard drive, or CD-ROM,
the installation program
can fetch these files for you (using e.g. ftp),
if you have a network connection.
There are several other methods to get the binary sets onto
your machine.
You will at a minimum need
the following sets:
kern.tgz,
base.tgz
and
etc.tgz.
In a typical workstation installation you will probably want
all the installation sets.
ofwboot.xcf and netbsd.ram.gz
to an MS-DOS formatted floppy disk and rename
netbsd.ram.gz to netbsd.gz.
Otherwise, drag
ofwboot.xcf and netbsd.ram.gz
to your hard drive icon (the top level of the drive, not the desktop). If
you are making a CD, burn it now.
The disk(s) you just prepared will be used to boot the installation kernel, which contains all the tools required to install NetBSD.
At present,
NetBSD/macppc
cannot exist on the same hard drive as
MacOS
unless you partition your disk using a
MacOS
partitioning utility. Open Firmware versions prior to 3 cannot boot into
NetBSD
on a drive partitioned this way -- you must use the entire disk,
partitioned with the installation tools. Open Firmware version 3 cannot
boot into
NetBSD
on a drive partitioned with the installation tools, you must use a
MacOS
partitioning utility and the
``Re-install sets or install additional sets''
option in the installer (selecting the
``Install NetBSD to hard disk''
or
``Upgrade NetBSD on a hard disk''
options will render your drive unbootable). If you are unsure, you may
want to read the section below on
Partitioning your hard drive for NetBSD
You should have the Open Firmware
``
For boot CDs, the command is something like
``boot cd:,\ofwboot.xcf netbsd.macppc''
(for Open Firmware 3) or
``boot scsi-int/sd@3:0 NETBSD.MACPPC''
(for earlier Open Firmware versions).
You will need to use the correct case for
OFWBOOT.XCF and NETBSD.MACPPC
depending on how your version of Open Firmware interprets the ISO
filesystem. You may need to replace
cd
with
scsi/sd@3 , scsi-int/sd@3 , scsi-ext/sd@3 , ata/atapi-disk ,
or some other device alias. You should also use the Open Firmware
dir
command to confirm that the
NetBSD/macppc
kernel is called
COMMAND-OPTION-O-F
keys after the boot chime starts, but before it ends. Entering Open
Firmware versions prior to 3 is usually the most frustrating part of
installation -- you may want to read the section below on
Older Open Firmware System Preparation
0 >''
prompt on your screen before attempting to boot
NetBSD/macppc.
NETBSD.MACPPC.
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.3
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.
NetBSD
1.5.3 is an upgrade of
NetBSD
1.5, 1.5.1, 1.5.2, and earlier major and maintenance releases of
NetBSD.
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.5 was started are designated
by version identifiers such as 1.5A, 1.5B, etc.
These identifiers do not designate releases, but indicate major changes
in internal kernel APIs.
Note that the kernel from
NetBSD
1.5.3 can
not
be used to upgrade a system running one of those intermediate development
versions.
Trying to use the
NetBSD
1.5.3 kernel on such a system
will
probably 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.5.3 to determine if a given feature is present or absent
in 1.5.3. The development of 1.5 and the subsequent maintenance releases
is done on a separate branch in the CVS repository.
The branch was created when
the release cycle for 1.5 was started, and during the release cycle of
1.5 and its maintenance releases, selected fixes and enhancements have been
imported from the main development trunk.
So, there are features in 1.5.3 which were not in, e.g. 1.5B, and vice
versa.
In addition, many bugs have been fixed--more than 70 problems
reported through our problem tracking system have been fixed,
and several other non-reported problems have also been found and fixed.
See the CHANGES-1.5.3 file for the complete list.
Additionally, a few more bugs have been fixed.
See the CHANGES-1.5.2 file for the complete list of changes.
In addition, many bugs have been fixed--more than 95 problems
reported through our problem tracking system have been fixed,
and some other non-reported problems have also been found and fixed.
See the CHANGES-1.5.1 file for the complete list.
The NetBSD Packages Collection (pkgsrc) which is used to maintain,
build, track dependencies, and maintain NetBSD-specific fixes to
third-party programs, has received a major overhaul for NetBSD 1.5.1.
Some highlights are:
Please note that at the moment,
sysinst
will not assist you in
installing pre-built third-party binary packages or the pkgsrc
system itself, so you will have to manually install packages using
pkg_install
or fetch and extract the pkgsrc.tgz tar file to get started.
Lastly, it should be noted that the X11 binaries shipped in
NetBSD
1.5.3
is still based on XFree86 version 3.3.6.
Several newer graphics cards are inadequately supported
by that code base, but on the other hand support for several
older graphics cards is not available in newer XFree86 code.
NetBSD
is in the process of moving to XFree86 version 4, and is currently
maintaining both the XFree86 3.3.6 and the XFree86 version 4 code
in the
xsrc
source set, and you may at compile time pick which sources to
build and install.
To ease installation, testing and use of the XFree86 version 4
code, a binary snapshot based on XFree86
version 4.0.3 will be made available for at least the i386
architecture shortly after the release of
NetBSD
1.5.3.
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.3
release. Some highlights include:
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 second major release of
NetBSD
for the macppc platform, including the Apple iBook, iMac, PowerMacintosh, and
PowerBook models, as well as clones.
As is usual between releases, the macppc port has had many improvements
made to it - too many to detail all of them here.
Numerous new drivers have been added.
See the supported hardware list for details.
Some (but not all!) notable macppc-specific improvements include:
NetBSD1.5.3
on macppc is, as usual, also fully backward compatible with old
NetBSD/macppc
binaries, so you don't need to recompile all your local programs
provided you set the appropriate binary compatibility options in your
kernel configuration.
The
NetBSD
Foundation 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.3
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.3
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.
The binaries shipped with
NetBSD
1.5.3
are based on XFree86 version 3.3.6.
NetBSD
is in the process of moving to XFree86 version 4, and
the X source set actually contains source for both XFree86 3.3.6
and XFree86 4, and the ability to decide
at compile-time which one to build and install.
The X Window System binary sets distributed with
NetBSD
are:
The macppc 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
Currently,
NetBSD/macppc
requires the use of
Open Firmware
to boot.
Open Firmware is a command environment using the FORTH language which the
NetBSD
kernel uses to gether information about your system, and to control some
of your devices. It is part of the boot ROMs in most
PowerPC-based Macintosh
systems. Until late 1996,
Apple
never intended to use Open Firmware for anything other than internal debugging and hardware support. It was not
intended to be used to boot an operating system. This is why earlier machines
have so much trouble with Open Firmware.
This also means that PowerMacs and clones that lack Open Firmware cannot boot
NetBSD
on the macppc platform. Most machines introduced by Apple and the clone-makers
after August 17, 1995 have Open Firmware and are supported.
Apple made several revisions of this Open Firmware environment, and each has
various quirks and problems that we must work around. The single hardest step
of installing
NetBSD/macppc
is to set up Open Firmware properly. Open Firmware versions 1.0.5 and
2.0.x act
similarly and the same set of instructions applies to them. Open Firmware
version 2.4 is slightly different with regards to booting. Open Firmware
version 3 is altogether different.
At present,
NetBSD/macppc
does not support the PPC 601 microprocessor, which means that the
PowerMacintosh 7200 and 7500 models are not supported. The PowerMacintosh
7500 may be upgraded to a PPC 604, G3, or G4 microprocessor via a
daughtercard replacement, in which case
NetBSD
will run on this system.
The minimal configuration requires 16 MB of RAM and ~80 MB of disk space.
To install the entire system requires much more disk space, and to run
X or compile the system, more RAM is recommended, as
NetBSD
with 16 MB of RAM is very slow. Note that until you have
around 32 MB of RAM, getting more RAM is more important than getting a
faster CPU.
Go to the
NetBSD/macppc
Model Support webpage and look up your system. Take note of the comments
about your model and keep these in mind during the rest of this installation
procedure.
http://www.netbsd.org/Ports/macppc/models.html
You should wait to decide where to put the
NetBSD
distribution sets until you have figured out how you are going to boot
your system. Refer back to this section after you have done so.
Installation is supported from several media types, including:
The steps necessary to prepare the distribution sets for installation
depend upon which installation medium you choose.
The steps for the various media are outlined below.
Proceed to the instruction on installation.
Once you have this information, you can proceed to the next
step in the installation or upgrade process.
If you're installing
NetBSD
from scratch, go to the section on preparing your hard disk, below.
If you're upgrading an existing installation, go directly to
the section on upgrading.
You need to know the numeric IP address of the NFS server,
and, if the server is not on a network directly connected to
the machine on which you're installing or upgrading
NetBSD,
you need to know the numeric IP address of the router closest
to the
NetBSD
machine.
Finally, you need to know the numeric IP address of the
NetBSD
machine itself.
Once the NFS server is set up properly and you have the
information mentioned above, you can proceed to the next step
in the installation or upgrade process.
If you're installing
NetBSD
from scratch, go to the section on preparing your hard disk, below.
If you're upgrading an existing installation, go directly to the
section on upgrading.
Good. Now, make sure you are reading the PDF (if available), PostScript,
or HTML version of this document, as the
While it's printing, get some coffee, relax a bit, and mentally prepare
yourself for something that promises to be confusing, frustrating, and
annoying. If you assume the worst, you'll be pleasantly surprised when
everything works easier than you expected. Also, forget everything you've
been told about installing
NetBSD/macppc.
That's right, flush your knowledge cache -- some of it is almost
certainly dirty.
Some of this document assumes familiarity with
MacOS,
e.g. how to download BinHex files and extract things with StuffIt
Expander. If you've never heard of those terms before, it is possible to
install
NetBSD/macppc
without booting or knowing how to use
MacOS,
but depending on your model it may be almost as painful as learning a
little
MacOS.
See the FAQ for more help:
http://www.netbsd.org/Ports/macppc/faq.html#macos-newbie
It's done printing? Fine, now get a dark writing implement.
The recommended installation procedure is as follows:
Open Firmware 3 systems have a rewritable
``firmware'',
also called the BootROM. When you use an Apple
firmware updater, it updates the BootROM. This will
not
change the version of Open Firmware in your machine - it will still be
Open Firmware 3. The BootROM is what is first executed when you power on
or reset your system. The BootROM then loads Open Firmware, which boots
your operating system.
Go to the
`Apple Software Updates'
web site at
http://asu.info.apple.com/
and search for
`firmware'
and install the most recent version for your model.
You will need to run the FirmWare updater from MacOS 9.
The PowerBook (FireWire) and PowerBook G4
(Titanium) models with BootROM 4.1.8 are not supported in this release.
If your system has this BootROM, you must use a kernel from the -current
branch.
There are reports that FirmWare Update 4.1.9 on iMac (Summer 2000) will
prevent the CD-ROM and the hard drive from operating together. You may get
Hold down a special four-key combination when your system boots.
After the chime starts, but before it stops, hold down the four
Welcome to Open Firmware.
To continue booting, type "mac-boot" and press return.
To shut down, type "shut-down" and press return.
ok
0 >
Now, set your system to always stop at the Open Firmware prompt.
Skip down to the section on
Setting up Open Firmware 3 to boot NetBSD
since the next several pages are instructions for older models.
The version of Open Firmware in the
Apple Network Servers can only use a serial console.
You must first hook up a serial console
(38400 bps, 8 bits, no parity, 1 stop bit, no handshaking) to
`Port 2'
(the
`
Hold down a special four-key combination on the keyboard attached to
the ADB port on your system (not the serial console) when
your system boots.
After the chime starts, but before it stops, hold down the four
Your Apple Network Server's screen will remain black.
Now, set your system to always stop at the Open Firmware prompt.
Skip down to the section on
Setting up pre-Open Firmware 3 to boot NetBSD
since the next several pages are instructions for MacOS models.
These models are significantly trickier than the newer machines.
Open Firmware has two variables,
`input-device'
and
`output-device',
which specify which devices to use for input and output.
All Open Firmware 1.0.5 and most Open Firmware 2.0.x systems will default
to using the
`Modem'
serial port for the console instead of the ADB keyboard and the monitor
attached to the on-board video.
Unless you use a MacOS-based utility to set
these variables correctly, you
will
need to hook up a serial console temporarily to configure Open Firmware
to use your keyboard and screen. Some models (such as the Performa 54xx,
6360, 6400, and 6500) have the
`Modem'
serial port covered with a piece of plastic since the internal modem
usurps that serial port. You will either need to use Boot Variables to
set the
`input-device'
and
`output-device'
variables to
`ttyb'
(which is the Printer serial port) or remove the internal modem.
Now would be a good time to look at the
NetBSD/macppc
Model Support webpage to determine the issues with your model.
http://www.netbsd.org/Ports/macppc/models.html
In particular, some models
must
use a serial console, or they will be unable to boot
NetBSD
at all. All models can be set to use a serial console, if you desire
to bypass the keyboard and screen.
If, after re-reading the next several sections, you still need help
figuring out your
`input-device'
and
`output-device'
settings, see the FAQ:
http://www.netbsd.org/Ports/macppc/faq.html#ofw-input-output-devices
If you need to use a serial console, you can use a normal
`printer'
cable (mini-DIN 8 to mini-DIN 8) and a
MacOS
tool, such as ZTerm to
connect a
MacOS
system to your
NetBSD/macppc
system.
http://hyperarchive.lcs.mit.edu/HyperArchive/Archive/comm/term/zterm-101.hqx
See the NetBSD Serial Port Primer for additional help and references:
http://www.netbsd.org/Documentation/Hardware/Misc/serial.html
All pre-Open Firmware 3 macppc systems have Open Firmware bugs. Luckily, Open
Firmware has a small
Non-Volatile RAM variable (NVRAM) which is reserved for FORTH commands which
will be run before booting an operating system. Apple has released a freeware
MacOS
tool called System Disk, which patches
most of these bugs. We
strongly
recommend that you use this tool to patch your Open Firmware,
as several systems cannot boot without these patches. Instructions for
using System Disk are covered in the next section.
Unfortunately, some models are broken by or are unsupported by System Disk.
If you have one of the following models, then skip down to the section on
Getting to the Open Firmware Prompt (Harder method using MacOS)
Download System Disk:
ftp://ftp.apple.com/developer/macosxserver/utilities/SystemDisk2.3.1.smi.bin
For a brief tutorial on how to use System Disk, see:
http://www.netbsd.org/Ports/macppc/SystemDisk-tutorial/
Launch the
MacOS
System Disk tool. Click on
``Power User (Open Firmware)''
then click on the
``Advanced Options''
button. Now, click on the checkbox that says
``Stop Boot at Open Firmware prompt''
and select
``OK''.
Click the
``Save''
button and reboot your system.
If your
`output-device'
is
`
You should now see the Open Firmware command prompt on your screen:
If your screen is black, then your model does not support using the
on-board video in
Open Firmware. You will need to connect a serial console to the
`Modem'
port of your system
(38400 bps, 8 bits, no parity, 1 stop bit, no handshaking).
If System
Disk doesn't work because your version of
MacOS
is too old or because
System Disk says that it doesn't support your model, then you may try using
the
MacOS
BootVars tool.
ftp://ftp.netbsd.org/pub/NetBSD/arch/macppc/macos-utils/bootvars/bootvars.sit.hqx
Look up the proper
`output-device'
for your model on the
NetBSD/macppc
Model Support webpage.
http://www.netbsd.org/Ports/macppc/models.html
If the
NetBSD/macppc
Model support webpage does not list an
`output-device'
for your model, then your system will default to using the on-board
video. You needn't fill in the
`output-device'
and
`input-device'
variables.
Launch the
MacOS
BootVars tool. Uncheck the
``auto-boot?''
checkbox, then check on the
``All Variables''
checkbox and type
kbd
into the
`input-device'
box, and the proper device name into the
`output-device'
box.
Click on the
``write''
button, and then reboot your system.
If your
`output-device'
is
`
You should now see the Open Firmware command prompt on your screen:
If your screen is black, then your model has defaulted to using a serial
console. This is fairly common on Open Firmware 1 and 2 models if you do not
use the System Disk tool to set up Open Firmware. You must hook up a serial
console (38400 bps, 8 bits, no parity, 1 stop bit, no handshaking).
If you don't
have
MacOS,
then you need to hold down a special four-key combination when your system
boots. Do this on the keyboard attached to
the ADB port on your system (not the serial console or PS/2 port) when
your system boots.
After the chime starts, but before it stops, hold down the four
If your screen is black, then your system has defaulted to using a serial
console. This is fairly common on Open Firmware 1 and 2 models if you do
not use the System
Disk tool to set up Open Firmware. You must hook up a serial console
(38400 bps, 8 bits, no parity, 1 stop bit, no handshaking).
Now, set your system to always stop at the Open Firmware prompt.
To use your on-board video and keyboard, look up the proper
`output-device'
for your model on the
NetBSD/macppc
webpage
http://www.netbsd.org/Ports/macppc/models.html
Run the following commands to use your screen instead of
a serial console
(replace
`
Now you should see the Open Firmware prompt on your screen.
If your
`output-device'
is
`
This section describes some steps you must take to prepare Open Firmware
to boot
NetBSD.
Additional resources are available in the FAQ regarding how to use
the Open Firmware command environment, and the Open Firmware variables
you may be using:
http://www.netbsd.org/Ports/macppc/faq.html#ofw-access
http://www.netbsd.org/Ports/macppc/faq.html#ofw-variables
Double-check your Open Firmware version:
If your system has Open Firmware prior to version 3, then you must set
some Open Firmware variables before
NetBSD
can boot. Do
not
run these commands on Open Firmware 3 machines, as you may overwrite your
firmware requiring a trip to Apple for repairs.
The last command reboots your machine so that the
settings are stored.
If you will be netbooting your system, you can look up your MAC address.
You can check your Open Firmware settings with the
This section describes some steps you must take to prepare Open Firmware
to boot
NetBSD.
Additional resources are available in the FAQ regarding how to use
the Open Firmware command environment, and the Open Firmware variables
you may be using:
http://www.netbsd.org/Ports/macppc/faq.html#ofw-access
http://www.netbsd.org/Ports/macppc/faq.html#ofw-variables
Double-check your Open Firmware version:
If you will be netbooting your system, you can look up your MAC address.
You can check your Open Firmware settings with the
Each version of Open Firmware is capable of booting from a variety of
media (such as hard drives, floppy disks, CD-ROMs, and ethernet). Open
Firmware is able to boot files from a variety of filesystems (such as ISO9660,
MS-DOS, and on some models HFS and HFS+). Unfortunately, Open Firmware is
not
able to use the
NetBSD
filesystem (FFS), so we must put the bootloader in a location that Open
Firmware is capable of using.
Therefore, to boot the
NetBSD
kernel, Open Firmware must first open a
`bootloader'
which knows how to load the
NetBSD
kernel. There are two approaches, the
The following bootable media are available for loading the bootloader
(
Once
Such as the boot floppy, or an installed
NetBSD
partition.
Only on Open Firmware 2.4 or Open Firmware 3 systems.
The boot floppy image provided with the distribution sets has a
`partition zero'
bootloader and a
NetBSD
file system with an installation kernel. The boot CD-R images provided
with the distribution sets has both a
`partition zero'
bootloader and
This section gives a quick description of the various media that can be
used by Open Firmware to load the bootloader.
This method loads a primary bootloader called
While Open Firmware 3 supports this boot method,
NetBSD/macppc
does not yet support it on these systems.
This method loads
Alternatively, the kernel (compressed
or non-compressed) may be on an HFS or HFS+ partition. Due to Open Firmware
pickiness, it must be on the same partition as
Load the
You can run your entire system diskless or netboot only the files necessary
to boot (i.e. the bootloader and the installation kernel),
but you must have root access on another
UNIX
machine on your subnet.
Load the
Open Firmware 1.0.5 and 2.0.x machines will
not
boot from the ISO9660 file system if you create a hybrid HFS/ISO
format CD-R. Make sure that the CD
only
has ISO9660 data and does not have an Apple Partition Map.
Load the
Make sure that the CD has an Apple Partition Map.
You can use the instructions in this section to partition a disk that may
also be used with
MacOS,
although a disk prepared in this way
will not boot
NetBSD.
That means, your root partition
Unless you are planning to use partitions on the same disk as
MacOS,
skip forward to
Preparing the Bootable Media
If you'd like to have
MacOS
and
NetBSD
partitions on one hard drive (and for both to be bootable),
then read the rest of this section.
This is the drive that will be holding the bootloader,
The rest of this section describes how to make a
single disk dual-bootable which is necessary for machines which have only
one hard drive (such as the iBook, iMac, PowerBook, and PowerMacintosh Cube
systems).
Using the
NetBSD
installer to install a disklabel or bootloader will
render your disk unusable by
MacOS.
Either will also prevent Open Firmware 3 machines from booting.
You will need to use the installer's
``Re-install sets''
option. More information is provided below on this process.
There are several contradictory partition numbering schemes. You may want
to look at the explanation in the FAQ.
http://www.netbsd.org/Ports/macppc/faq.html#partitions
Unfortunately, the partitioning tools for
NetBSD
are not advanced enough to create HFS or HFS+ file systems or a
partition map that can be shared with
MacOS.
You will need to use the
MacOS
Drive Setup tool (versions 1.8.1 and later are
known to work) to partition the hard drive you will be using for
NetBSD.
Drive Setup will erase the contents of your drive -- it does not preserve
data from any of your partitions. Make the following partitions:
If you need further help, there is a partitioning HOW-TO on the
NetBSD
website:
http://www.netbsd.org/Ports/macppc/partitioning.html
If you will be running your system diskless (i.e. entirely over NFS, not
using any local hard drives), then you do not need to run the installer,
you only need to extract the distribution sets on the diskless server.
To get the distribution sets (which will be placed on your
hard drive) onto appropriate media, see the above section entitled
Getting the NetBSD System on to Useful Media
.
You may wish to do this at the same time you create the bootable media
(such as netbooting and placing distribution sets on the netboot server,
or booting from CD-R and placing distribution sets on the same disk)
These are the recommended techniques for booting the
NetBSD
install kernel:
What follows are the steps to create different types of bootable media.
You should only need to create one of these to get your system to boot the
installer
Skip forward to
Installing the NetBSD System
Get either the
rawrite.exe
program from the NetBSD/i386 distribution or
rawrite32.exe
from
http://www.duskware.com/rawrite32/
Get
DiskCopy
6.3.3 from
http://downloAd.info.apple.com/Apple_Support_Area/Apple_Software_Updates/English-North_American/Macintosh/Utilities/Disk_Copy/Disk_Copy_6.3.3.smi.bin
If you are running a
MacOS
version prior to 9.0, get
ftp://ftp.netbsd.org/pub/NetBSD/arch/macppc/macos-utils/MakeDiskCopyFloppyType.hqx
and un-BinHex it. Then, drag the
Get
suntar
from
http://hyperarchive.lcs.mit.edu/HyperArchive/Archive/cmp/suntar-222.hqx
Skip forward to
Installing the NetBSD System
Place
Skip forward to
Installing the NetBSD System
Go to one of the
NetBSD
mirror sites and download CD-R image from the
Get and install cdrecord.
NetBSD
users should install it from the package collection. Other unix systems
should get it from the official website:
You will need to substitute the correct name of the disk image file,
speed for your CD writer, and the
correct device for your system (for i386 it would be
Skip forward to
Installing the NetBSD System
This section describes how to create your own bootable
NetBSD/macppc
CD-R. We recommend that you use the official
NetBSD/macppc-1.5.3
CD-R image, as described in the section above.
Place
Get and install mkhybrid. This is now part of the cdrecord package.
NetBSD
users should install it from the package collection. Other unix systems
should get it from the official website:
You will need to substitute the correct speed for your CD writer, and the
correct device for your system (for i386 it would be
See the
NetBSD
Bootable CD-ROM HOW-TO for more detail:
http://www.netbsd.org/Documentation/bootcd.html
Skip forward to
Installing the NetBSD System
This section describes how to create your own bootable
NetBSD/macppc
CD-R. We recommend that you use the official
NetBSD/macppc-1.5.3
CD-R image, as described two sections above.
Place
Get and install mkhybrid. This is now part of the cdrecord package.
NetBSD
users should install it from the package collection. Other unix systems
should get it from the official website:
ftp://ftp.netbsd.org/pub/NetBSD/packages/pkgsrc/sysutils/cdrecord/README.html
http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html
You will need to substitute the correct speed for your CD writer, and the
correct device for your system (for i386 it would be
See the
NetBSD
Bootable CD-ROM HOW-TO for more detail:
http://www.netbsd.org/Documentation/bootcd.html
Skip forward to
Installing the NetBSD System
Set up the DHCP daemon in BOOTP compatible mode, the TFTP daemon, and
the NFS daemons on your netboot server.
Tell Open Firmware to boot over ethernet, and it will send a BOOTP
request, which will tell Open Firmware what your system's IP address
is, and where its bootloader can be downloaded via TFTP.
Once Open FIrmware has downloaded the bootloader via TFTP, it will
then load the installation kernel via an NFS connection.
Follow these instructions to configure a
NetBSD
machine as your netboot server. If you intend to use a different platform
as your netboot server, follow the directions in the Diskless HOW-TO:
http://www.netbsd.org/Documentation/network/netboot
We will use
`
You should replace all of these with the names, addresses, and paths
appropriate to your environment.
Now, set up your
dhcpd
server. Make sure the following lines are in
You will need to make sure that the
You will need to
kill
the
dhcpd
and restart it to get it to re-read its configuration file.
If the server is running
NetBSD1.5,
you can achieve this with:
Now, place a copy of the
Now, you should edit
Put the following line in
If your server is currently running NFS services, you only need to
kill -HUP
the
mountd
process. Otherwise, you need to run:
Now, you need to place the files your netboot client will need.
As noted above in the section
Preparing your System for NetBSD installation
you have several options when choosing a location to store the
distribution
filesets. However, the easiest way is to put the distribution
files into the exported directory for your client on the server.
Your client will need a kernel to boot (use
Skip forward to
Installing the NetBSD System
If the boot floppy image is compressed, then you will need to uncompress
it first.
Find a spare bootable drive (i.e. SCSI or IDE), and use some tool to write
the floppy disk image
where
Get
rawrite32.exe
from
http://www.duskware.com/rawrite32/
Be certain you have selected the correct disk, as it will erase the
contents.
Get
suntar
from
http://hyperarchive.lcs.mit.edu/HyperArchive/Archive/cmp/suntar-222.hqx
where the
You use the
If the
The
-a
flag will ask you for the location of the next item to load (i.e.
the bootloader will ask where the kernel is (if unspecified), or the
kernel will ask where the root file system is).
The
-s
flag will boot into
`single-user'
mode.
The exact command you will be using depends on which version of Open Firmware
your machine has and which device you will be booting from. Sometimes you
may have to guess as we don't know all of the combinations of models,
device names, and file names. In general the format is:
We'll try to walk you through the process of figuring out what Open
Firmware calls your device, partition, and file names.
To start with, Open Firmware keeps a
``device tree''
with all of the devices it finds in your system. You can get a
listing of the nodes in this device tree with the
dev and ls
commands.
dev
is similar to the unix
cd
command and is used to change between the nodes in the Open Firmware
device tree (similar to a filesystem).
ls
of course is similar to the unix
ls
command and is used to list the contents of the current device node.
To get a listing of all the devices available in your system, use the
following commands:
Open Firmware has device aliases which are simple names for the full
hardware path to a device (similar to
alias
in
On most systems, you'll find the devices you're looking for. Typical
aliases are:
Upgrade path to NetBSD 1.5.3
If you are not installing your system ``from scratch'' but instead
are going to upgrade an existing system already running
NetBSD
you need to know which versions you can upgrade with
NetBSD
1.5.3.
Major Changes Between 1.5.2 and 1.5.3
Some highlights are:
lpd(8)
has been fixed to deal with a security issue (SA2001-018).
ca(4)
to be replaced by
ld(4).
Drivers for the Mylex DAC960 management interface
and DPT/Adaptec I2O RAID management interface has also been added.
See
dpti(4)
and
mlxctl(8).
twe(4).
ep(4),
ex(4),
rtk(4),
sip(4),
ti(4),
tl(4),
and
wi(4).
rtk(4)
on CardBus has been added.
ne(4)
driver has been extended to support some more pcmcia cards.
pciide(4)
controllers added: HPT-370A, Acard ATP-850/860, and AMD-768.
Ultra-DMA 100 support added for CMD 0649.
emuxki(4).
esa(4).
siop(4)
driver.
sendmail(8)
has been upgraded to version 8.11.6.
Known Caveats with 1.5.3
The following are the major known issues with
NetBSD
1.5.3.
Major Changes Between 1.5.1 and 1.5.2
The main purpose of
NetBSD
1.5.2 is to fix some problems discovered shortly after the release of
NetBSD
1.5.1.
Some highlights are:
telnetd(8)
has been fixed to deal with a security issue (SA2001-012).
mount(8).
dump(8)
has been fixed to deal with a local security issue (SA2001-014).
Major Changes Between 1.5 and 1.5.1
The complete list of changes between
NetBSD
1.5 and 1.5.1 can be found in the file CHANGES-1.5.1 in the top directory
of the source tree.
The following are highlights only:
an(4).
siop(4)
driver has improved in performance and robustness.
ifconfig(8).
vlan(4).
isp(4)
driver has been upgraded to (among other things) work on MacPPC.
lfs(4)
file system has again been substantially updated, but is still
experimental.
pciide(4)
driver.
Support for Intel 82801BAM controllers has also been added, and
handling of Ali controllers has been improved.
ex(4)
driver has added support for 3Com 3c555, 3c556 and 3c556B MiniPCI Ethernet
cards.
awacs(4).
sip(4)
driver has been fixed to properly support the dp83815, as found in
current Netgear FA311 10/100 cards.
ftpd(8)
has been updated to deal with two security issues (SA2000-018 and
SA2001-005).
ntpd(8)
has been updated to deal with a security issue (SA2001-004).
telnetd(8)
has been updated to deal with a security issue (SA2000-017).
ne(4).
dhclient(8),
among other things. Please note that the new
dhcpd(8)
forces you to configure a "ddns-update-style" of either
"ad-hoc", "interim" or "none".
kerberos(8)
implementation has been upgraded to version 0.3e.
tlp(4)
driver.
yds(4).
esm(4)),
NeoMagic 256 (see
neo(4)),
and Cirrus Logic CrystalClear PCI Audio CS4281 (see
clct(4))have been added.
Changes Between The NetBSD 1.4 and 1.5 Releases
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).
sshd(8)
and
ssh(1)
now require
rnd(4)
kernel random number devices.
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.3 Release Contents
.../NetBSD-1.5.3/
CHANGESLAST_MINUTEMIRRORSREADME.filesTODOpatches/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
7.4 MB gzipped, 73.0 MB uncompressed
3.3 MB gzipped, 13.2 MB uncompressed
24.8 MB gzipped, 123.1 MB uncompressed
config(8);
and
dbsym(8).
18.0 MB gzipped, 90.9 MB uncompressed
78.1 MB gzipped, 393.6 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 - )
BSDSUMCKSUMMD5SYSVSUMNetBSD/macppc subdirectory structure
The macppc-specific portion of the
NetBSD1.5.3
release is found in the
macppc
subdirectory of the distribution:
.../NetBSD-1.5.3/macppc/
INSTALL.htmlINSTALL.psINSTALL.txtINSTALL.more.more file contains underlined text using the
more(1)
conventions for indicating italic and bold display.
binary/
kernel/
netbsd.GENERIC.gzsets/installation/
floppy/misc/Binary distribution sets
The
NetBSD
macppc
binary distribution sets contain the binaries which
comprise the
NetBSD1.5.3
release for the macppc. There are eight binary distribution sets.
The binary distribution sets can be found in the
macppc/binary/sets
subdirectory
of the
NetBSD1.5.3
distribution tree, and are as follows:
17.1 MB gzipped, 46.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.
14.4 MB gzipped, 55.4 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.
0.1 MB gzipped, 0.6 MB uncompressed
3.0 MB gzipped, 7.2 MB uncompressed
GENERIC
kernel, named
/netbsd.
You must
install this distribution set.
1.3 MB gzipped, 3.1 MB uncompressed
5.6 MB gzipped, 22.7 MB uncompressed
/usr/share.
2.2 MB gzipped, 7.5 MB uncompressed
groff(1),
all related programs, and their manual pages.
1.2 MB gzipped, 4.6 MB uncompressed
2.9 MB gzipped, 8.9 MB uncompressed
0.2 MB gzipped, 0.6 MB uncompressed
6.2 MB gzipped, 7.5 MB uncompressed
1.7 MB gzipped, 4.6 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
/.
NetBSD/macppc System Requirements and Supported Devices
Supported models
Find your model from the list below and take note of its Open Firmware
version:
Unsupported models
Supported devices
ttya
is the mini-DIN 8 serial port with the
`Modem'
icon, and
ttyb
is has the
`Printer'
icon. Some models with internal modems have the serial port with the
`Modem'
icon covered over, and the modem is
ttya.
Unsupported devices
Supported boot devices and media
Each version of Open Firmware supports different devices and media that you
may boot from. We define the terms
``bootable media''
as the media (hard drive, floppy, CD-R, ethernet) that will be used to
bootstrap your macppc system into
NetBSD,
and
``distribution sets''
or
``distribution media''
as the media (hard drive, CD-R, ethernet) that contains the files that
will be installed to generate a working
NetBSD
system onto your destination media.
Getting the NetBSD System on to Useful Media
204.152.184.75
(as of April, 2001).
/etc/exports
file on of the NFS server and resetting its mount daemon (mountd).
(Both of these actions will probably require superuser
privileges on the server.)
Preparing your System for NetBSD installation
Prepare yourself
Take a deep breath.
.txt and .more
versions lack important formatting information that will prevent you from
following the twisted path you must follow. OK, good. Now, print out
this document.
(Open Firmware 1.0.5, Open Firmware 1.1.22, Open Firmware 2.0.x, Open
Firmware 2.4, Open Firmware 3)
Updating your BootROM
(Open Firmware 3)
wdc0:0:1: lost interrupt
problems.
Getting to the Open Firmware Prompt on Newer Models
(Open Firmware 3)
COMMAND-OPTION-O-F
keys (the
COMMAND
key looks like a four-leaf clover or an open apple, and the
OPTION
key may look like a two-way switch with four straight line segments or say
ALT)
until you see the Open Firmware command prompt on your screen:
Apple PowerBook3,1 2.1f1 BootROM built on 01/29/00 at 22:38:07
Copyright 1994-2000 Apple Computer, Inc.
All Rights Reserved
0 > setenv auto-boot? false
Getting to the Open Firmware Prompt on Apple Network Servers
(Open Firmware 1.1.22)
ttya'
device in Open Firmware).
COMMAND-OPTION-O-F
keys (the
COMMAND
key looks like a four-leaf clover or an open apple, and the
OPTION
key may look like a two-way switch with four straight line segments or say
ALT)
until you see some introductory text and the Open Firmware
command prompt on your serial terminal:
0 >
0 > setenv auto-boot? false
Getting to the Open Firmware Prompt on Older Models
(Open Firmware 1.0.5, Open Firmware 2.0.x, Open Firmware 2.4)
Older Open Firmware System Preparation
(Open Firmware 1.0.5, Open Firmware 2.0.x, Open Firmware 2.4)
Apple Performa 4400, 5500, 6500, 54xx, 6400, and 6360,
Motorola Starmax 3000, 4000, 5000, and 5500,
APS Tech M*Power 604e/200,
PowerComputing PowerBase,
Umax Apus 2000, Apus 3000, C500, and C600
Umax S900
Getting to the Open Firmware Prompt (Recommended method using MacOS)
(Open Firmware 1.0.5, Open Firmware 2.0.x, Open Firmware 2.4)
COMMAND-OPTION-P-R
keys during the boot chimes, or if you accidentally boot into
MacOS.
/chaos/control'
(i.e. you have a PowerMacintosh 7300 - 8600 system), there is a chance that
your monitor will not sync. See
http://www.netbsd.org/Ports/macppc/SystemDisk-tutorial/of105patch.html
Open Firmware, 1.0.5
To continue booting the MacOS type:
BYE<return>
To continue booting from the default boot device type:
BOOT<return>
ok
0 >
0 > setenv auto-boot? false
0 > setenv use-nvramrc? false
0 > reset-all
Getting to the Open Firmware Prompt (Harder method using MacOS)
(Open Firmware 1.0.5, Open Firmware 2.0.x, Open Firmware 2.4)
/chaos/control'
(i.e. you have a PowerMacintosh 7300 - 8600 system), there is a chance that
your monitor will not sync. See
http://www.netbsd.org/Ports/macppc/SystemDisk-tutorial/of105patch.html
Open Firmware, 1.0.5
To continue booting the MacOS type:
BYE<return>
To continue booting from the default boot device type:
BOOT<return>
ok
0 >
0 > setenv auto-boot? false
Getting to the Open Firmware Prompt (Without using MacOS)
(Open Firmware 1.0.5, Open Firmware 2.0.x, Open Firmware 2.4)
COMMAND-OPTION-O-F
keys (the
COMMAND
key looks like a four-leaf clover or an open apple, and the
OPTION
key may look like a two-way switch with four straight line segments or say
ALT)
until you see the Open Firmware command prompt on
your screen or serial console:
Open Firmware, 1.0.5
To continue booting the MacOS type:
BYE<return>
To continue booting from the default boot device type:
BOOT<return>
ok
0 >
0 > setenv auto-boot? false
screen'
with the correct
`output-device'
for your model):
0 > setenv output-device screen
0 > setenv input-device kbd
0 > reset-all
/chaos/control'
(i.e. you have a PowerMacintosh 7300 - 8600 system), there is a chance that
your monitor will not sync. See
http://www.netbsd.org/Ports/macppc/SystemDisk-tutorial/of105patch.html
Setting up pre-Open Firmware 3 to boot NetBSD
(Open Firmware 1.0.5, Open Firmware 1.1.22, Open Firmware 2.0.x,
Open Firmware 2.4)
0 > dev /openprom
0 > .properties
name openprom
model Open Firmware, 1.0.5
relative-addressing
ok
0 > setenv load-base 600000
0 > setenv real-base F00000
0 > reset-all
0 > dev enet
0 > .properties
[...]
local-mac-address CCCCCCCC CCCC
[...]
ok
printenv
command:
0 > printenv
little-endian? false false
real-mode? false false
auto-boot? false true
diag-switch? false false
[...]
use-nvramrc? true false
real-base F00000 -1
[...]
load-base 600000 4000
[...]
input-device kbd ttya
output-device /chaos/control ttya
real-base
environment variable to its default value (which prevents
NetBSDfrom booting) if you boot into
MacOS.
Setting up Open Firmware 3 to boot NetBSD
(Open Firmware 3)
0 > dev /openprom
0 > .properties
name openprom
device_type BootROM
model OpenFirmware 3
relative-addressing
supports-bootinfo
ok
0 > dev enet
0 > .properties
[...]
local-mac-address CCCCCCCC CCCC
[...]
printenv
command:
0 > printenv
-------------- Partition: common -------- Signature: 0x70 ---------------
little-endian? false false
real-mode? false false
auto-boot? false true
diag-switch? false false
[...]
use-nvramrc? true false
real-base -1 -1
[...]
input-device keyboard keyboard
output-device screen screen
Available Boot Media
(All Open Firmware versions)
ofwboot.xcf
bootloader and the
`partition zero'
bootloader. In the former case, the user tells Open Firmware to
load
ofwboot.xcf
and it will load the kernel. In the latter case, the user tells Open
Firmware to boot from a particular device, and a primary bootloader
bootxx
is loaded, which then loads the secondary bootloader
ofwboot
which then loads the kernel.
ofwboot.elf
is obsoleted. All users should be using
ofwboot.xcf
instead of
ofwboot.elf
now.
ofwboot or ofwboot.xcf)
(see below for descriptions):
ofwboot
or
ofwboot.xcf
is loaded, it can open the kernel from one of the following sources:
ofwboot.xcf
on a hybrid partition so it can be booted on all Open Firmware
versions. The boot CD-R image also has an ISO9660 filesystem with
an installation kernel and the distribution sets.
Description of bootable media
(All Open Firmware versions)
(Open Firmware 1.0.5, Open Firmware 1.1.22, Open Firmware 2.0.x, Open
Firmware 2.4)
bootxx
located in the Apple Partition Map, which then loads the secondary
bootloader
ofwboot
(functionally identical to
ofwboot.xcf
(q.v.))
which then loads the kernel. This is what
sysinst
will place on your hard drive during the installation procedure.
Additionally, the
NetBSD/macppc
CD-R images and boot floppies use this method to load a kernel from
the floppy's FFS partition or the CD-R's ISO9660 partition.
(Open Firmware 3)
(Open Firmware 2.4, Open Firmware 3)
ofwboot.xcf
from an HFS or HFS+ partition which then loads the kernel from an acceptable
source (such as an FFS partition or an HFS or HFS+ partition). The FFS-based
kernel may be on the boot floppy image
(boot.fs)
located on an HFS or HFS+ partition, or located on a full FFS partition.
ofwboot.xcf.
(All Open Firmware versions)
ofwboot.xcf
bootloader from an MS-DOS filesystem (such as a floppy or Zip disk). It
can then load a
NetBSD
kernel from the same MS-DOS filesystem or elsewhere.
(All Open Firmware versions)
(Open Firmware 1.0.5, Open Firmware 1.1.22, Open Firmware 2.0.x, Open
Firmware 2.4)
ofwboot.xcf
bootloader from an ISO9660 CD-ROM. It can then load a
NetBSD
kernel from the ISO9660 CD-ROM.
(Open Firmware 2.4, Open Firmware 3)
ofwboot.xcf
bootloader from the CD-ROM's HFS filesystem. It can then load a
NetBSD
kernel from the HFS or ISO9660 filesystem.
Partitioning your hard drive for NetBSD
(All Open Firmware versions)
You must use the
NetBSD
installer to partition your disk if you want it to be bootable. With
this release of
NetBSD,
there is no way to dual-boot
MacOS
and
NetBSD
on one hard drive.
(/)
must be on a drive prepared with the
NetBSD
installer, but the partitions not necessary to boot (for example
/usr,
/home,
or
/export)
may be on the same disk as
MacOS.
We recommend using the
NetBSD
installer to partition your disk, but you will not be able to use
partitions on this drive with
MacOS.
You must have at least one disk that was partitioned using a
MacOS
tool before installing
NetBSD
on your system.
ofwboot.xcf.
Your
NetBSD
partitions may either be on this same disk (using the method described
in the rest of this section), or on a separate disk accessible only to
NetBSD.
If you are dedicating an entire disk to
NetBSD,
then your
MacOS
partitioned disk only needs HFS or HFS+ partitions.
/usr (at least 200 MB), /home, /usr/local, or
/usr/pkg.
NetBSD
interprets these partitions as normal
NetBSD-style
partitions.
These partitions are not readable from
MacOS.
Preparing the Bootable Media
The purpose of this section is to prepare the media from which your system
will boot the installer. We'll describe how to put the files in the right
places on your disk(s) or netboot server and prepare it for use on your
system.
(Open Firmware 1.0.5, Open Firmware 1.1.22, Open Firmware 2.0.x, Open
Firmware 2.4)
mount_msdos(8)
on any unix-like machine.
netbsd.ram.gz and ofwboot.xcf
to the floppy.
netbsd.ram.gz to netbsd.gz,
since OpenFirmware can't deal with MS-DOS filenames longer than eight
characters.
(Open Firmware 1.0.5, Open Firmware 1.1.22, Open Firmware 2.0.x, Open
Firmware 2.4)
installation/boot.fs
to a floppy disk
# dd if=boot.fs of=/dev/rfd0a bs=36k
boot.fs
file onto this application, which will change the type and creator to
dimg and ddsk,
which is necessary for DiskCopy to work.
boot.fs
boot.fs
and click
``Open''
(Open Firmware 2.4, Open Firmware 3)
ofwboot.xcf
and the installation kernel
netbsd.ram.gz
at the top level of your Macintosh filesystem. That is, drag the two
icons onto your hard drive icon (not the desktop). Make sure they're
both on the same partition.
(All Open Firmware versions)
pub/NetBSD/iso
directory.
http://www.netbsd.org/mirrors/#iso
ftp://ftp.netbsd.org/pub/NetBSD/packages/pkgsrc/sysutils/cdrecord/README.html
http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html
# cdrecord -v speed=4 dev=/dev/cd1c output.iso
/dev/cd1d).
(Open Firmware 1.0.5, Open Firmware 1.1.22, Open Firmware 2.0.x, Open
Firmware 2.4)
ofwboot.xcf
and the installation kernel
netbsd.ram.gz
at the top level of the CD.
You may also place the
NetBSD1.5.3
distribution sets on the disk.
ftp://ftp.netbsd.org/pub/NetBSD/packages/pkgsrc/sysutils/cdrecord/README.html
http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html
# mkhybrid -o output.iso -a -l -J -r -L /cdsources
# cdrecord -v speed=4 dev=/dev/cd1c output.iso
/dev/cd1d).
installation/ofwboot.xcf
and
installation/netbsd.ram.gz
into the window
(Open Firmware 2.4, Open Firmware 3)
ofwboot.xcf
and the installation kernel
netbsd.ram.gz
at the top level of the CD. Make sure that the
bootloader is present on the HFS partition, and the kernel is on both the
ISO9660 and HFS partitions. You may also place the
NetBSD1.5.3
distribution sets on the ISO9660 partition
(not
only on the HFS partition).
# mkhybrid -o output.iso -hfs -part -a -l -J -r -L /cdsources
# cdrecord -v speed=4 dev=/dev/cd1c output.iso
/dev/cd1d).
ofwboot.xcf
is necessary).
installation/ofwboot.xcf
to the temporary partition
installation/netbsd.ram.gz
into the window. You may also want to drag the
NetBSD1.5.3
distribution sets to this window as well.
(All Open Firmware versions)
CC:CC:CC:CC:CC:CC'
as the MAC address (ethernet hardware address) of your netboot client machine
that you wish to install
NetBSD
on. We use
`192.168.1.10'
as the IP address of your client, and
`client.test.net'
as the name. The server name is
`server.test.net',
and the path on the server to the NFS exported directory is
/export/client/root.
/etc/dhcpd.conf:
ddns-update-style none;
# Do not use any dynamic DNS features
#
allow bootp; # Allow bootp requests, thus the dhcp server
# will act as a bootp server.
#
authoritative; # This is the authoritative DHCP server for this subnet
#
subnet 192.168.1.0 netmask 255.255.255.0 {
# Which network interface the server will
# listen on. The zeros indicate which
# range of addresses are allowed to connect.
}
group {
# Set of parameters common to all clients
# in this "group".
#
option broadcast-address 192.168.1.255;
option domain-name "test.net";
option domain-name-servers dns.test.net;
option routers router.test.net;
option subnet-mask 255.255.255.0;
#
# An individual client.
#
host client.test.net {
hardware ethernet CC:CC:CC:CC:CC:CC;
fixed-address 192.168.1.10;
#
# Name of the host (if the fixed address
# doesn't resolve to a simple name).
#
option host-name "client";
#
# Name of the bootloader or kernel
# to download via tftp.
#
filename "ofwboot.xcf";
#
# The path on the NFS server.
#
option root-path "/export/client/root";
}
}
dhcpd.leases
file exists.
# touch /var/db/dhcpd.leases
# /etc/rc.d/dhcpd restart
installation/ofwboot.xcf
bootloader in
/tftpboot
# cp ofwboot.xcf /tftpboot
/etc/inetd.conf
and make sure that the line starting with
tftp
is uncommented. You will need to
kill -HUP
the
inetd
process to enable tftp if this line was previously commented out. The next
step is to set up NFS exports. Create the directory you are exporting for
the netboot client:
# mkdir -p /export/client/root
/etc/exports
to enable NFS sharing:
/export/client/root -maproot=root client.test.net
# /usr/sbin/mountd
# /usr/sbin/nfsd -tun 4
# mv *.tgz /export/client/root
installation/netbsd.ram.gz).
# gunzip netbsd.ram.gz
# mv netbsd.ram /export/client/root/netbsd
(Open Firmware 1.0.5, Open Firmware 1.1.22, Open Firmware 2.0.x, Open
Firmware 2.4)
installation/boot.fs
to your spare drive, and boot from that drive. For example, you could use
a Zip drive, a Jaz drive, a Compact Flash drive, or even a spare hard
drive. The floppy image has a
`partition zero'
bootloader which ultimately loads the installation kernel from the FFS
filesystem from the disk image.
# dd if=boot.fs of=/dev/rsd0c
/dev/rsd0c
is the
`whole disk'
partition for the drive you will be using. Be certain you have typed this
correctly, as it will erase the disk.
boot.fs
and click
``Open''
Installing the NetBSD System
Open Firmware boot syntax
The syntax of the Open Firmware
boot
command is:
boot boot-device [boot-file] [-as]
boot-device
describes where to find the bootloader,
boot-file
describes where to find the
NetBSD
kernel, and the options specify how you want to boot.
boot-device
to tell Open Firmware where to find
ofwboot(7)
by listing the device, the partition (if it's a disk), and the filename
of the bootloader (if using
ofwboot.xcf).
boot-file
is on the same device and (if it's a disk) partition as the
boot-device
then you can just specify the kernel filename. Otherwise, you need
to specify the full Open Firmware path to the kernel.
device:[partition][,\filename].
Keep in mind for the future that you may be able to have your
boot-device
and
boot-file
on entirely different devices (such as the bootloader netbooted from
enet
and the kernel loaded from a hard drive on the
ultra0
ATA/IDE bus).
0 > dev /
0 > ls
csh(1)).
You can find out
what device aliases Apple created on your machine with the
devalias
command. For example, here are the devaliases on a PowerMacintosh 7300:
0 > devalias
vci0 /chaos@F0000000
pci1 /bandit@F2000000
pci2 /bandit@F4000000
fd /bandit/gc/swim3
kbd /bandit/gc/via-cuda/adb/keyboard
ttya /bandit/gc/escc/ch-a
ttyb /bandit/gc/escc/ch-b
enet /bandit/gc/mace
scsi /bandit/gc/53c94
scsi-int /bandit/gc/mesh
ok
hd |
Note that some of these items are the device itself, and some are a bus. When you only have the devalias to a bus, you need to specify which device on that bus you want to use. You can use the Open Firmware dev and ls commands. For example, here are the devices on the internal SCSI bus of a PowerMacintosh 7300:
0 > dev scsi-int
0 > ls
FF83C850: /sd@0,0
FF83D480: /st@0,0
ok
In this case, Open Firmware seems to be saying there are two devices, both at address zero (one is a SCSI disk `sd@0,0' and the other is a SCSI tape `st@0,0 ).' Unfortunately, older systems will only list the naming convention and not the actual devices currently connected, but that's OK -- we've got more tricks up our sleeve.
If you've got ATA/IDE drives, you have all the device information you need
(since Apple only ever ships drives as
``master''
which is typically something like
ata-disk@0, ATA-Disk@0, atapi-disk, or disk@0 ).
You can find out the devices on your SCSI bus with the show-children command:
0 > dev scsi-int
0 > show-children
Target 0
Unit 0 Disk IBM DCAS-32160 S65A
Target 3
Unit 0 Removable Read Only device SONY CD-ROM CDU-8005 1.0j
ok
Open Firmware calls SCSI IDs
``Target''.
The
``Unit''
number is the Logical Unit Number (LUN). This is almost always zero.
Thus, this PowerMacintosh system has an IBM hard drive (DCAS-32160) at
SCSI ID 0, and a Sony CD-ROM drive (CDU-8005) at SCSI ID 3.
Now, we've got enough information to construct the device name for
Open Firmware. Just stick everything together to describe to Open
Firmware what you want. For example, Open Firmware calls the CD-ROM drive
in this system
scsi-int/sd@3.
To determine if a device is bootable, type:
0 > dev scsi-int/sd@3
0 > words
load write read seek close open
write-blocks read-blocks max-transfer block-size dma-sync dma-map-out
dma-map-in dma-free dma-alloc
ok
If the
word ``open''
is present in the list, then the device is almost certainly bootable.
Next, you need to figure out what partition Open Firmware thinks your
bootloader is located on if you're going to boot from a disk. If you're
using a
``partition zero''
bootloader, the answer is obvious: 0. Thus, your
boot-device
for the
NetBSD/macppc
CD-R image on an Open Firmware 1.0.5 system would be
scsi-int/sd@3:0
since the image has a
`partition zero'
bootloader.
Other situations get a little trickier, as we know of no way to get a partition map from within Open Firmware, and it uses a different numbering scheme than either NetBSD or MacOS 9.x and earlier. See the FAQ for an explanation: http://www.netbsd.org/Ports/macppc/faq.html#partitions
Typically, MS-DOS and ISO9660 formatted disks have their filesystems at partition 1. Typically, Drive Setup formatted disks have their filesystems starting at partition number 9. Often, if you omit the partition number, Open Firmware looks in the first partition it understands holding a valid filesystem.
Open Firmware uses a comma (,) to separate the partition number from the
filename. It uses a backslash (the
\
character) to separate directories. The bootloader uses forward slashes (the
/
character) to separate directories when specifying the
boot-file.
Thus, to specify the top of the
filesystem on a CD-ROM in the example PowerMacintosh 7300 system, you'd
use:
scsi-int/sd@3:,\
Now, to confirm that you and Open Firmware are looking at the same files, you can get a directory listing of the filesystem on your device with the dir command. This command is only useful with filesystems that Open Firmware understands and is able to boot from. On Open Firmware 1.0.5, 1.1.22, and 2.0.x systems, you can use dir on ISO9660 (not hybrid) and MS-DOS filesystems. On Open Firmware 2.4, you can use it on HFS, HFS+, hybrid, ISO9960, and MS-DOS filesystems. On Open Firmware 3, you can use it on HFS, HFS+, hybrid (not pure ISO9660), and MS-DOS filesystems.
0 > dir fd:,\
FINDER .DAT 022 2 2B8
DESKTOP . 022 0 0
RESOURCE.FRK 012 3 0
NETBSD~1.GZ 020 5 1FDFCA
TRASH . 010 B00 0
OFWBOOT .XCF 020 A75 D8F4
ok
NETBSD~1.GZ and OFWBOOT.XCF.
Note that
MacOS
shortened
netbsd.ram.gz to NETBSD~1.GZ
since MS-DOS filesystems can only natively hold 8 characters for the
filename. Keep in mind that Open Firmware is often case-sensitive when it
comes to filenames.
If the
dir
command showed you the files you're looking for, then you've figure out
how to tell Open Firmware to look for your bootloader! In this case, your
boot-device
is
fd:,\OFWBOOT.XCF
and your
boot-file
is
fd:,/NETBSD~1.GZ.
For additional help, see
ofwboot(7)
and the FAQ on topics like how to use the
Open Firmware command environment and how to boot from a device attached
to a PCI card which has Open Firmware support:
http://www.netbsd.org/Ports/macppc/faq.html#ofw-use
http://www.netbsd.org/Ports/macppc/faq.html#boot-pci
Use the Open Firmware
dir
command to get a listing of the files on the floppy. Typically you'll
find filenames like
OFWBOOT.XCF and NETBSD~1.GZ.
0 > boot fd:,\OFWBOOT.XCF NETBSD~1.GZ
You can eject a floppy by typing:
0 > eject fd
The floppy disk has a `partition zero' bootloader.
0 > boot fd:0
You can eject a floppy by typing:
0 > eject fd
You can try the simple form (i.e. that you are booting from ethernet):
0 > boot enet:,\ofwboot.xcf
Or you may be more specific, specifying the bootloader filename and the kernel name:
0 > boot enet:,\ofwboot.xcf enet:,/netbsd.ram
ofwboot.xcf
version 1.2 cannot load compressed kernels. Uncompress them first.
You can try the simple form (i.e. that you are booting from ethernet):
0 > boot enet:0
Or you may be more specific, specifying the bootloader filename and the kernel name:
0 > boot enet:0,\ofwboot.xcf enet:0,/netbsd.ram.gz
Here are some examples of what you might use to boot from CD-ROM (Apple usually sets their CD-ROM drives to SCSI ID 3):
0 > boot scsi-int/sd@3:0 NETBSD.MACPPC
0 > boot scsi/sd@3:0 NETBSD.MACPPC
0 > boot scsi-ext/sd@3:0 NETBSD.MACPPC
0 > boot ata/atapi-disk:0 NETBSD.MACPPC
0 > boot ide1/disk@0:0 NETBSD.MACPPC
0 > boot cd:0 NETBSD.MACPPC
0 > boot cd:,\ofwboot.xcf netbsd.macppc
Open Firmware doesn't understand long filenames (created with the RockRidge and Joliet extensions), so you may need to figure out what your file is called. You should use the Open Firmware dir command to get a listing of the files on your CD.
For instance,
Toast
for
MacOS
creates CDs with long filenames, but uses
MS-DOS
style short names
as well. Instead of referencing
Another thing to note is that you
must
use the same case when specifying the filename to load that Open Firmware
uses.
Also, keep in mind what format your CD-R has to be for your version of
Open Firmware (pure ISO versus hybrid ISO/HFS).
Here are some examples of what you might use to boot from CD-ROM (Apple
usually sets their CD-ROM drives to SCSI ID 3):
You do not specify a file to load, since the
`partition zero'
booloader knows what to do. You would boot such a system if you have dumped
the boot floppy image to your drive, or if you have an already-installed
NetBSD/macppc
system
Remember, that SCSI Zip disks are usually ID 5 or 6.
Internal hard drives are usually SCSI ID 0.
Here are some examples of what you might use to boot from such a drive:
MacOS
drives have several system-level partitions reserved for
MacOS
drivers.
You may find that your first HFS or HFS+ partition might be as high as
partition 9.
You may need to keep trying higher partition numbers until you find the one
that has your bootloader. If you're running
MacOS X
you can run the following command to print out the partition table on your
drive:
If you are confused by the various partition numbering schemes, see the
explanation in the FAQ
http://www.netbsd.org/Ports/macppc/faq.html#partitions
You should use the Open Firmware
dir
command to get a directory listing of the files on your hard drive.
If bootloader is on a different partition from the
NetBSD
kernel, you will need to specify where to find the kernel.
Remember, that SCSI Zip disks are usually ID 5 or 6. Internal hard drives
are usually SCSI ID 0.
Here are some examples of what you might use to boot the installer kernel
located on an HFS or HFS+ partition:
netbsd-GENERIC
you would need to open
NETBSD-G.ENE
The
mkisofs
and
mkhybrid
programs have a similar problem. For them,
netbsd.ram.gz
becomes
NETBSD_RAM.GZ.
0 > boot scsi-int/sd@3:,\OFWBOOT.XCF NETBSD.MACPPC
0 > boot scsi/sd@3:,\OFWBOOT.XCF NETBSD.MACPPC
0 > boot scsi-ext/sd@3:,\OFWBOOT.XCF NETBSD.MACPPC
0 > boot ata/atapi-disk:,\OFWBOOT.XCF NETBSD.MACPPC
0 > boot ide1/disk@0:,\OFWBOOT.XCF NETBSD.MACPPC
0 > boot cd:,\ofwboot.xcf netbsd.macppc
(Open Firmware 1.0.5, Open Firmware 1.1.22, Open Firmware 2.0.x, Open
Firmware 2.4)
0 > boot scsi-int/sd@0:0
0 > boot scsi/sd@0:0
0 > boot scsi-ext/sd@0:0
0 > boot ata/ata-disk@0:0
0 > boot ata/ATA-Disk@0:0
0 > boot ide0/disk@0:0
0 > boot zip:0
(Open Firmware 2.4, Open Firmware 3)
% sudo pdisk /dev/disk0 -dump
0 > boot scsi/sd@0:9,\ofwboot.xcf netbsd.ram.gz
0 > boot ide0/disk@0:10,\ofwboot.xcf netbsd.ram.gz
0 > boot hd:9,\ofwboot.xcf netbsd.ram.gz
0 > boot ultra1:9,ofwboot.xcf netbsd.ram.gz
Apple PowerBook3,1 2.1f1 BootROM built on 01/29/00 at 22:38:07
Copyright 1994-2000 Apple Computer, Inc.
All Rights Reserved
Welcome to Open Firmware.
To continue booting, type "mac-boot" and press return.
To shut down, type "shut-down" and press return.
ok
0 > boot enet:,\ofwboot.xcf netbsd.ram.gz
loading XCOFF
tsize=C280 dsize=14AC bsize=2620 entry=600000
SECTIONS:
.text 00600000 00600000 0000C280 000000E0
.data 0060D000 0060D000 000014AC 0000C360
.bss 0060E4B0 0060E4B0 00002620 00000000
loading .text, done..
loading .data, done..
clearing .bss, done..
>> NetBSD/macppc OpenFirmware Boot, Revision 1.3
>> (tsubai@mint.iri.co.jp, Sun Nov 26 01:41:27 JST 2000)
1701508+177748 [100+68176+55886]=0x1e9468
start=0x100000
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001
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.2 (INSTALL) #0: Thu Mar 15 00:52:56 PST 2001
mw@al:/usr/src/sys/arch/macppc/compile/INSTALL
total memory = 192 MB
avail memory = 172 MB
using 2483 buffers containing 9932 KB of memory
[...]
erase ^H, werase ^W, kill ^U, intr ^C, status ^T
Terminal type? [vt100]
Erase is backspace.
(I)nstall, (S)hell or (H)alt ?
If your system is a PowerBook, NetBSD may have turned down the brightness of the backlight. Use the buttons to turn your brightness back up.
Otherwise, you need a serial console. See the section entitled Getting to the Open Firmware Prompt on Older Models
This means that your system is trying to boot
MacOS.
You might get to this state if you didn't properly enter Open Firmware, or if
your Open Firmware boot command is misformed.
If you typed a bad boot command, Open Firmware tries to boot from the
value stored in the
The grey screen with the icon is generated by the MacOS ROM. A flashing
question-mark or broken folder means that your machine is looking for a
bootable MacOS filesystem, but can't find one. A happy face means it's
trying to boot MacOS.
The boot floppy does not have a bootable MacOS filesystem, it has a
bootable NetBSD filesystem.
Reboot, re-enter Open Firmware and check your syntax carefully.
If you have a PowerMacintosh 7300 through 8600, then you need to read the
section on System Disk and the patches it applies. See the section
entitled
Getting to the Open Firmware Prompt on Older Models
If you have a Twentieth Anniversary Macintosh, Open Firmware does not work
with the internal display, you will need to set up a serial console.
This is a general message from Open Firmware to the effect that it had
trouble loading a file.
If your machine is Open Firmware version 1.0.5, 2.0.x, or 2.4, this error
does sometimes appear randomly. You might try the boot command a second time
(this is known to work on some models). It's also an indication that
either your floppy disk is bad, or the floppy drive is bad. Try doing a
low-level format on the floppy, re-copy the files, and try again.
There are several models that cannot be booted while using the on-board
video and keyboard. Try using a serial console.
This is a general message from Open Firmware to the effect that it failed
to allocate some memory or memory is messed up.
First, make sure you have the Open Firmware variable
Do not change
If you tried one boot command and it failed, then you tried a second and
got the
Contradictorily, if your machine is Open Firmware version 1.0.5, 2.0.x or
2.4, this error does sometimes appear randomly. You might try the boot
command a second time (this is known to work on some models).
There are several models that cannot be booted while using the on-board
video and keyboard. Try using a serial console.
Open Firmware either can't open the device you specified (because it is not
present or the device path is mistyped) or the file you specified. Check your
typing and check to make sure that the media has the files you think it has.
Use the Open Firmware
dir
command to verify that the file(s) you tried accessing are really there.
This is a general Open Firmware error message indicating that the filename
you tried to open either doesn't exist or is in the wrong format. For
Open Firmware 1 and 2 machines, it must be an XCOFF file (such as
If you're trying to boot an Open Firmware 1.0.5, 1.1.22, or 2.0.x system,
this probably means that your media (i.e. hard drive or CD-ROM) has an HFS
filesystem on it (such as a hybrid CD-R or a hard drive with MacOS
partitions).
Either the server's TFTP server isn't running, or you're using a model
with Open Firmware 1.0.5 and not specifying the location of the
bootloader. Unfortunately, on the early models,
You forgot to set
Make sure you have the Open Firmware variable
Do not set
Actually, this can have many causes. The most likely is a keyboard
problem. First, try
plugging the USB keyboard directly into the computer (i.e. not through a
hub) and unplugging the mouse.
This is also a known problem on some PowerMacintosh G3 (Blue and
White) and iMac (Bondi Blue) machines. If you have a
PowerMacintosh G3 (Blue and White) with this problem, then you can try the
following procedure:
The USB will be usable at this point and you can use the system. You'll
notice that the ADB is dead even before you unplugged it. Also you MUST
boot without the USB installed or this won't work.
Alternatively, much as it pains us to say this,
NetBSD
1.4.3 works fine on both the iMac (Bondi Blue) and the PowerMacintosh G3
(Blue and White) models and does not have this USB keyboard problem.
boot-device
variable, whose default value is the MacOS ROM.
DEFAULT CATCH!''
CLAIM failed''
load-base
set correctly. If your system is Open Firmware version 1.0.5, 1.1.22,
2.0.x, or 2.4, see the section above on
Setting up pre-Open Firmware 3 to boot NetBSD
load-base
on an Open Firmware 3 system.
CLAIM failed
message, then this is an indication that you should
reboot between attempts. Use the Open Firmware
reset-all
command.
can't OPEN''
unrecognized Client Program formatstate not valid''
ofwboot.xcf)
and for Open Firmware 3 machines, it must be either XCOFF or ELF (such as
a kernel). Make sure that you have use binary mode to FTP the files, and
that they are properly uncompressed.
bad partition number, using 0no bootable HFS partition''
TFTP timeout''
ofwboot.xcf
gets confused and doesn't work right unless you load it explicitly from the
boot-device,
even if the bootp or DHCP server provides the correct information. You
need to boot with a command like:
0 > boot enet:,\ofwboot.xcf
real-base
in Open Firmware or it got erased by your booting into
MacOS.
real-base
set correctly. If your system is Open Firmware version 1.0.5, 1.1.22,
2.0.x, or 2.4, see the section above on
Setting up pre-Open Firmware 3 to boot NetBSD
real-base
on an Open Firmware 3 system.
Using sysinst, installing NetBSD is a relatively easy process. You still should read this document and have it in hand when doing the installation process. This document tries to be a good guideline for the installation and as such covers many details to be completed. Do not let this discourage you, the install program is not hard to use.
The following is a walk-through of the steps you will take while
getting
NetBSD
installed on your hard disk.
sysinst
is a menu driven
installation system that allows for some freedom in doing the
installation. Sometimes, questions will be asked and in many cases
the default answer will be displayed in brackets
(``[ ]'')
after the question. If you wish to stop the installation, you may press
CONTROL-C
at any time, but if you do, you'll have to begin the installation
process again from scratch, by running the
/sysinst
program from the command prompt, you do not need to reboot.
First, let's describe a quick install. The other sections of this document go into the installation procedure in more detail, but you may find that you do not need this. If you want detailed instructions, skip to section 3. This section describes a basic installation, using a CD-ROM install as an example.
.***********************************************.
* NetBSD-1.5.3 Install System *
* *
*>a: Install NetBSD to hard disk *
* b: Upgrade NetBSD on a hard disk *
* c: Re-install sets or install additional sets *
* d: Reboot the computer *
* e: Utility menu *
* x: Exit Install System *
.***********************************************.
root,
and set a password for that account. You are also
advised to edit the file
/etc/rc.conf
to match your system needs.
/usr/X11R6/lib/X11/doc.
Further information can be found on
http://www.netbsd.org/Ports/macppc/x11.html
Boot the system as described in the previous section.
You may want to read the
boot messages, to notice your disk's name and capacity. Its name
will be something like
sd0
or
wd0
and the geometry will be
printed on a line that begins with its name. As mentioned above,
you may need your disk's geometry when creating
NetBSD's
partitions.
You will also need to know the name, to tell
sysinst
on which disk
to install.
The most important thing to know is that
wd0
is
NetBSD's
name for your first IDE disk,
wd1
the second, etc.
sd0
is your first SCSI disk,
sd1
the second, etc.
Once NetBSD has booted and printed all the boot messages, you will be presented with a welcome message and a main menu. It will also include instructions for using the menus.
If you will not use network operation during the installation, but you do want your machine to be configured for networking once it is installed, you should first go to the Utility menu , and select the Configure network option. If you only want to temporarily use networking during the installation, you can specify these parameters later. If you are not using the Domain Name System (DNS), you can give an empty response in reply to answers relating to this.
Skip this step if you are installing NetBSD onto a dedicated drive.
Go to the
Utility Menu,
and select the
Run /bin/sh
option which will give you a shell prompt. From this shell prompt, you
will do some of the steps that the normal install procedure
runs automatically. Unfortunately, at the moment, our install tools
aren't smart enough to deal with drives shared with
MacOS
and will overwrite important information describing your partitions.
You may need to type one of the following commands to get your delete key
to work properly, depending on your keyboard:
Type the following command (replacing
This will print out the partition info that was generated by Drive
Setup. Note that, as discussed above in the
Partitioning your hard drive for NetBSD
section, your
A/UX Root
typically is the first partition
(a)
and your
A/UX Swap
typically is the second partition
(b).
You may also find that your
A/UX User
partition is the seventh partition
(g).
For example:
Now, you need to create filesystems on the partitions that
NetBSD
will be using.
Do not modify any partitions labeled
Run the
newfs
command on the
Now you need to mount your destination root partition:
Make an
If you mess up while typing, you can press
Great, now create the mountpoints for the filesystems you listed in the
Clean up and return to
sysinst:
To start the
installation onto a dedicated
NetBSD
drive,
select
Install NetBSD to hard disk
from the main menu.
To start the installation onto a drive which will
also be used with
MacOS,
select
Re-install sets or install additional sets
from the main menu.
The first thing is to identify the disk on which you want to
install
NetBSD.
sysinst
will report a list of disks it finds
and ask you for your selection. Depending on how many disks
are found, you may get a different message. You should see
disk names like
If
sysinst
reports
You can skip a few steps, down to
`Getting the distribution sets',
if you are installing onto a drive that will be used with
MacOS
(i.e. you selected
Re-install sets or install additional sets
from the main menu).
The partition table of the
NetBSD
part of a disk is called a
disklabel.
In actuality,
NetBSD/macppc
uses an Apple Partition Map. The installer creates something like a real
Apple Partition Map, but it is not compatible with
MacOS,
which is one of the reasons why you cannot use this installer to partition
a disk that can be used with
MacOS.
There are 3 layouts for the
NetBSD
part of the disk that you can pick from:
Standard, Standard with X
and
Custom.
The first two use a set of default
values (that you can change) suitable for a normal
installation, possibly including X. The last option
lets you specify everything yourself.
You will be presented with the current layout of the
NetBSD
disklabel, and given a chance to change it.
For each partition, you can set the type, offset and size,
block and fragment size, and the mount point. The type
that
NetBSD
uses for normal file storage is called
4.2BSD.
A swap partition has a special type called
swap.
Some partitions in the disklabel have a fixed purpose.
You will then be asked to name your disk's disklabel. The
default response is
mydisk.
For most purposes this will be OK.
If you choose to name it something different, make sure the name
is a single word and contains no special characters. You don't
need to remember this name.
You are now at the point of no return.
Nothing has been
written to your disk yet, but if you confirm that you want to
install
NetBSD,
your hard drive will be modified. If you are
sure you want to proceed, enter
The install program will now label your disk and make the file
systems you specified. The file systems will be initialized to
contain
NetBSD
bootstrapping binaries and configuration files.
You will see messages on your screen from the various
NetBSD
disk preparation tools that are running. There should be no
errors in this section of the installation. If there are,
restart from the beginning of the installation process.
Otherwise, you can continue the installation program
after pressing the return key.
The
NetBSD
distribution consists of a number of
sets,
that come in the form of gzipped tarfiles. A few sets must be
installed for a working system, others are optional. At this
point of the installation, you will be presented with a menu
which enables you to choose from one of the following methods
of installing the sets. Some of these methods will first
load the sets on your hard disk, others will extract the sets
directly.
For all these methods, the first step is making the sets
available for extraction, and then do the actual installation.
The sets can be made available in a few different ways. The
following sections describe each of those methods. After
reading the one about the method you will be using, you
can continue to section labeled
`Extracting the distribution sets'.
To be able to install using ftp, you first need to configure
your network setup, if you haven't already at the start of
the install procedure.
sysinst
will do this for you, asking you
to provide some data, like IP address, hostname, etc. If you
do not have name service set up for the machine that you
are installing on, you can just press
You will also be asked to specify the host that you want
to transfer the sets from, the directory on that host,
and the account name and password used to log into that
host using ftp. If you did not set up DNS when answering
the questions to configure networking, you will need to
specify an IP address instead of a hostname for the ftp
server.
sysinst
will proceed to transfer all the default set files
from the remote site to your hard disk.
To be able to install using NFS, you first need to configure
your network setup, if you haven't already at the start of
the install procedure.
sysinst
will do this for you, asking you
to provide some data, like IP address, hostname, etc. If you
do not have name service set up for the machine that you
are installing on, you can just press
You will also be asked to specify the host that you want
to transfer the sets from, and the directory on that host
that the files are in. This directory should be mountable
by the machine you are installing on, i.e. correctly
exported to your machine.
If you did not set up DNS when answering the questions to
configure networking, you will need to specify an IP address
instead of a hostname for the NFS server.
When installing from a CD-ROM, you will be asked to specify
the device name for your CD-ROM player
(usually
sysinst
will then check if the files are indeed available
in the specified location, and proceed to the actual
extraction of the sets.
In order to install from a local file system, you will
need to specify the device that the file system resides
on
(for example
This option assumes that you have already done some preparation
yourself. The sets should be located in a directory on a
file system that is already accessible.
sysinst
will ask you
for the name of this directory.
After the install sets containing the
NetBSD
distribution
have been made available, you can either extract all the
sets (a full installation), or only extract sets that
you have selected. In the latter case, you will be shown the
currently selected sets, and given the opportunity to select
the sets you want. Some sets always need to be installed
(kern, base and etc)
they will not be shown in this selection menu.
Before extraction begins, you can elect to watch the files being
extracted; the name of each file that is extracted will be shown.
This can slow down the installation process considerably, especially
on machines with slow graphics consoles or serial consoles.
If you are installing using the
Re-install sets or install additional sets
option, then you will need to create the device nodes in
If you are installing using the
Re-install sets or install additional sets
option, then you will need to create the device nodes in
Go to the main installation menu, and select
Utility menu
and then select the
Run /bin/sh
option, which will give you a shell prompt.
You may need to type one of the following commands to get your delete key
to work properly, depending on your keyboard:
Type the following command (replacing
Congratulations, you have successfully installed
NetBSD1.5.3.
# stty erase '^h'
# stty erase '^?'
wd0
with the name of your destination hard drive):
# disklabel wd0
# disklabel wd0
[...]
# size offset fstype [fsize bsize cpg/sgs]
a: 426613 837432 4.2BSD 0 0 0 # (Cyl. 1622*- 2449*)
b: 204800 632632 swap # (Cyl. 1226*- 1622*)
c: 2134305 0 unused 0 0 # (Cyl. 0 - 4136*)
d: 426616 1216 HFS # (Cyl. 2*- 829*)
e: 204800 427832 HFS # (Cyl. 829*- 1226*)
f: 21 2134284 unknown # (Cyl. 4136*- 4136*)
g: 870239 1264045 4.2BSD 0 0 0 # (Cyl. 2449*- 4136*)
disklabel: boot block size 0
disklabel: super block size 0
HFS or unknown.
The partitions you will be using have their
fstype
listed as
4.2BSD.
4.2BSD
partitions:
You can ignore the
# newfs /dev/wd0a
newfs: /dev/sd1a: not a character-special device
Warning: 120 sector(s) in last cylinder unallocated
/dev/sd1a: 426612 sectors in 827 cylinders of 4 tracks, 129 sectors
208.3MB in 52 cyl groups (16 c/g, 4.03MB/g, 1024 i/g)
super-block backups (for fsck -b #) at:
32, 8432, 16832, 25232, 33056, 41456, 49856, 58256, 66080,
74480, 82880, 91280, 99104, 107504, 115904, 124304, 132128, 140528,
148928, 157328, 165152, 173552, 181952, 190352, 198176, 206576, 214976,
223376, 231200, 239600, 248000, 256400, 264224, 272624, 281024, 289424,
297248, 305648, 314048, 322448, 330272, 338672, 347072, 355472, 363296,
371696, 380096, 388496, 396320, 404720, 413120, 421520,
newfs: ioctl (WDINFO): Invalid argument
newfs: /dev/sd1a: can't rewrite disk label
`not a character-special device',
`sector(s) in last cylinder unallocated',
`ioctl (WDINFO): Invalid argument',
and
`can't rewrite disk label'
warnings.
# mount /dev/wd0a /mnt
fstab
file for your new system (right now, you only really need to include
/,
/usr,
and
swap ),
for example:
# mkdir /mnt/etc
# cat > /mnt/etc/fstab
/dev/wd0a / ffs rw 1 1
/dev/wd0b none swap sw 0 0
/dev/wd0g /usr ffs rw 1 2
CONTROL-U
to erase everything on the current line, or
CONTROL-C
to cancel the file creation, so you can start over.
fstab:
# mkdir /mnt/usr
# cd /;umount /mnt
# exit
wd0,
wd1,
sd0
or
sd1.
I can not find any hard disk for use by NetBSD
or the drive you wish to install onto is missing, then you should look at
the FAQ entry
http://www.netbsd.org/Ports/macppc/faq.html#nodisk
a/),
bcd-hg
is the partition mounted on
/usr,
but this is historical practice and not a fixed value.
yes
at the prompt.
ofwboot.xcf
on an HFS or HFS+ partition.
RETURN
in answer to these questions, and DNS will not be used.
RETURN
in answer to these questions, and DNS will not be used.
cd0),
and the directory name on the CD-ROM where the distribution files are.
sd1e)
the type of the file system,
and the directory on the specified file system where the sets are located.
sysinst
will then check if it
can indeed access the sets at that location.
Remember,
NetBSD/macppc
doesn't grok HFS or HFS+ partitions
/dev,
otherwise,
all the necessary device node files will be created. If you have already
configured networking, you will be asked if you want to
use this configuration for normal operation. If so, these
values will be installed in the network configuration files.
The next menu will allow you to select the time zone that you're in,
to make sure your clock has the right offset from UTC.
Finally you can set a password for the "root" account, to prevent
the machine coming up without access restrictions.
/dev
now. Otherwise, skip this step.
# stty erase '^h'
# stty erase '^?'
wd0a
with the partition name of your destination root partition):
Now you need to mount your destination root partition:
# mount /dev/wd0a /mnt
# cd /mnt/dev
# sh MAKEDEV all
# cd /;umount /mnt
# exit
0 > setenv auto-boot? true
0 > setenv boot-device scsi/sd@0:0
0 > setenv boot-file netbsd
0 > reset-all
The last command resets the system so that these settings are stored. Replace scsi/sd@0:0 with the actual device you will be booting from. If you find that your system tries booting before your hard drive has spun up, you may need to also enter something like:
0 > setenv boot-command begin ['] boot catch 1000 ms cr again
If you are not using a `partition zero' style boot scheme, then you can still plug in all the information you need:
0 > setenv auto-boot? true
0 > setenv boot-device ide0/disk@0:8,\ofwboot.xcf
0 > setenv boot-file ide0/disk@0:13,/netbsd
0 > reset-all
Once you've got the operating system running, there are a few things you need to do in order to bring the system into a properly configured state, with the most important ones described below.
/etc/rc.conf
If you or the installation software haven't done any configuration of
/etc/rc.conf
(sysinst
usually will),
the system will drop you into single user mode on first reboot with the
message
/etc/rc.conf is not configured. Multiuser boot aborted.
and with the root file system
(/)
mounted read-write. When the system
asks you to choose a shell, simply press
RETURN
to get to a
/bin/sh
prompt. If you are asked for a terminal type, respond with
vt100
(or whatever is appropriate for your terminal type)
and press
RETURN.
You may need to type one of the following commands to get your delete key
to work properly, depending on your keyboard:
# stty erase '^h'
# stty erase '^?'
At this point, you need to configure at least
one file in the
/etc
directory. You will need to mount your root filesystem read/write with:
# /sbin/mount -u -w /
Change to the
/etc
directory and take a look at the
/etc/rc.conf
file. Modify it to your tastes, making sure that you set
rc_configured=YES
so that your changes will be enabled and a multi-user boot can
proceed.
Default values for the various programs can be found in
/etc/defaults/rc.conf,
where some in-line documentation may be found.
More complete documentation can be found in
rc.conf(5).
If your
/usr
directory is on a separate partition and you do not know how to use
ed,
you will have to mount your
/usr
partition to gain access to
ex
or
vi.
Do the following:
# mount /usr
# export TERM=vt100
If you have
/var
on a separate partition, you need to repeat
that step for it. After that, you can edit
/etc/rc.conf
with
vi(1).
When you have finished, type
exit
at the prompt to
leave the single-user shell and continue with the multi-user boot.
Other values that need to be set in
/etc/rc.conf
for a networked environment are
hostname and possibly
defaultroute,
furthermore add an
ifconfig_int
for your
<int>
network interface,
where your on-board interfaces may be one of
mc0, bm0, de0 or gm0.
For example:
ifconfig_mc0="inet 123.45.67.89 netmask 255.255.255.0"
or, if you have
myname.my.dom
in
/etc/hosts:
ifconfig_mc0="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.
Other files in
/etc
that may require modification or setting up include
/etc/mailer.conf,
/etc/nsswitch.conf,
and
/etc/wscons.conf.
After reboot, you can log in as
root
at the login prompt. Unless you've set a password in
sysinst,
there
is no initial password. If you're using the machine in a
networked environment, you should create an account for yourself
(see below) and protect it and the
``root''
account with good passwords.
Unless you have connected an unusual terminal device as the console
you can just press
RETURN
when it prompts for
Terminal type? [...].
Use the
useradd(8)
command to add accounts to your system,
do not
edit
/etc/passwd
directly. See
useradd(8)
for more information on how to add a new user to the system.
If you have installed the X Window System, look at the files in
/usr/X11R6/lib/X11/doc
for information.
Also, you may want to read through the
NetBSD/macppc
X11R6 FAQ.
http://www.netbsd.org/Ports/macppc/x11.html
Don't forget to add
/usr/X11R6/bin
to your path in your shell's dot file so that you have access to the X binaries.
If you wish to install any of the software freely available for UNIX-like systems you are strongly advised to first check the NetBSD package system. This automatically handles any changes necessary to make the software run on NetBSD, retrieval and installation of any other packages on which the software may depend, and simplifies installation (and deinstallation), both from source and precompiled binaries.
1.5.3/macppc/All
subdir. You can install them with the following commands:
# export PKG_PATH=\ ftp://ftp.netbsd.org/pub/NetBSD/packages/1.5.3/macppc/All\;\ ftp://ftp.netbsd.org/pub/NetBSD/packages/1.5/macppc/All # pkg_add -v tcsh # pkg_add -v cvs # pkg_add -v apache # pkg_add -v perl ...
The above commands will install the tcsh shell, the CVS source code management system, the Apache web server and the perl programming language as well as all the packages they depend on.
/usr/pkgsrc
(though other locations work fine), with the commands:
# mkdir /usr/pkgsrc
#( cd /usr/pkgsrc ; tar -zxpf - ) < pkgsrc.tar.gz
After extracting, then see the
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. Don't forget to run
newaliases(1)
afterwards.
/etc/mail/sendmail.cf
file will almost definitely need to be adjusted;
files aiding in this can be found in
/usr/share/sendmail.
See the
/etc/rc.local
to run any local daemons you use.
/etc
files are documented in section 5 of the manual; so just invoking
# man 5 filename
is likely to give you more information on these files.
The upgrade to NetBSD1.5.3 is a binary upgrade; it can be quite difficult to advance to a later version by recompiling from source due primarily to interdependencies in the various components.
To do the upgrade, you must boot from the installer kernel using one of
the methods described above.
You must also have at least the
base
and
kern
binary distribution sets available, so that you can upgrade with them,
using one of the upgrade methods described above. Finally, you must
have sufficient disk space available to install the new binaries.
Since the old binaries are being overwritten in place, you only need
space for the new binaries, which weren't previously on the system.
If you have a few megabytes free on each of your root
(/)
and
/usr
partitions, you should have enough space.
Since upgrading involves replacing the boot blocks on your
NetBSD
partition, the kernel, and most of the system binaries, it has the
potential to cause data loss. You are strongly advised to
back up any important data on your disk,
whether on the
NetBSD
partition or on
another operating system's partition, before beginning the upgrade
process.
Since installation of the bootloader will prevent
MacOS
from using the disk and will prevent Open Firmware 3 machines from
booting, there is an option to bypass this step. Make sure you know
whether or not to install the bootloader.
The upgrade procedure using the
sysinst
tool is similar to an installation, but without the hard disk partitioning.
The original
After a new kernel has been copied to your hard disk, your
machine is a complete
NetBSD1.5.3
system. However, that
doesn't mean that you're finished with the upgrade process.
You will probably want to update the set of device
nodes you have in
You must also deal with certain changes in the formats of
some of the configuration files. The most notable change is
that the options given to many of the file systems in
Finally, you will want to delete old binaries that were part
of the version of
NetBSD
that you upgraded from and have since been removed from the
NetBSD
distribution.
Users upgrading from previous versions of
NetBSD
may wish to bear the
following problems and compatibility issues in mind when upgrading to
NetBSD1.5.3.
Prior to
NetBSD1.5,
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
majordomo@netbsd.org.
To get help on using the mailing
list server, send mail to that address with an empty body, and it will
reply with instructions.
There are various mailing lists set up to deal with comments and
questions about this release. Please send comments to:
netbsd-comments@netbsd.org.
To report bugs, use the
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:
netbsd-help@netbsd.org.
As a favor, please avoid mailing huge documents or files to these
mailing lists. Instead, put the material you would have sent up
for FTP or WWW somewhere, then mail the appropriate list about it, or, if
you'd rather not do that, mail the list saying you'll send the data
to those who want it.
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)
/etc
directory is renamed to
/etc.old,
and no attempt is made to merge any of the previous configuration into
the new system except that the previous
/etc/fstab
file is copied into the new configuration.
Getting the binary
sets is done in the same manner as the installation procedure;
refer to the installation part of the document
for how to do this. Also, some sanity checks are done, i.e.
file systems are checked before unpacking the sets.
/dev.
If you've changed the contents of
/dev
by hand, you will need to be careful about this, but if
not, you can just cd into
/dev,
and run the command:
# sh MAKEDEV all
/etc/fstab
have changed, and some of the file
systems have changed names. To find out what the new options
are, it's suggested that you read the manual page
for the file system's mount commands, for example
mount_nfs(8)
for NFS.
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; 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 upgrade from NetBSD 1.4 or prior
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:
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
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
Reinoud Zandijk
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.
Precedence Technologies Ltd
Salient Systems Inc.
VMC Harald Frank, Germany
Warped Communications, Inc.
Whitecross Database Systems Ltd.
We are...
| The NetBSD core group: | ||||||||
| 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 | ||||||
| Simon Burge | simonb@netbsd.org | pmax | ||||||
| Jeremy Cooper | jeremy@netbsd.org | sun3x | ||||||
| Matt Fredette | fredette@netbsd.org | sun2 | ||||||
| Ross Harvey | ross@netbsd.org | alpha | ||||||
| Jun-ichiro itojun Hagino | itojun@netbsd.org | sh3 | ||||||
| Ben Harris | bjh21@netbsd.org | arm26 | ||||||
| Eduardo Horvath | eeh@netbsd.org | sparc64 | ||||||
| Darrin Jewell | dbj@netbsd.org | next68k | ||||||
| Søren Jørvang | soren@netbsd.org | cobalt | ||||||
| Søren Jørvang | soren@netbsd.org | sgimips | ||||||
| Wayne Knowles | wdk@netbsd.org | mipsco | ||||||
| Paul Kranenburg | pk@netbsd.org | sparc | ||||||
| Anders Magnusson | ragge@netbsd.org | vax | ||||||
| Minoura Makoto | minoura@netbsd.org | x68k | ||||||
| Phil Nelson | phil@netbsd.org | pc532 | ||||||
| Tohru Nishimura | nisimura@netbsd.org | luna68k | ||||||
| NONAKA Kimihiro | nonaka@netbsd.org | prep | ||||||
| Scott Reynolds | scottr@netbsd.org | mac68k | ||||||
| Kazuki Sakamoto | sakamoto@netbsd.org | bebox | ||||||
| Noriyuki Soda | soda@netbsd.org | arc | ||||||
| Wolfgang Solfrank | ws@netbsd.org | ofppc | ||||||
| Ignatios Souvatzis | is@netbsd.org | amiga | ||||||
| Jonathan Stone | jonathan@netbsd.org | pmax | ||||||
| Shin Takemura | takemura@netbsd.org | hpcmips | ||||||
| Jason Thorpe | thorpej@netbsd.org | alpha | ||||||
| Jason Thorpe | thorpej@netbsd.org | hp300 | ||||||
| Tsubai Masanari | tsubai@netbsd.org | macppc | ||||||
| Tsubai Masanari | tsubai@netbsd.org | newsmips | ||||||
| Izumi Tsutsui | tsutsui@netbsd.org | news68k | ||||||
| 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.5.3 Release Engineering team: | ||||||||
| Chris G. Demetriou | cgd@netbsd.org | |||||||
| Håvard Eidnes | he@netbsd.org | |||||||
| Ted Lemon | mellon@netbsd.org | |||||||
| Perry Metzger | perry@netbsd.org | |||||||
| Curt Sampson | cjs@netbsd.org | |||||||
| Jason Thorpe | thorpej@netbsd.org | |||||||
| Todd Vierling | tv@netbsd.org | |||||||
|
| ||||||||
| Developers and other contributors: | ||||||||
| Nathan Ahlstrom | nra@NetBSD.org | |||||||
| Steve Allen | wormey@netbsd.org | |||||||
| Julian Assange | proff@netbsd.org | |||||||
| Lennart Augustsson | augustss@netbsd.org | |||||||
| Christoph Badura | bad@netbsd.org | |||||||
| Bang Jun-Young | junyoung@netbsd.org | |||||||
| Dieter Baron | dillo@netbsd.org | |||||||
| Robert V. Baron | rvb@netbsd.org | |||||||
| Jason Beegan | jtb@netbsd.org | |||||||
| Erik Berls | cyber@netbsd.org | |||||||
| John Birrell | jb@netbsd.org | |||||||
| Mason Loring Bliss | mason@netbsd.org | |||||||
| Rafal Boni | rafal@netbsd.org | |||||||
| Manuel Bouyer | bouyer@netbsd.org | |||||||
| John Brezak | brezak@netbsd.org | |||||||
| Allen Briggs | briggs@netbsd.org | |||||||
| Aaron Brown | abrown@netbsd.org | |||||||
| Andrew Brown | atatat@netbsd.org | |||||||
| David Brownlee | abs@netbsd.org | |||||||
| Frederick Bruckman | fredb@netbsd.org | |||||||
| Jon Buller | jonb@netbsd.org | |||||||
| Dave Burgess | burgess@cynjut.infonet.net | |||||||
| Robert Byrnes | byrnes@netbsd.org | |||||||
| D'Arcy J.M. Cain | darcy@netbsd.org | |||||||
| Dave Carrel | carrel@netbsd.org | |||||||
| James Chacon | jmc@netbsd.org | |||||||
| Bill Coldwell | billc@netbsd.org | |||||||
| Julian Coleman | jdc@netbsd.org | |||||||
| Chuck Cranor | chuck@netbsd.org | |||||||
| Alistair Crooks | agc@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 | |||||||
| Tracy Di Marco White | gendalia@netbsd.org | |||||||
| Jaromír Dolecek | jdolecek@netbsd.org | |||||||
| Andy Doran | ad@netbsd.org | |||||||
| Roland Dowdeswell | elric@netbsd.org | |||||||
| Emmanuel Dreyfus | manu@netbsd.org | |||||||
| Matthias Drochner | drochner@netbsd.org | |||||||
| Jun Ebihara | jun@netbsd.org | |||||||
| Håvard Eidnes | he@netbsd.org | |||||||
| Stoned Elipot | seb@netbsd.org | |||||||
| Enami Tsugutomo | enami@netbsd.org | |||||||
| Bernd Ernesti | veego@netbsd.org | |||||||
| Erik Fair | fair@netbsd.org | |||||||
| Hubert Feyrer | hubertf@netbsd.org | |||||||
| Jason R. Fink | jrf@netbsd.org | |||||||
| Thorsten Frueauf | frueauf@netbsd.org | |||||||
| Castor Fu | castor@netbsd.org | |||||||
| Ichiro Fukuhara | ichiro@netbsd.org | |||||||
| Brian R. Gaeke | brg@dgate.org | |||||||
| Thomas Gerner | thomas@netbsd.org | |||||||
| Simon J. Gerraty | sjg@netbsd.org | |||||||
| Justin Gibbs | gibbs@netbsd.org | |||||||
| Adam Glass | glass@netbsd.org | |||||||
| Michael Graff | explorer@netbsd.org | |||||||
| Brad Grantham | grantham@tenon.com | |||||||
| Brian C. Grayson | bgrayson@netbsd.org | |||||||
| Matthew Green | mrg@netbsd.org | |||||||
| Juergen Hannken-Illjes | hannken@netbsd.org | |||||||
| Charles M. Hannum | mycroft@netbsd.org | |||||||
| Eric Haszlakiewicz | erh@netbsd.org | |||||||
| John Hawkinson | jhawk@netbsd.org | |||||||
| HAYAKAWA Koichi | haya@netbsd.org | |||||||
| René Hexel | rh@netbsd.org | |||||||
| Michael L. Hitch | mhitch@netbsd.org | |||||||
| Christian E. Hopps | chopps@netbsd.org | |||||||
| Ken Hornstein | kenh@netbsd.org | |||||||
| Marc Horowitz | marc@netbsd.org | |||||||
| Nick Hudson | skrll@netbsd.org | |||||||
| Martin Husemann | martin@netbsd.org | |||||||
| Dean Huxley | dean@netbsd.org | |||||||
| Bernardo Innocenti | bernie@netbsd.org | |||||||
| Tetsuya Isaki | isaki@netbsd.org | |||||||
| ITOH Yasufumi | itohy@netbsd.org | |||||||
| IWAMOTO Toshihiro | toshii@netbsd.org | |||||||
| Matthew Jacob | mjacob@netbsd.org | |||||||
| Lonhyn T. Jasinskyj | lonhyn@netbsd.org | |||||||
| Chris Jones | cjones@netbsd.org | |||||||
| Takahiro Kambe | taca@netbsd.org | |||||||
| Antti Kantee | pooka@netbsd.org | |||||||
| Masanori Kanaoka | kanaoka@netbsd.org | |||||||
| KAWAMOTO Yosihisa | kawamoto@netbsd.org | |||||||
| Mario Kemper | magick@netbsd.org | |||||||
| Lawrence Kesteloot | kesteloo@cs.unc.edu | |||||||
| Thomas Klausner | wiz@netbsd.org | |||||||
| Klaus Klein | kleink@netbsd.org | |||||||
| Wayne Knowles | wdk@netbsd.org | |||||||
| John Kohl | jtk@netbsd.org | |||||||
| Martti Kuparinen | martti@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 | |||||||
| Tomasz Luchowski | zuntum@netbsd.org | |||||||
| Federico Lupi | federico@netbsd.org | |||||||
| Brett Lymn | blymn@netbsd.org | |||||||
| Paul Mackerras | paulus@netbsd.org | |||||||
| MAEKAWA Masahide | gehenna@netbsd.org | |||||||
| David Maxwell | david@netbsd.org | |||||||
| Dan McMahill | dmcmahill@netbsd.org | |||||||
| Gregory McGarry | gmcgarry@netbsd.org | |||||||
| Jared D. McNeill | jmcneill@netbsd.org | |||||||
| Neil J. McRae | neil@netbsd.org | |||||||
| Perry Metzger | perry@netbsd.org | |||||||
| der Mouse | mouse@netbsd.org | |||||||
| Joseph Myers | jsm@netbsd.org | |||||||
| Ken Nakata | kenn@netbsd.org | |||||||
| Bob Nestor | rnestor@netbsd.org | |||||||
| NISHIMURA Takeshi | nsmrtks@netbsd.org | |||||||
| NONAKA Kimihiro | nonaka@netbsd.org | |||||||
| Jesse Off | joff@netbsd.org | |||||||
| Tatoku Ogaito | tacha@netbsd.org | |||||||
| Masaru Oki | oki@netbsd.org | |||||||
| Atsushi Onoe | onoe@netbsd.org | |||||||
| Greg Oster | oster@netbsd.org | |||||||
| Herb Peyerl | hpeyerl@netbsd.org | |||||||
| Matthias Pfaller | matthias@netbsd.org | |||||||
| Chris Pinnock | cjep@netbsd.org | |||||||
| Dante Profeta | dante@netbsd.org | |||||||
| Chris Provenzano | proven@netbsd.org | |||||||
| Michael Rauch | mrauch@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 | |||||||
| Reed Shadgett | dent@netbsd.org | |||||||
| Tim Shepard | shep@netbsd.org | |||||||
| Takao Shinohara | shin@netbsd.org | |||||||
| Takuya SHIOZAKI | tshiozak@netbsd.org | |||||||
| Chuck Silvers | chs@netbsd.org | |||||||
| Thor Lancelot Simon | tls@netbsd.org | |||||||
| Jeff Smith | jeffs@netbsd.org | |||||||
| SOMEYA Yoshihiko | someya@netbsd.org | |||||||
| Bill Sommerfeld | sommerfeld@netbsd.org | |||||||
| Bill Squier | groo@netbsd.org | |||||||
| Bill Studenmund | wrstuden@netbsd.org | |||||||
| Kevin Sullivan | sullivan@netbsd.org | |||||||
| SUNAGAWA Keiki | kei@netbsd.org | |||||||
| Kimmo Suominen | kim@netbsd.org | |||||||
| TAMURA Kent | kent@netbsd.org | |||||||
| Shin'ichiro TAYA | taya@netbsd.org | |||||||
| Matt Thomas | matt@netbsd.org | |||||||
| Christoph Toshok | toshok@netbsd.org | |||||||
| UCHIYAMA Yasushi | uch@netbsd.org | |||||||
| Shuichiro URATA | ur@netbsd.org | |||||||
| Todd Vierling | tv@netbsd.org | |||||||
| Aymeric Vincent | aymeric@netbsd.org | |||||||
| Paul Vixie | vixie@netbsd.org | |||||||
| Krister Walfridsson | kristerw@netbsd.org | |||||||
| Lex Wennmacher | wennmach@netbsd.org | |||||||
| Assar Westerlund | assar@netbsd.org | |||||||
| Todd Whitesel | toddpw@netbsd.org | |||||||
| Rob Windsor | windsor@netbsd.org | |||||||
| Dan Winship | danw@netbsd.org | |||||||
| Jim Wise | jwise@netbsd.org | |||||||
| Michael Wolfson | mbw@netbsd.org | |||||||
| Colin Wood | ender@netbsd.org | |||||||
| YAMAMOTO Takashi | yamt@netbsd.org | |||||||
| Yuji Yamano | yyamano@netbsd.org | |||||||
| Reinoud Zandijk | reinoud@netbsd.org | |||||||
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 (eay@mincom.oz.au).
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 Reinoud Zandijk.
This product includes software developed by Allen K. Briggs.
This product includes software developed by Apple Computer, Inc.
This product includes software developed by Bill Studenmund.
This product includes software developed by Bradley A. Grantham.
This product includes software developed by Carnegie-Mellon University.
This product includes software developed by Chris P. Cputo.
This product includes software developed by Colin Wood.
This product includes software developed by David Huang.
This product includes software developed by Internet Research Institute, Inc.
This product includes software developed by John P. Wittkoski.
This product includes software developed by Open Software Foundation, Inc.
This product includes software developed by Per Fogelstrom, Opsycon AB and
RTMX Inc, USA.
This product includes software developed by Takashi Hamada.
This product includes software developed by Tsubai Masanari.
This product includes software developed by University of Utah.
This product includes software developed by Wolfgang Solfrank.