About this Document............................................2
Quick install notes for the impatient..........................3
What is NetBSD?................................................4
Upgrade path to NetBSD 1.6.....................................4
Changes Between The NetBSD 1.5 and 1.6 Releases................5
Kernel......................................................5
Networking..................................................5
File system.................................................6
Security....................................................6
System administration and user tools........................7
Miscellaneous...............................................7
macppc specific.............................................8
The Future of NetBSD...........................................8
Sources of NetBSD..............................................9
NetBSD 1.6 Release Contents....................................9
NetBSD/macppc subdirectory structure.......................11
Binary distribution sets...................................11
NetBSD/macppc System Requirements and Supported Devices.......13
Supported models...........................................13
Unsupported models.........................................14
Supported devices..........................................15
Unsupported devices........................................17
Supported boot devices and media...........................17
Getting the NetBSD System on to Useful Media..................17
Preparing your System for NetBSD installation.................19
Prepare yourself...........................................19
Updating your BootROM......................................20
Getting to the Open Firmware Prompt on Newer Models........20
Getting to the Open Firmware Prompt on Apple Network.......21
Getting to the Open Firmware Prompt on Older Models........21
Older Open Firmware System Preparation.....................22
Getting to the Open Firmware Prompt (Recommended method using22
Getting to the Open Firmware Prompt (Harder method using...23
Getting to the Open Firmware Prompt (Without using MacOS)..24
Setting up pre-Open Firmware 3 to boot NetBSD..............25
Setting up Open Firmware 3 to boot NetBSD..................26
Available Boot Media.......................................27
Description of bootable media..............................28
Partitioning your hard drive for NetBSD....................29
Preparing the Bootable Media...............................31
Booting off an MS-DOS floppy............................32
Booting off the NetBSD install floppy...................32
Booting off an HFS or HFS+ partition....................33
Booting off the NetBSD/macppc CD-R image................33
Booting off an ISO9660 CD-ROM...........................33
Booting off a hybrid HFS/ISO9660 CD-ROM.................34
Booting over the ethernet...............................35
Booting the floppy image off a SCSI or IDE drive........39
Installing the NetBSD System..................................40
Open Firmware boot syntax..................................40
Examples of Open Firmware boot commands....................43
Booting off an MS-DOS floppy............................43
Booting off the NetBSD install floppy...................43
Booting off the NetBSD/macppc install CD-R..............44
Booting off the NetBSD/macppc install CD-R..............44
Booting off a home-made CD-ROM ISO9660 or Hybrid........44
Booting off an IDE or SCSI drive with 'partition zero'..45
Booting off an IDE or SCSI drive with an HFS partition..45
Example of a normal boot...................................46
Common Problems and Error Messages.........................46
Black screen............................................47
Grey screen with flashing question mark.................47
Information on your screen seems garbled or out of sync.47
DEFAULT CATCH!..........................................47
CLAIM failed............................................47
can't OPEN..............................................48
unrecognized Client Program formatstate not valid.......48
bad partition number, using 0no bootable HFS partition..48
TFTP timeout............................................48
Bootloader hangs before the copyright notice............48
Hang after configuring devices..........................49
Milestone..................................................49
Running the sysinst installation program...................49
Introduction............................................49
General.................................................49
Quick install...........................................49
Booting NetBSD..........................................51
Network configuration...................................51
Preparing a disk which will be used for Mac OS and NetBSDInstallation drive selection and parameters.............52
Partitioning the disk...................................53
Preparing your hard disk................................53
Getting the distribution sets...........................54
Installation using ftp..................................54
Installation using NFS..................................54
Installation from CD-ROM................................54
Installation from an unmounted file system..............55
Installation from a local directory.....................55
Extracting the distribution sets........................55
Making the device nodes.................................55
Finalizing your installation............................56
Post installation steps.......................................56
Upgrading a previously-installed NetBSD System................58
Compatibility Issues With Previous NetBSD Releases............59
Issues affecting an upgrade from NetBSD 1.5................59
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.......................................................71
This document describes the installation procedure for
NetBSD1.6
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
.more
more(1)
and
less(1)
pager utility programs.
This is the format in which the on-line
man
pages are generally presented.
.txt
You are reading the HTML version.
This section contains some brief notes describing what you need to install NetBSD1.6 on a machine of the macppc architecture.
installation/ofwboot.xcf
and the installation kernel
binary/kernel/netbsd.INSTALL.gz
.
For systems without floppy drives, fetch the bootloader
installation/ofwboot.xcf
and the installation kernel
binary/kernel/netbsd.GENERIC_MD.gz
.
Alternatively, you can fetch the CD image,
macppc_bootable.iso
or the boot floppy image
installation/floppy/boot.fs
which include the bootloader and installation kernel.
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-GENERIC.tgz
,
base.tgz
and
etc.tgz
.
In a typical workstation installation you will probably want
all the installation sets.
ofwboot.xcf
and
netbsd.INSTALL.gz
to an MS-DOS formatted floppy disk and rename
netbsd.INSTALL.gz
to
netbsd.gz
.
Otherwise, drag
ofwboot.xcf
and
netbsd.GENERIC_MD.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 Mac OS unless you partition your disk using a Mac OS 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 Mac OS 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
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
You should have the Open Firmware
``0 >
''
prompt on your screen before attempting to boot
NetBSD/macppc.
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
file system.
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
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 fifty three different system architectures (ports), featuring seventeen machine architectures across eleven distinct CPU families, and is being ported to more. The NetBSD1.6 release contains complete binary releases for thirty eight different system architectures. (The fifteen 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.
NetBSD1.6 is an upgrade of NetBSD1.5.3 and earlier major and patch 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.6 was started are designated by version identifiers such as 1.6A, 1.6B, etc. These identifiers do not designate releases, but indicate major changes in internal kernel APIs. Note that the kernel from NetBSD 1.6 can not be used to upgrade a system running one of those intermediate development versions. Trying to use the NetBSD 1.6 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.6 to determine if a given feature is present or absent in 1.6. The development of 1.6 and the subsequent ``point'' releases is done on a separate branch in the CVS repository. The branch was created when the release cycle for 1.6 was started, and during the release cycle of 1.6 and its patch releases selected fixes and enhancements have been imported from the main development trunk.
The NetBSD1.6 release provides numerous significant functional enhancements, including support for many new devices, integration of hundreds of bug fixes, new and updated kernel subsystems, and many user-land enhancements. The result of these improvements is a stable operating system fit for production use that rivals most commercially available systems.
It is impossible to completely summarize over eighteen months of development that went into the NetBSD1.6 release. Some highlights include:
scsipi(9)
.
userconf(4)
,
activated with the
-c
boot loader flag.
ehci(4)
host controller.
irframe(4)
IrDA frame level driver.
Serial dongles and the
oboe(4)
driver are currently supported.
INCLUDE_CONFIG_FILE
in
options(4)
for more information.
sysctl(8)
.
).
vlan(4)
.
ndbootd(8)
added;
used to netboot
NetBSD/sun2
machines.
racoon(8)
added;
IKE key management daemon for IPsec key negotiation, from the KAME project.
ifconfig(8)
and
awi(4)
driver.
wi(4)
and
wiconfig(8)
now support scanning for access points,
and defaults to BSS instead of ad-hoc mode.
bridge(4)
.
pppoe(4)
.
ifwatchd(8)
added;
invokes up-script and down-script when a network interface goes up and down.
Used by
pppoe(4)
.
dump(8)
,
dumpfs(8)
,
fsck_ffs(8)
,
fsirand(8)
,
newfs(8)
,
and
tunefs(8)
support a
-F
option to manipulate file system images in regular files.
makefs(8)
added;
creates file system images from a directory tree.
(Currently ffs only.)
)
by Grigoriy Orlov, which noticeably improves performance on FFS file systems
when creating directories, and subsequently manipulating them.
newfs(8)
calculates default block size from the file system size,
and uses the largest possible cylinders/group (cpg) value if
-c
isn't given.
dpti(4)
driver added;
an implementation of the DPT/Adaptec SCSI/I2O RAID management interface.
Allows the use of the Linux versions of
dptmgr,
raidutil,
dptelog,
(etc).
chroot(8)
hierarchy for services including
named(8)
,
ntpd(8)
,
and
sshd(8)
.
passwd(5)
ciphers:
MD5, and
DES with more encryption rounds.
See
passwd.conf(5)
.
/etc/security
performs many more checks and is far more flexible in how it monitors
changes.
See
security.conf(5)
.
sushi(8)
added;
a menu based system administration tool.
pgrep(1)
and
pkill(1)
added;
find or signal processes by name or other attributes.
etcupdate(8)
script which helps updating the
/etc
config files interactively, and the
/etc/postinstall
script which is provided to check for or fix configuration changes
that have occurred in
NetBSD.
stat(1)
added;
a user interface to the information returned by the
stat(2)
system call.
sort(1)
replaces
GNU
sort(1)
.
rc.d(8)
scripts waits until the service terminates before returning.
This improves the reliability of
``restart''
operations as well.
swapoff
in
rc.conf(5)
.
rc.shutdown(8)
after the number of seconds provided in
rcshutdown_timeout
from
rc.conf(5)
.
src/build.sh
is available for doing arbitrary cross-builds; see
src/BUILDING
for more information.
At least 38 ports for the
NetBSD1.6
release were cross-built on a
NetBSD/i386
system using this mechanism.
agp(4)
for faster access to graphics boards.
init(8)
will create an mfs (memory based file system)
/dev
if
/dev/console
is missing.
vmstat(8)
displays kernel hash statistics with
-H
and
-h hash.
wscons(4)
supports blanking of VGA consoles.
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 third 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.6 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.6 release is organized as follows:
.../NetBSD-1.6/
CHANGES
LAST_MINUTE
MIRRORS
README.files
TODO
patches/
source/
In addition to the files and directories listed above, there is one
directory per architecture, for each of the architectures for which
NetBSD1.6
has a binary distribution.
There are also
README.export-control
files sprinkled liberally throughout the
distribution tree, which point out that there are some portions of the
distribution 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.
The source distribution sets can be found in subdirectories of the
source
subdirectory of the distribution tree.
They contain the complete sources to the system.
The source distribution sets are as follows:
config(8)
;
and
dbsym(8)
.
All the above source sets are located in the
source/sets
subdirectory of the distribution tree.
The source sets are distributed as compressed tar files.
Except for the
pkgsrc
set, which is traditionally unpacked into
/usr/pkgsrc
,
all sets may be unpacked into
/usr/src
with the command:
#
( cd / ; tar -zxpf - ) < set_name.tgz
The
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.)
The split distributions may be reassembled and extracted with cat as follows:
#
cat set_name.?? | ( cd / ; tar -zxpf - )
In each of the source distribution set directories, there are files which contain the checksums of the files in the directory:
BSDSUM
CKSUM
MD5
SYSVSUM
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.
macppc
subdirectory of the distribution:
.../NetBSD-1.6/macppc/
INSTALL.html
INSTALL.ps
INSTALL.txt
INSTALL.more
.more
file contains underlined text using the
more(1)
conventions for indicating italic and bold display.
binary/
kernel/
netbsd-GENERIC.gz
netbsd.GENERIC_MD.gz
netbsd.INSTALL.gz
sets/
installation/
floppy/boot.fs
ofwboot.xcf
macppc/binary/sets
subdirectory
of the
NetBSD1.6
distribution tree, and are as follows:
/usr/include
)
and the various system libraries (except the shared
libraries, which are included as part of the
base
set).
This set also includes the manual pages for
all of the utilities it contains, as well as the
system call and library manual pages.
/etc
and in several other places.
This set
must
be installed if you are installing the system from scratch, but should
not
be used if you are upgrading.
GENERIC
kernel, named
/netbsd
.
You
must
install this distribution set.
/usr/share
.
groff(1)
,
all related programs, and their manual pages.
NetBSD maintains its own set of sources for the X Window System in order to assure tight integration and compatibility. These sources are based on XFree86, and tightly track XFree86 releases. They are currently equivalent to XFree86 3.3.6. Binary sets for the X Window System are distributed with NetBSD. The sets are:
The macppc binary distribution sets are distributed as gzipped tar files
named with the extension
.tgz,
e.g.
base.tgz
.
The instructions given for extracting the source sets work equally
well for the binary sets, but it is worth noting that if you use that
method, the filenames stored in the sets are relative and therefore
the files are extracted
below the current directory.
Therefore, if you want to extract the binaries into your system, i.e.
replace the system binaries with them, you have to run the
tar -xpf
command from the root directory (
/
) of your system.
This utility is used only in a Traditional method installation.
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.
204.152.184.75
(as of June, 2002).
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.
/etc/exports
file on of the NFS server and resetting its mount daemon (mountd).
(Both of these actions will probably require superuser
privileges on the server.)
You need to know the 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
.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.
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.
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
wdc0:0:1: lost interrupt
problems.
Hold down a special four-key combination when your system boots.
After the chime starts, but before it stops, hold down the four
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
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.
0 > setenv auto-boot? false
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
`ttya
'
device in Open Firmware).
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
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 >
Your Apple Network Server's screen will remain black.
Now, set your system to always stop at the Open Firmware prompt.
0 > setenv auto-boot? false
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.
Open Firmware seems to ignore the settings on most DB15 to VGA adapters. Depending on your model, it will default to either 640 x 480 at 60 Hz or to the resolution previously selected in MacOS. Make sure that your monitor can handle these resolutions.
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)
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
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.
COMMAND-OPTION-P-R
keys during the boot chimes, or if you accidentally boot into
MacOS.
If your
`output-device'
is
`/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
You should now see the Open Firmware command prompt on your screen:
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 >
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).
0 > setenv auto-boot? false
0 > setenv use-nvramrc? false
0 > reset-all
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
`/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
If you have a Performa 5500 or 6500, you may need to apply NVRAMRC patches to use your built-in video. See the information in the NetBSD/macppc Model Support webpage.
You should now see the Open Firmware command prompt on your screen:
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 >
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).
0 > setenv auto-boot? false
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
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 >
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.
0 > setenv auto-boot? false
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
`screen
'
with the correct
`output-device'
for your model):
0 > setenv output-device screen
0 > setenv input-device kbd
0 > reset-all
Now you should see the Open Firmware prompt on your screen.
If your
`output-device'
is
`/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
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:
0 > dev /openprom
0 > .properties
name openprom
model Open Firmware, 1.0.5
relative-addressing
ok
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.
0 > setenv load-base 600000
0 > setenv real-base F00000
0 > reset-all
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.
0 > dev enet
0 > .properties
[...]
local-mac-address CCCCCCCC CCCC
[...]
ok
You can check your Open Firmware settings with the
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.
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:
0 > dev /openprom
0 > .properties
name openprom
device_type BootROM
model OpenFirmware 3
relative-addressing
supports-bootinfo
ok
If you will be netbooting your system, you can look up your MAC address.
0 > dev enet
0 > .properties
[...]
local-mac-address CCCCCCCC CCCC
[...]
You can check your Open Firmware settings with the
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
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 file systems (such as ISO9660, MS-DOS, and on some models HFS and HFS+). Unfortunately, Open Firmware is not able to use the NetBSD file system (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
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.
The following bootable media are available for loading the bootloader
(ofwboot
or ofwboot.xcf
)
(see below for descriptions):
Once
ofwboot
or
ofwboot.xcf
is loaded, it can open the kernel from one of the following sources:
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
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 file system with
an installation kernel and the distribution sets.
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
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.
While Open Firmware 3 supports this boot method, NetBSD/macppc does not yet support it on these systems.
This method loads
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 a previously installed
NetBSD
file system.
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
ofwboot.xcf
.
Load the
ofwboot.xcf
bootloader from an MS-DOS file system (such as a floppy or Zip disk).
It can then load a
NetBSD
kernel from the same MS-DOS file system or elsewhere.
This has only been thoroughly tested on floppy disks,
but may work on FDISK-formatted hard drives.
This does not work for MS-DOS partitions on a hard drive with an Apple
Partition Map.
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
ofwboot.xcf
bootloader from an ISO9660 CD-ROM.
It can then load a
NetBSD
kernel from the ISO9660 CD-ROM.
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
ofwboot.xcf
bootloader from the CD-ROM's HFS file system.
It can then load a
NetBSD
kernel from the HFS or ISO9660 file system.
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
(
/
)
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.
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,
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.
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:
/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.
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
mount_msdos(8)
on any unix-like machine.
netbsd.INSTALL.gz
and
ofwboot.xcf
to the floppy.
netbsd.INSTALL.gz
to
netbsd.gz
,
since OpenFirmware can't deal with MS-DOS filenames longer than eight
characters.
Skip forward to Installing the NetBSD System
installation/floppy/boot.fs
to a floppy disk
# dd if=boot.fs of=/dev/rfd0a bs=36k
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
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
Get suntar from http://hyperarchive.lcs.mit.edu/HyperArchive/Archive/cmp/suntar-222.hqx
boot.fs
and click
``Open''
Skip forward to Installing the NetBSD System
Place
ofwboot.xcf
and the installation kernel
netbsd.GENERIC_MD.gz
at the top level of your Macintosh file system.
That is, drag the two icons onto your hard drive icon (not the desktop).
Make sure they're both on the same partition.
Skip forward to Installing the NetBSD System
Go to one of the
NetBSD
mirror sites and download CD-R image from the
pub/NetBSD/iso
directory.
http://www.netbsd.org/mirrors/#iso
Get and install cdrecord.
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
# cdrecord -v speed=4 dev=/dev/cd1c output.iso
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
/dev/cd1d
).
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.6 CD-R image, as described in the section above.
Place
ofwboot.xcf
and the installation kernel
netbsd.GENERIC_MD.gz
at the top level of the CD.
Due to restrictions in the way that Open Firmware deals with ISO
filenames, you may wish to name your kernel
netbsd.gz
.
You may also place the
NetBSD1.6
distribution sets on the disk.
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
# mkhybrid -o output.iso -a -l -J -r -L /cdsources
# cdrecord -v speed=4 dev=/dev/cd1c output.iso
You will need to substitute the correct speed for your CD writer, and the
correct device for your system (for i386 it would be
/dev/cd1d
).
See the NetBSD Bootable CD-ROM HOW-TO for more detail: http://www.netbsd.org/Documentation/bootcd.html
installation/ofwboot.xcf
and
binary/kernel/netbsd.GENERIC_MD.gz
into the window
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.6 CD-R image, as described two sections above.
Place
ofwboot.xcf
and the installation kernel
netbsd.GENERIC_MD.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.
Due to restrictions in the way that Open Firmware deals with ISO
filenames, you may wish to name your kernel
netbsd.gz
.
You may also place the
NetBSD1.6
distribution sets on the ISO9660 partition
(not
only on the HFS partition).
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
# mkhybrid -o output.iso -hfs -part -a -l -J -r -L /cdsources
# cdrecord -v speed=4 dev=/dev/cd1c output.iso
You will need to substitute the correct speed for your CD writer, and the
correct device for your system (for i386 it would be
/dev/cd1d
).
See the NetBSD Bootable CD-ROM HOW-TO for more detail: http://www.netbsd.org/Documentation/bootcd.html
ofwboot.xcf
is necessary).
installation/ofwboot.xcf
to the temporary partition
binary/kernel/netbsd.GENERIC_MD.gz
into the window.
You may also want to drag the
NetBSD1.6
distribution sets to this window as well.
Skip forward to Installing the NetBSD System
To netboot a macppc, you must configure one or more servers to provide
information and files to your macppc (the
`client ).'
If you are using
NetBSD
(any architecture) on your netboot server(s), the information
provided here should be sufficient to configure everything.
Additionally, you may wish to look at the
diskless(8)
manual page and the manual pages for each daemon you'll be configuring.
If the server(s) are another operating system, you should consult the
NetBSD Diskless HOW-TO, which will walk you through the steps necessary to
configure the netboot services on a variety of platforms.
http://www.netbsd.org/Documentation/network/netboot/
You may either netboot the installer so you can install onto a locally attached disk, or you may run your system entirely over the network.
Briefly, the netboot
process involves discovery, bootstrap, kernel and file system stages.
In the first stage, the client discovers information
about where to find the bootstrap program.
Next, it downloads and executes the bootstrap program.
The bootstrap program goes through another discovery phase to determine
where the kernel is located.
The bootstrap program tries to mount the NFS share containing the kernel.
Once the kernel is loaded, it starts executing.
For RAM disk kernels, it mounts the RAM disk file system and begins
executing the installer from the RAM disk.
For normal (non-RAM disk) kernels, the
kernel tries to mount the NFS share that had the kernel and starts
executing
the installation tools or
init(8)
.
All macppc systems use BOOTP for the discovery stage.
TFTP is used in the bootstrap phase to download
the bootstrap program,
ofwboot.xcf
.
NFS is used in both the kernel and file system stages to download the
kernel, and to access files on the file server.
We will use
`CC:CC:CC:CC:CC:CC
'
as the MAC address (ethernet hardware address) of your netboot client
machine.
You should have determined this address in an earlier stage.
In this example, we will use
`192.168.1.10
'
as the IP address of your client and
`client.test.net
'
as its name.
We will assume you're providing all of your netboot services
on one machine called
`server.test.net
'
with the client's files exported from the directory
/export/client/root
.
You should, of course, replace all of these with the names, addresses,
and paths appropriate to your environment.
You should set up each netboot stage in order (i.e. discovery, bootstrap, kernel, and then file system) so that you can test them as you proceed.
dhcpd(8)
in
bootpd(8)
compatible mode
Put the following lines in your
/etc/dhcpd.conf
(see
dhcpd.conf(5)
and
dhcp-options(5)
for more information):
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";
}
#you may paste another "host" entry here for additional clients on this network
}
You will need to make sure that the
dhcpd.leases
file exists.
# touch /var/db/dhcpd.leases
You will need to start the dhcpd. If it's already running, you will need to restart it to force it to re-read its configuration file. If the server is running NetBSD1.5 or later, you can achieve this with:
# /etc/rc.d/dhcpd restart
tftpd(8)
The default configuration of the TFTP server is to run in a
chroot(8)
environment in the
/tftpboot
directory.
Thus, the first order of business is to create this directory:
# mkdir -p /tftpboot
Next, edit
/etc/inetd.conf
and uncomment the line with the TFTP daemon:
tftp dgram udp wait root /usr/libexec/tftpd tftpd -l -s /tftpboot
Now, restart
inetd(8)
.
If the server is running
NetBSD1.5
or later, you can achieve this with:
# /etc/rc.d/inetd restart
Now, you need to copy the bootloader for your macppc machine to
/tftpboot
.
Get
ofwboot.xcf(8)
from the
installation
directory of the distribution.
# cp ofwboot.xcf /tftpboot
# chmod -R a+rX /tftpboot
Sometimes, the
arp(8)
table gets messed up, and the TFTP server can't communicate with the
client.
In this case, it will write a log message (via
syslogd(8)
)
to
/var/log/messages
saying:
`tftpd: write: Host is down
'.
If this is the case, you may need to force the server to map your client's
ethernet address to its IP address:
# arp -s client CC:CC:CC:CC:CC:CC
nfsd(8)
,
mountd(8)
,
and
rpcbind(8)
Now your system should be able to load the bootstrap program and start looking for the kernel. Let's set up the NFS server. Create the directory you are exporting for the netboot client:
# mkdir -p /export/client/root
Put the following line in
/etc/exports
to enable NFS sharing:
/export/client/root -maproot=root client.test.net
If your server is currently running an NFS server, you only need to
restart
mountd(8)
.
Otherwise, you need to start
rpcbind(8)
and
nfsd(8)
.
If the server is running
NetBSD1.5
or later, you can achieve this with:
# /etc/rc.d/rpcbind start
# /etc/rc.d/nfsd start
# /etc/rc.d/mountd restart
Now, if you place a kernel named
netbsd
in
/export/client/root
your client should boot the kernel.
If you are netbooting the installer, use
binary/kernel/netbsd.GENERIC_MD.gz
(this has the installation tools in a RAM disk).
Also, copy the distribution files to the client's root directory.
# cp *tgz /export/client/root
# gunzip netbsd.GENERIC_MD.gz
# mv netbsd.GENERIC_MD /export/client/root/netbsd
If you are running your macppc diskless, simply use
binary/kernel/netbsd-GENERIC.gz
.
You can skip this step if you do not plan to run your client diskless after installation. Otherwise, you need to extract and set up the client's installation of NetBSD. The Diskless HOW-TO describes how to provide better security and save space on the NFS server over the procedure listed here. http://www.netbsd.org/Documentation/network/netboot/nfs.html
# cd /export/client/root
# tar -xpzf /path/to/files/base.tgz
# tar -xpzf /path/to/files/etc.tgz
Continue with the other non-essential distribution sets if desired.
# mkdir /export/client/root/swap
# dd if=/dev/zero of=/export/client/swap bs=4k count=4k
# echo '/export/client/swap -maproot=root:wheel client.test.net' | cat >> /etc/exports
# /etc/rc.d/mountd restart
# cd /export/client/root/dev
# ./MAKEDEV all
This procedure only works on NetBSD hosts.
fstab(5)
Create a file in
/export/client/root/etc/fstab
with the following lines:
server:/export/client/swap none swap sw,nfsmntpt=/swap
server:/export/client/root / nfs rw 0 0
rc.conf(5)
Edit
/export/client/root/etc/rc.conf
rc_configured=YES
hostname="client"
defaultroute="192.168.1.1"
nfs_client=YES
auto_ifconfig=NO
net_interfaces=""
Make sure rc does not reconfigure the network device since it will lose its connection to the NFS server with your root file system.
hosts(5)
file.
Edit
/export/client/root/etc/hosts
::1 localhost
127.0.0.1 localhost
192.168.1.10 client.test.net client
192.168.1.5 server.test.net server
If you want
these services to start up every time you boot
your server, make sure the following lines are present in your
/etc/rc.conf
:
dhcpd=YES dhcpd_flags="-q"
nfs_server=YES # enable server daemons
mountd=YES
rpcbind=YES rpcbind_flags="-l" # -l logs libwrap
Also, you'll need to make sure the
tftpd
line in
/etc/inetd.conf
remains uncommented.
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
installation/floppy/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
file system from the disk image.
# dd if=boot.fs of=/dev/rsd0c
where
/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.
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
boot.fs
and click
``Open''
boot
boot-device
[boot-file]
[-as]
where the
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.
You use the
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
).
If the
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.
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:
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).
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 file system). 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:
0 > dev /
0 > ls
Open Firmware has device aliases which are simple names for the full
hardware path to a device (similar to
alias
in
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
On most systems, you'll find the devices you're looking for. Typical aliases are:
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 file systems at partition 1. Typically, Drive Setup formatted disks have their file systems starting at partition number 9. Often, if you omit the partition number, Open Firmware looks in the first partition it understands holding a valid file system.
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
file system 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 file system on your device with the dir command. This command is only useful with file systems 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 file systems. On Open Firmware 2.4, you can use it on HFS, HFS+, hybrid, ISO9960, and MS-DOS file systems. On Open Firmware 3, you can use it on HFS, HFS+, hybrid (not pure ISO9660), and MS-DOS file systems.
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.GENERIC_MD.gz
to
NETBSD~1.GZ
since MS-DOS file systems 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.GENERIC_MD.gz
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.GENERIC_MD.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
netbsd-GENERIC
you would need to open
NETBSD-G.ENE
The
mkisofs
and
mkhybrid
programs have a similar problem.
For them,
netbsd.GENERIC_MD.gz
becomes
NETBSD_GENERIC_MD.GZ
.
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).
We'll assume that you've wisely renamed your kernel to
netbsd.gz
to avoid many of these name issues.
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:,\OFWBOOT.XCF NETBSD.GZ
0 > boot scsi/sd@3:,\OFWBOOT.XCF NETBSD.GZ
0 > boot scsi-ext/sd@3:,\OFWBOOT.XCF NETBSD.GZ
0 > boot ata/atapi-disk:,\OFWBOOT.XCF NETBSD.GZ
0 > boot ide1/disk@0:,\OFWBOOT.XCF NETBSD.GZ
0 > boot cd:,\ofwboot.xcf netbsd.gz
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:
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
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:
% sudo pdisk /dev/disk0 -dump
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:
0 > boot scsi/sd@0:9,\ofwboot.xcf netbsd.GENERIC_MD.gz
0 > boot ide0/disk@0:10,\ofwboot.xcf netbsd.GENERIC_MD.gz
0 > boot hd:9,\ofwboot.xcf netbsd.GENERIC_MD.gz
0 > boot ultra1:9,ofwboot.xcf netbsd.GENERIC_MD.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.GENERIC_MD.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.1 (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
boot-device
variable, whose default value is the MacOS ROM.
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 file system, but can't find one. A happy face means it's trying to boot MacOS.
The boot floppy does not have a bootable MacOS file system, it has a bootable NetBSD file system.
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.
DEFAULT CATCH!
''
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.
CLAIM failed
''
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
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
Do not change
load-base
on an Open Firmware 3 system.
If you tried one boot command and it failed, then you tried a second and
got the
CLAIM
failed
message, then this is an indication that you should reboot between attempts.
Use the Open Firmware
reset-all
command.
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.
can't OPEN
''
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.
unrecognized Client Program formatstate not valid
''
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
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
''
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 file system on it (such as a hybrid CD-R or a hard drive with MacOS partitions).
TFTP timeout
''
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,
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
You forgot to set
real-base
in Open Firmware or it got erased by your booting into
MacOS.
Make sure you have the Open Firmware variable
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
Do not set
real-base
on an Open Firmware 3 system.
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.
Using sysinst, installing NetBSD is a relatively easy process. You still should read this document and have it in hand when doing the installation process. This document tries to be a good guideline for the installation and as such covers many details for the sake of completeness. Do not let this discourage you; the install program is not hard to use.
The following is a walk-through of the steps you will take while
getting
NetBSD
installed on your hard disk.
sysinst
is a menu driven
installation system that allows for some freedom in doing the
installation.
Sometimes, questions will be asked and in many cases
the default answer will be displayed in brackets
(``[ ]'')
after the question.
If you wish to stop the installation, you may press
CONTROL-C
at any time, but if you do, you'll have to begin the installation
process again from scratch by running the
/sysinst
program from the command prompt.
It is not necessary to reboot.
First, let's describe a quick install. The other sections of this document go into the installation procedure in more detail, but you may find that you do not need this. If you want detailed instructions, skip to the next section. This section describes a basic installation, using a CD-ROM install as an example.
.***********************************************.
* NetBSD-1.6 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
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 Mac OS 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:
#
stty erase '^h'
#
stty erase '^?'
Type the following command (replacing
wd0
with the name of your destination hard drive):
#
disklabel wd0
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:
#
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
Now, you need to create file systems on the partitions that NetBSD will be using.
Do not modify any partitions labeled
HFS
or
unknown
.
The partitions you will be using have their
fstype
listed as
4.2BSD
.
Run the
newfs
command on the
4.2BSD
partitions:
#
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.
Now you need to mount your destination root partition:
#
mount /dev/wd0a /mnt
Make an
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
If you mess up while typing, you can press
CONTROL-U
to erase everything on the current line, or
CONTROL-C
to cancel the file creation, so you can start over.
Great, now create the mountpoints for the file systems you listed in the
fstab
:
#
mkdir /mnt/usr
Clean up and return to
sysinst:
#
cd /;umount /mnt
#
exit
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 Mac OS, 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
wd0
,
wd1
,
sd0
or
sd1
.
If
sysinst
reports
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
You can skip a few steps, down to `Getting the distribution sets', if you are installing onto a drive that will be used with Mac OS (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 Mac OS, which is one of the reasons why you cannot use this installer to partition a disk that can be used with Mac OS.
There are 4 layouts for the NetBSD part of the disk that you can pick from: Standard, Standard with X, Custom and Use Existing. The first two use a set of default values (that you can change) suitable for a normal installation, possibly including X. With the Custom option you can specify everything yourself. The last option uses the partition info already present on the disk.
You will be presented with the current layout of the NetBSD disklabel, and given a chance to change it. For each partition, you can set the type, offset and size, block and fragment size, and the mount point. The type that NetBSD uses for normal file storage is called 4.2BSD. A swap partition has a special type called swap. Some partitions in the disklabel have a fixed purpose.
a
/
)
b
c
d-p
g
is the partition mounted on
/usr
,
but this is historical practice and not a fixed value.
You will then be asked to name your disk's disklabel. The default response 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
yes
at the prompt.
The install program will now label your disk and make the file systems you specified. The file systems will be initialized to contain NetBSD bootstrapping binaries and configuration files. You will see messages on your screen from the various NetBSD disk preparation tools that are running. There should be no errors in this section of the installation. If there are, restart from the beginning of the installation process. Otherwise, you can continue the installation program after pressing the return key.
ofwboot.xcf
on an HFS or HFS+ partition.
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
RETURN
in answer to these questions, and DNS will not be used.
You will also be asked to specify the host that you want to transfer the sets from, the directory on that host, the account name and password used to log into that host using ftp, and optionally a proxy server to use. If you did not set up DNS when answering the questions to configure networking, you will need to specify an IP address instead of a hostname for the ftp server.
sysinst will proceed to transfer all the default set files from the remote site to your hard disk.
To be able to install using NFS, you first need to configure
your network setup, if you haven't already at the start of
the install procedure.
sysinst
will do this for you, asking you
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
RETURN
in answer to these questions, and DNS will not be used.
You will also be asked to specify the host that you want to transfer the sets from, and the directory on that host that the files are in. This directory should be mountable by the machine you are installing on, i.e. correctly exported to your machine.
If you did not set up DNS when answering the questions to configure networking, you will need to specify an IP address instead of a hostname for the NFS server.
When installing from a CD-ROM, you will be asked to specify
the device name for your CD-ROM player
(usually cd0
),
and the directory name on the CD-ROM where the distribution files are.
sysinst will then check if the files are indeed available in the specified location, and proceed to the actual extraction of the sets.
In order to install from a local file system, you will
need to specify the device that the file system resides
on
(for example sd1e
)
the type of the file system,
and the directory on the specified file system where the sets are located.
sysinst
will then check if it
can indeed access the sets at that location.
Remember,
NetBSD/macppc
doesn't grok HFS or HFS+ partitions
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
/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 will be asked to select a password encryption algorithm
and can than set a password for the "root" account, to prevent
the machine coming up without access restrictions.
If you are installing using the
Re-install sets or install additional sets
option, then you will need to create the device nodes in
/dev
now.
Otherwise, skip this step.
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:
#
stty erase '^h'
#
stty erase '^?'
Type the following command (replacing
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
Congratulations, you have successfully installed NetBSD1.6.
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-only.
When the system asks you to choose a shell, simply press
RETURN
to get to a
/bin/sh
prompt.
If you are asked for a terminal type, respond with
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 file system read/write with:
#
/sbin/mount -u -w /
Change to the
/etc
directory and take a look at the
/etc/rc.conf
file.
Modify it to your tastes, making sure that you set
rc_configured=YES
so that your changes will be enabled and a multi-user boot can
proceed.
Default values for the various programs can be found in
/etc/defaults/rc.conf
,
where some in-line documentation may be found.
More complete documentation can be found in
rc.conf(5)
.
If your
/usr
directory is on a separate partition and you do not know how to use
ed,
you will have to mount your
/usr
partition to gain access to
ex
or
vi.
Do the following:
#
mount /usr
#
export TERM=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.6/macppc/All
subdir.
You can install them with the following commands:
# PKG_PATH=ftp://ftp.netbsd.org/pub/NetBSD/packages/1.6/macppc/All # export PKG_PATH # pkg_add -v tcsh # pkg_add -v apache # pkg_add -v perl ...
The above commands will install the tcsh shell, 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
README
file there for more information.
/etc/rc.local
to run any local daemons you use.
/etc
files are documented in section 5 of the manual; so just invoking
#
man 5 filename
is likely to give you more information on these files.
The upgrade to NetBSD1.6 is a binary upgrade; it can be quite difficult to update the system from an earlier version by recompiling from source, primarily due to interdependencies in the various components.
To do the upgrade, you must 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 files already installed on the system are overwritten in place,
you only need additional free space for files which weren't previously
installed or to account for growth of the sets between releases.
If you have a few megabytes free on each of your root
(/
)
and
/usr
partitions, you should have enough space.
Since upgrading involves replacing the 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 Mac OS 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
/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.
After a new kernel has been copied to your hard disk, your
machine is a complete
NetBSD1.6
system.
However, that doesn't mean that you're finished with the upgrade process.
You will probably want to update the set of device
nodes you have in
/dev
.
If you've changed the contents of
/dev
by hand, you will need to be careful about this, but if
not, you can just cd into
/dev
,
and run the command:
#
sh MAKEDEV all
Finally, you will want to delete old binaries that were part
of the version of
NetBSD
that you upgraded from and have since been removed from the
NetBSD
distribution.
Users upgrading from previous versions of NetBSD may wish to bear the following problems and compatibility issues in mind when upgrading to NetBSD1.6.
mkdir /tmp/upgrade
cd /tmp/upgrade
pax -zrpe -f /path/to/etc.tgz
./etc/postinstall -s `pwd` check
./etc/postinstall -s `pwd` fix
Issues fixed by postinstall:
/etc
need upgrading.
These include:
/etc/defaults/*
/etc/mtree/*
/etc/daily
/etc/weekly
/etc/monthly
/etc/security
/etc/rc.subr
/etc/rc
/etc/rc.shutdown
/etc/rc.d/*
/etc/rc.d/NETWORK
and
/etc/rc.d/gated
.
rc.conf(5)
entries are now obsolete:
amd_master
,
ip6forwarding
,
defcorename
,
and
nfsiod_flags
.
critical_filesystems_beforenet
has been replaced by
critical_filesystems_local
.
critical_filesystems
has been replaced by
critical_filesystems_remote
.
ssh(1)
and
sshd(8)
were moved from
/etc
to
/etc/ssh
,
including
ssh_known_hosts*
files and the
host key files
ssh_host*_key*
.
/etc/ssh.conf
was renamed to
/etc/ssh/ssh_config
,
and
/etc/sshd.conf
was renamed to
/etc/ssh/sshd_config
.
wscons.conf(5)
are now obsolete.
The following issues need to be resolved manually:
postfix(8)
configuration files require upgrading.
cd /usr/share/examples/postfix
cp post-install postfix-files postfix-script /etc/postfix
postfix check
/etc/ifconfig.de*
to
/etc/ifconfig.tlp*
,
renaming of
rc.conf(5)
entries
ifconfig_de*
to
ifconfig_tlp*
,
and the reconfiguration of files such as
/etc/dhclient.conf
and
/etc/ipf.conf
.
/etc/rc
modified to use
/etc/rc.d/*
Prior to
NetBSD1.5,
/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/
.
At system startup,
/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.'
At system shutdown,
/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
.
Local and third-party scripts may be installed into
/etc/rc.d
as necessary.
Refer to the other scripts in that directory and
rc(8)
for more information on implementing
rc.d
scripts.
named(8)
leaks version information.
Previous releases of
NetBSD
disabled a feature of
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)
was 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.
Due to
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.
Documentation is available if you first install the manual
distribution set.
Traditionally, the
``man pages''
(documentation) are denoted by
`name(section)
'.
Some examples of this are
intro(1)
,
man(1)
,
apropros(1)
,
passwd(1)
,
and
passwd(5)
.
The section numbers group the topics into several categories, but three are of primary interest: user commands are in section 1, file formats are in section 5, and administrative information is in section 8.
The man command is used to view the documentation on a topic, and is started by entering man[ section] topic. The brackets [] around the section should not be entered, but rather indicate that the section is optional. If you don't ask for a particular section, the topic with the lowest numbered section name will be displayed. For instance, after logging in, enter
#
man passwd
to read the documentation for
passwd(1)
.
To view the documentation for
passwd(5)
,
enter
#
man 5 passwd
instead.
If you are unsure of what man page you are looking for, enter apropos subject-word
where subject-word is your topic of interest; a list of possibly related man pages will be displayed.
If you've got something to say, do so! We'd like your input. There are various mailing lists available via the mailing list server at majordomo@netbsd.org. To get help on using the mailing list server, send mail to that address with an empty body, and it will reply with instructions.
There are various mailing lists set up to deal with comments and questions about this release. Please send comments to: netbsd-comments@netbsd.org.
To report bugs, use the
send-pr(1)
command shipped with
NetBSD,
and fill in as much information about the problem as you can.
Good bug reports include lots of details.
Additionally, bug reports can be sent by mail to:
netbsd-bugs@netbsd.org.
Use of
send-pr(1)
is encouraged, however, because bugs reported with it
are entered into the
NetBSD
bugs database, and thus can't slip through
the cracks.
There are also port-specific mailing lists, to discuss aspects of each port of NetBSD. Use majordomo to find their addresses, or visit http://www.netbsd.org/MailingLists/. If you're interested in doing a serious amount of work on a specific port, you probably should contact the `owner' of that port (listed below).
If you'd like to help with this effort, and have an idea as to how you could be useful, send us mail or subscribe to: netbsd-help@netbsd.org.
As a favor, please avoid mailing huge documents or files to these mailing lists. Instead, put the material you would have sent up for FTP or WWW somewhere, then mail the appropriate list about it, or, if you'd rather not do that, mail the list saying you'll send the data to those who want it.
Keith Bostic Ralph Campbell Mike Karels Marshall Kirk McKusick
for their ongoing work on BSD systems, support, and encouragement.
Mike Hibler Rick Macklem Jan-Simon Pendry Chris Torek
for answering lots of questions, fixing bugs, and doing the various work they've done.
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 Luke Mewburn 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 Rob Windsor Jim Wise Reinoud Zandijk Christos Zoulas
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.
(in alphabetical order)
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.