INSTALL(8)		NetBSD System Manager's	Manual		    INSTALL(8)

NNAAMMEE
     IINNSSTTAALLLL --	Installation procedure for NetBSD/macppc.

CCOONNTTEENNTTSS
     About this	Document
     Quick install notes for the impatient
     What is NetBSD?
     Changes Between The NetBSD	9 and 10 Releases
     Features to be removed in a later release
     The NetBSD	Foundation
     Sources of	NetBSD
     NetBSD 10.1_STABLE	Release	Contents
	NetBSD/macppc subdirectory structure
	Binary distribution sets
     NetBSD/macppc System Requirements and Supported Devices
	Supported models
	Unsupported models
	Supported devices
	Unsupported devices
	Supported boot devices and media
     Getting the NetBSD	System on to Useful Media
     Preparing your System for NetBSD installation
	Prepare	yourself
     Preparing your Open Firmware 3 System for NetBSD
	Updating your BootROM
	Getting	to Open	Firmware 3
	Setting	up Open	Firmware 3 to boot NetBSD
	Available Boot Media
	Partitioning your hard drive for NetBSD
	Preparing the Open Firmware 3 Bootable Media
	   Creating the	NetBSD/macppc CD-R
	   Preparing an	HFS or HFS+ partition
	   Preparing a custom hybrid HFS/ISO9660 CD-R
	   Creating an MS-DOS disk
	   Preparing the netboot server
	   Preparing a SCSI or IDE drive with the CD-R image
     Preparing your Open Firmware 1.x or 2.x System for	NetBSD
	Getting	to Open	Firmware on Apple Network Servers
	Open Firmware 1	and 2 System Preparation
	Getting	to Open	Firmware (MacOS	X or Darwin)
	Getting	to Open	Firmware (Best,	MacOS 8	or 9)
	Getting	to Open	Firmware (Harder, MacOS	7, 8, or 9)
	Getting	to Open	Firmware (Without using	MacOS)
	Setting	up Open	Firmware 1 and 2 to boot NetBSD
	Available Boot Media
	Partitioning your hard drive for NetBSD
	Preparing the Open Firmware 1 or 2 Bootable Media
	   Creating the	NetBSD/macppc CD-R
	   Creating the	NetBSD install floppies
	   Creating a custom ISO9660 CD-R
	   Creating an MS-DOS disk
	   Preparing the netboot server
	   Preparing a SCSI or IDE drive with the CD-R image
     Installing	the NetBSD System
	Open Firmware boot syntax
	Examples of Open Firmware boot commands
	   Booting the NetBSD/macppc install CD-R
	   Booting the NetBSD install floppies
	   Booting an IDE or SCSI drive	with an	HFS partition
	   Booting a custom CD-ROM
	   Booting an MS-DOS floppy
	   Booting over	the ethernet
	   Booting an IDE or SCSI drive	with 'partition	zero'
	Example	of a normal boot
	Common Problems	and Error Messages
	   Black screen
	   Grey	screen with flashing question mark
	   Information on your screen seems garbled or out of sync
	   DEFAULT CATCH!
	   CLAIM failed
	   can't OPEN
	   unrecognized	Client Program formatstate not valid
	   bad partition number, using 0no bootable HFS	partition
	   READ	TIMEOUT@
	   TFTP	timeout
	   enet:,/netbsd.ram.gz: Inappropriate file type or format
	   Bootloader hangs before the copyright notice
	   Hang	after configuring devices
	Milestone
	Running	the sysinst installation program
	   Introduction
	   General
	   Quick install
	   Booting NetBSD
	   Network configuration
	   Preparing a disk for	Open Firmware 3	systems
	   Installation	drive selection	and parameters
	   Selecting which sets	to install
	   Partitioning	the disk
	   Preparing your hard disk
	   Getting the distribution sets
	   Installation	from CD-ROM
	   Installation	using FTP
	   Installation	using NFS
	   Installation	from an	unmounted file system
	   Installation	from a local directory
	   Extracting the distribution sets
	   Configure additional	items
	   Finalizing your installation
	Finalizing Open	Firmware settings
	   Booting NetBSD exclusively
	   Additional Open Firmware tips
	   Booting NetBSD and MacOS X or Darwin
	   Booting NetBSD and MacOS 9 or earlier
	   Other boot techniques
     Post installation steps
     Upgrading a previously-installed NetBSD System
     Compatibility Issues With Previous	NetBSD Releases
     Using online NetBSD documentation
     Administrivia
     Thanks go to
     Legal Mumbo-Jumbo
     The End

DDEESSCCRRIIPPTTIIOONN
   AAbboouutt tthhiiss DDooccuummeenntt
     This document describes the installation procedure	for
     NetBSD 10.1_STABLE	on the _m_a_c_p_p_c platform.	 It is available
     in	four different formats titled _I_N_S_T_A_L_L_._e_x_t, where _._e_x_t is
     one of _._p_s, _._h_t_m_l,	_._m_o_r_e, or _._t_x_t:

	   _._p_s	   PostScript.

	   _._h_t_m_l   Standard Internet HTML.

	   _._m_o_r_e   The enhanced	text format used on UNIX-like
		   systems by the more(1) and less(1) pager util-
		   ity programs.  This is the format in	which the
		   on-line _m_a_n pages are generally presented.

	   _._t_x_t	   Plain old ASCII.

     You are reading the _m_o_r_e version.

   QQuuiicckk iinnssttaallll nnootteess ffoorr tthhee iimmppaattiieenntt
     This section contains some	brief notes describing what you
     need to install NetBSD 10.1_STABLE	on a machine of	the
     macppc architecture.

     ++oo	 Fetch files needed to install NetBSD.	The files depend
	 on which model	you are	using and how you plan to boot
	 your machine.	For systems with built-in floppy drives
	 (Open Firmware	1 or 2), fetch the pair	of boot	floppy
	 images	_m_a_c_p_p_c_/_i_n_s_t_a_l_l_a_t_i_o_n_/_f_l_o_p_p_y_/_b_o_o_t_1_._f_s and
	 _m_a_c_p_p_c_/_i_n_s_t_a_l_l_a_t_i_o_n_/_f_l_o_p_p_y_/_b_o_o_t_2_._f_s, which include the
	 bootloader and	installation kernel.  For systems without
	 floppy	drives (most are Open Firmware 3), fetch the
	 bootloader _m_a_c_p_p_c_/_i_n_s_t_a_l_l_a_t_i_o_n_/_o_f_w_b_o_o_t_._x_c_f and	the
	 installation kernel
	 _m_a_c_p_p_c_/_b_i_n_a_r_y_/_k_e_r_n_e_l_/_n_e_t_b_s_d_-_G_E_N_E_R_I_C___M_D_._g_z.  If	you have
	 a CD-R, you can fetch the CD image,
	 _N_e_t_B_S_D_-_1_0_._1___S_T_A_B_L_E_-_m_a_c_p_p_c_._i_s_o.	 Alternatively,	you may
	 netboot the installation kernel.  This	process	is cov-
	 ered below, in	detail.

     ++oo	 The actual binary distribution	is in the
	 _m_a_c_p_p_c_/_b_i_n_a_r_y_/_s_e_t_s_/ directory.	 When you boot the
	 install kernel	from floppies, 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:
	 _k_e_r_n_-_G_E_N_E_R_I_C_._t_g_z, _b_a_s_e_._t_g_z and	_e_t_c_._t_g_z.  In a typical
	 workstation installation you will probably want all the
	 installation sets.

     ++oo	 If your macppc	has a floppy drive, create the pair of
	 boot floppies using ssuunnttaarr (MacOS 9), rraawwrriittee (Windows),
	 or dddd (any UNIX-like system with floppy support).  If
	 your system has Open Firmware 3, drag _o_f_w_b_o_o_t_._x_c_f and
	 _n_e_t_b_s_d_-_G_E_N_E_R_I_C___M_D_._g_z to your hard drive icon (the top
	 level of the drive, not the desktop).	If you are using
	 the CD	image, burn it now.

	 The media you just prepared will be used to boot the
	 installation kernel, which contains all the tools
	 required to install NetBSD.

     ++oo	 Determine your	machine's model, quirks, and Open
	 Firmware version from the NetBSD/macppc _M_o_d_e_l _S_u_p_p_o_r_t
	 _w_e_b_p_a_g_e_:
	       hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//mmooddeellss..hhttmmll.

	 At present, NetBSD/macppc cannot exist	on the same hard
	 drive as Mac OS unless	you partition your disk	before
	 running the installer.	 Open Firmware versions	prior to
	 3 require a dedicated NetBSD drive -- 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
	 partition your	disk before running the	installer, then
	 select	the ``RRee--iinnssttaallll sseettss oorr iinnssttaallll aaddddiittiioonnaall
	 sseettss''	option in the installer	(selecting the ``IInnssttaallll
	 NNeettBBSSDD	ttoo hhaarrdd	ddiisskk'' or ``UUppggrraaddee NNeettBBSSDD oonn aa	hhaarrdd
	 ddiisskk''	options	will render your drive unbootable).  If
	 you are unsure, you may want to read the section below
	 on _P_a_r_t_i_t_i_o_n_i_n_g _y_o_u_r _h_a_r_d _d_r_i_v_e _f_o_r _N_e_t_B_S_D

     ++oo	 For systems with Open Firmware	versions prior to 3, you
	 may need to use Apple's System	Disk utility to	enter
	 Open Firmware and use your screen and keyboard.  To
	 enter Open Firmware, hold down	the COMMAND-OPTION-O-F
	 keys after the	boot chime starts, but before the chime
	 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 _O_l_d_e_r _O_p_e_n
	 _F_i_r_m_w_a_r_e _S_y_s_t_e_m _P_r_e_p_a_r_a_t_i_o_n

	 You should have the Open Firmware ``_0 _>'' prompt on your
	 screen	before attempting to boot NetBSD/macppc.

     ++oo	 At the	Open Firmware prompt, type the command to boot.
	 To boot from the installation floppies, the command is
	 ``bboooott	ffdd::00''.	 For the install kernel	and bootloader on
	 your hard drive (Open Firmware	3), the	command	is ``bboooott
	 hhdd::,,\\ooffwwbboooott..xxccff nneettbbssdd--GGEENNEERRIICC__MMDD..ggzz''.

	 For boot CDs, the command is something	like ``bboooott
	 ccdd::,,\\ooffwwbboooott..xxccff nneettbbssdd..mmaaccppppcc'' (for Open Firmware 3)
	 or ``bboooott ssccssii--iinntt//ssdd@@33::00 NNEETTBBSSDD..MMAACCPPPPCC'' (for	earlier
	 Open Firmware versions).  You will need to use	the cor-
	 rect case for OOFFWWBBOOOOTT..XXCCFF and NNEETTBBSSDD..MMAACCPPPPCC depending on
	 how your version of Open Firmware interprets the ISO
	 file system.  You may need to replace ccdd with ssccssii//ssdd@@33
	 ,, ssccssii--iinntt//ssdd@@33 ,, aattaa//aattaappii--ddiisskk ,, or some other device
	 alias.	 You should also use the Open Firmware ddiirr com-
	 mand to confirm that the NetBSD/macppc	kernel is called
	 _N_E_T_B_S_D_._M_A_C_P_P_C.	 You may want to read the section below
	 on _O_p_e_n _F_i_r_m_w_a_r_e _b_o_o_t _s_y_n_t_a_x

     ++oo

	 PowerPC 601 machines need to use separate boot	floppies
	 _m_a_c_p_p_c_/_i_n_s_t_a_l_l_a_t_i_o_n_/_f_l_o_p_p_y_/_b_o_o_t_6_0_1___1_._f_s and
	 _m_a_c_p_p_c_/_i_n_s_t_a_l_l_a_t_i_o_n_/_f_l_o_p_p_y_/_b_o_o_t_6_0_2___2_._f_s, a different
	 kernel	set _k_e_r_n_-_G_E_N_E_R_I_C___6_0_1_._t_g_z, and a	different install
	 kernel	_n_e_t_b_s_d_-_I_N_S_T_A_L_L___6_0_1_._g_z.	The same boot CD can be
	 used but at the boot prompt you must specify the 601
	 kernel, i.e., replace nneettbbssdd..mmaaccppppcc with nneettbbssdd..660011

     ++oo	 For third-party programs which	are not	part of	the base
	 NetBSD	distribution, you will want to explore the ppkkggssrrcc
	 package management system, which contains thousands of
	 third-party software applications.

   WWhhaatt	iiss NNeettBBSSDD??
     The NetBSD	Operating System is a fully functional open-
     source operating system derived from the University of Cali-
     fornia, Berkeley Networking Release 2 (Net/2), 4.4BSD-Lite,
     and 4.4BSD-Lite2 sources.	NetBSD runs on many different
     different system architectures (ports) across a variety of
     distinct CPU families, and	is being ported	to more.  The
     NetBSD 10.1_STABLE	release	contains complete binary releases
     for most of these system architectures, with preliminary
     support for the others included in	source form.  For more
     information please	visit hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//.

     NetBSD is a completely integrated system.	In addition to
     its highly	portable, high performance kernel, NetBSD fea-
     tures a complete set of user utilities, compilers for sev-
     eral 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 commu-
     nity.  Without the	unique cooperation and coordination the
     net makes possible, NetBSD	would not exist.

   CChhaannggeess BBeettwweeeenn TThhee NNeettBBSSDD 99	aanndd 1100 RReelleeaasseess
     The NetBSD	10.1_STABLE release provides many significant
     changes, including	support	for many new devices, hundreds of
     bug fixes,	new and	updated	kernel subsystems, and numerous
     userland enhancements.  The result	of these improvements is
     a stable operating	system fit for production use that rivals
     most commercially available systems.

     One important new feature in this release is the support for
     extended attributes and access control lists on FFS file
     systems.

     For new installations the installer will by default disable
     these features, so	the file system	is compatible with older
     NetBSD releases (before 10), and allow other operating sys-
     tems to mount this	file systems at	least in read-only mode.

     If	you want a new installed file system to	support	extended
     attributes, change	the file system	type from ``FFSv2'' to
     ``FFSv2ea'' in the	partitioning menu.  You	can also convert
     file systems later, using the fsck_ffs(8) utility.	 More
     details are available in _t_h_i_s _g_u_i_d_e_:
	   hhttttppss::////wwiikkii..nneettbbssdd..oorrgg//ttuuttoorriiaallss//aaccllss__aanndd__eexxtteennddeedd__aattttrriibbuutteess__oonn__ffffss.

     If	you are	upgrading from a version of NetBSD -current
     please also check the _C_o_m_p_a_t_i_b_i_l_i_t_y _I_s_s_u_e_s	_W_i_t_h _P_r_e_v_i_o_u_s
     _N_e_t_B_S_D _R_e_l_e_a_s_e_s.  It is impossible	to completely summarize
     the massive development that went into the	NetBSD 10.1_STA-
     BLE release.  The complete	list of	changes	can be found in
     _C_H_A_N_G_E_S_:
	   hhttttppss::////nnyyccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD--ddaaiillyy//nneettbbssdd--1100//llaatteesstt//CCHHAANNGGEESS
     _C_H_A_N_G_E_S_-_1_0_._1_:
	   hhttttppss::////nnyyccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD--ddaaiillyy//nneettbbssdd--1100//llaatteesstt//CCHHAANNGGEESS--1100..11
     _C_H_A_N_G_E_S_-_1_0_._2_:
	   hhttttppss::////nnyyccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD--ddaaiillyy//nneettbbssdd--1100//llaatteesstt//CCHHAANNGGEESS--1100..22
     which are also present in the top level directory of the
     NetBSD 10.1 release tree.

   FFeeaattuurreess ttoo bbee rreemmoovveedd iinn aa llaatteerr rreelleeaassee
     The following features are	to be removed from NetBSD in the
     future:

	   ++oo   groff(1).  Man pages are	now handled with
	       mandoc(1), and groff(1) can still be found in
	       pkgsrc as _t_e_x_t_p_r_o_c_/_g_r_o_f_f.

	   ++oo   pf(4).  This packet filter is obsolete and unmain-
	       tained in NetBSD.  It will be eventually	removed
	       due to possible long-standing security issues and
	       lack of multiprocessor support.	New installations
	       should use npf(7).

   TThhee NNeettBBSSDD FFoouunnddaattiioonn
     The NetBSD	Foundation is a	tax exempt, not-for-profit
     501(c)(3) corporation that	devotes	itself to the traditional
     goals and spirit of the NetBSD Project and	owns the trade-
     mark of the word ``NetBSD''.  It supports the design, devel-
     opment, and adoption of NetBSD worldwide.	More information
     on	the NetBSD Foundation, its composition,	aims, and work
     can be found at:
	   hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ffoouunnddaattiioonn//

   SSoouurrcceess ooff NNeettBBSSDD
     Refer to _m_i_r_r_o_r_s_:
	   hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//mmiirrrroorrss//

   NNeettBBSSDD 1100..11__SSTTAABBLLEE RReelleeaassee CCoonntteennttss
     The root directory	of the NetBSD 10.1_STABLE release is
     organized as follows:

     _._._._/_N_e_t_B_S_D_-_1_0_._1___S_T_A_B_L_E_/

     CHANGES	   Changes between the 9.0 and 10.0 releases.

     CHANGES-10.0  Changes between the initial 10.0 branch and
		   final release of 10.0.

     CHANGES-10.1  Changes between the 10.0 and	the 10.1 release.

     CHANGES-10.2  Changes after the release of	10.1.

     CHANGES.prev  Changes in previous NetBSD releases.

     README.files  README describing the distribution's	contents.

     _i_m_a_g_e_s_/	   Images (ISO 9660 or USB) for	installing
		   NetBSD.  Depending on your system, these may
		   be bootable.

     _s_o_u_r_c_e_/	   Source distribution sets; see below.

     In	addition to the	files and directories listed above, there
     is	one directory per architecture,	for each of the	architec-
     tures for which NetBSD 10.1_STABLE	has a binary distribu-
     tion.

     The source	distribution sets can be found in subdirectories
     of	the _s_o_u_r_c_e subdirectory	of the distribution tree.  They
     contain the complete sources to the system.  The source dis-
     tribution sets are	as follows:

     ggnnuussrrcc    This set	contains the ``gnu'' sources, including
	       the source for the compiler, assembler, groff, and
	       the other GNU utilities in the binary distribution
	       sets.

     sshhaarreessrrcc  This set	contains the ``share'' sources,	which
	       include the sources for the man pages not associ-
	       ated with any particular	program; the sources for
	       the typesettable	document set; the dictionaries;
	       and more.

     ssrrcc       This set	contains all of	the base NetBSD	10.1_STA-
	       BLE sources which are not in ggnnuussrrcc, sshhaarreessrrcc, or
	       ssyyssssrrcc.

     ssyyssssrrcc    This set	contains the sources to	the NetBSD
	       10.1_STABLE kernel for all architectures	as well
	       as the config(1)	utility.

     xxssrrcc      This set	contains the sources to	the X Window Sys-
	       tem.

     All the above source sets are located in the _s_o_u_r_c_e_/_s_e_t_s
     subdirectory of the distribution tree.

     The source	sets are distributed as	compressed tar files.
     Except for	the ppkkggssrrcc set,	which is traditionally unpacked
     into _/_u_s_r_/_p_k_g_s_r_c, all sets	may be unpacked	into _/_u_s_r_/_s_r_c
     with the command:
	   # ccdd	// ;; ttaarr	--zzxxppff sseett__nnaammee..ttggzz

     In	each of	the source distribution	set directories, there
     are files which contain the checksums of the files	in the
     directory:

	   MD5	   MD5 digests in the format produced by the com-
		   mand:
		   cckkssuumm --aa MMDD55	_f_i_l_e.

	   SHA512  SHA512 digests in the format	produced by the
		   command:
		   cckkssuumm --aa SSHHAA551122 _f_i_l_e.

     The SHA512	digest is safer, but MD5 checksums are provided
     so	that a wider range of operating	systems	can check the
     integrity of the release files.

     _N_e_t_B_S_D_/_m_a_c_p_p_c _s_u_b_d_i_r_e_c_t_o_r_y	_s_t_r_u_c_t_u_r_e

     The macppc-specific portion of the	NetBSD 10.1_STABLE
     release is	found in the _m_a_c_p_p_c subdirectory of the	distribu-
     tion: _._._._/_N_e_t_B_S_D_-_1_0_._1___S_T_A_B_L_E_/_m_a_c_p_p_c_/.  It contains	the fol-
     lowing files and directories:

     _I_N_S_T_A_L_L_._h_t_m_l
     _I_N_S_T_A_L_L_._p_s
     _I_N_S_T_A_L_L_._t_x_t
     _I_N_S_T_A_L_L_._m_o_r_e  Installation	notes in various file formats,
		   including this file.	 The _._m_o_r_e file	contains
		   underlined text using the more(1) conventions
		   for indicating italic and bold display.
     _b_i_n_a_r_y_/
		   _k_e_r_n_e_l_/
			    _n_e_t_b_s_d_-_G_E_N_E_R_I_C_._g_z
				       A gzipped NetBSD	kernel
				       containing code for every-
				       thing supported in this
				       release.
			    _n_e_t_b_s_d_-_G_E_N_E_R_I_C___6_0_1_._g_z
				       A gzipped NetBSD	kernel
				       containing code for Pow-
				       erPC 601	machines.
			    _n_e_t_b_s_d_-_G_E_N_E_R_I_C_._M_P_._g_z
				       A gzipped NetBSD	kernel
				       containing code for every-
				       thing supported in this
				       release.	 This kernel sup-
				       ports SMP on systems with
				       more than one CPU.
			    _n_e_t_b_s_d_-_G_E_N_E_R_I_C___M_D_._g_z
				       A gzipped NetBSD	kernel
				       containing code for every-
				       thing supported in this
				       release.	 It also has a
				       RAM-disk	installer.  This
				       is the kernel you should
				       use when	you want to
				       install via netboot, from
				       a CD-R, or an HFS parti-
				       tion on Open Firmware 3
				       systems.
			    _n_e_t_b_s_d_-_I_N_S_T_A_L_L_._g_z
				       A gzipped NetBSD	kernel
				       containing code only for
				       Open Firmware 1.0.5,
				       1.1.22, 2.0.x, and 2.4
				       systems (i.e. those that
				       have floppy drives).  It
				       has a RAM-disk installer.
			    _n_e_t_b_s_d_-_I_N_S_T_A_L_L___6_0_1_._g_z
				       A gzipped NetBSD	kernel
				       containing code only for
				       PowerPC 601 machines, Open
				       Firmware	1.0.5, 1.1.22,
				       2.0.x, and 2.4 systems
				       (i.e. those that	have
				       floppy drives).	It has a
				       RAM-disk	installer.
			    _n_e_t_b_s_d_-_P_O_W_E_R_M_A_C___G_5_._g_z
				       A gzipped NetBSD	kernel
				       containing code only for
				       uniprocessor PowerPC 970FX
				       and 970MP machines.  It is
				       intended	for netbooting,
				       uncompressed, via TFTP.
			    _n_e_t_b_s_d_-_P_O_W_E_R_M_A_C___G_5_._M_P_._g_z
				       A gzipped NetBSD	kernel
				       containing code only for
				       multi-processor PowerPC
				       970FX and 970MP machines.
				       It is intended for net-
				       booting,	uncompressed, via
				       TFTP.
		   _s_e_t_s_/    macppc binary distribution sets; see
			    below.
     _i_n_s_t_a_l_l_a_t_i_o_n_/
		   _f_l_o_p_p_y_/_b_o_o_t_1_._f_s
		   _f_l_o_p_p_y_/_b_o_o_t_2_._f_s
			      macppc boot and installation floppy
			      images.  The first is the	boot-
			      loader and kernel.  The second
			      image has	the installation tools.
			      Only usable on models that ship
			      with a floppy drive (pre-Open
			      Firmware 3); see below.
		   _f_l_o_p_p_y_/_b_o_o_t_6_0_1___1_._f_s
		   _f_l_o_p_p_y_/_b_o_o_t_6_0_1___2_._f_s
			      Same as boot1.fs,	boot2.fs, except
			      for PowerPC 601 machines only.
		   _o_f_w_b_o_o_t_._x_c_f
			      macppc bootloader; see below.

     _B_i_n_a_r_y _d_i_s_t_r_i_b_u_t_i_o_n _s_e_t_s

     The NetBSD	macppc binary distribution sets	contain	the bina-
     ries which	comprise the NetBSD 10.1_STABLE	release	for
     macppc.  The binary distribution sets can be found	in the
     _m_a_c_p_p_c_/_b_i_n_a_r_y_/_s_e_t_s	subdirectory of	the NetBSD 10.1_STABLE
     distribution tree,	and are	as follows:

     bbaassee     The NetBSD 10.1_STABLE macppc bbaassee binary	distribu-
	      tion.  You _m_u_s_t install this distribution	set.  It
	      contains the base	NetBSD utilities that are neces-
	      sary for the system to run and be	minimally func-
	      tional.

     ccoommpp     Things needed for	compiling programs.  This set
	      includes the system include files	(_/_u_s_r_/_i_n_c_l_u_d_e)
	      and the various system libraries (except the shared
	      libraries, which are included as part of the bbaassee
	      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.

     ddeebbuugg    This distribution	set contains debug information
	      for all base system utilities.  It is useful when
	      reporting	issues with binaries or	during develop-
	      ment.  This set is huge, if the target disk is
	      small, do	not install it.

     eettcc      This distribution	set contains the system	configu-
	      ration files that	reside in _/_e_t_c and in several
	      other places.  This set _m_u_s_t be installed	if you
	      are installing the system	from scratch, but should
	      _n_o_t be used if you are upgrading.

     ggaammeess    This set includes	the games and their manual pages.

     kkeerrnn--GGEENNEERRIICC
	      This set contains	a NetBSD/macppc	10.1_STABLE
	      GENERIC kernel named _/_n_e_t_b_s_d.  You _m_u_s_t install
	      this distribution	set unless you have a PowerPC 601
	      machine.

     kkeerrnn--GGEENNEERRIICC__660011
	      This set contains	a NetBSD/macppc	10.1_STABLE
	      GENERIC_601 kernel named _/_n_e_t_b_s_d.	 You _m_u_s_t install
	      this distribution	set if you have	a PowerPC 601
	      machine.

     kkeerrnn--GGEENNEERRIICC..MMPP
	      This set contains	a NetBSD/macppc	10.1_STABLE
	      GENERIC.MP kernel, which will use	multiple proces-
	      sors (if present), named _/_n_e_t_b_s_d.

     mmaann      This set includes	all of the manual pages	for the
	      binaries and other software contained in the bbaassee
	      set.  Note that it does not include any of the man-
	      ual pages	that are included in the other sets.

     mmiisscc     This set includes	the system dictionaries, the
	      typesettable document set, and other files from
	      _/_u_s_r_/_s_h_a_r_e.

     mmoodduulleess  This set includes	kernel modules to add functional-
	      ity to a running system.

     rreessccuuee   This set includes	the statically linked emergency
	      recovery binaries	installed in _/_r_e_s_c_u_e.

     tteexxtt     This set includes	NetBSD's text processing tools,
	      including	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 compatibil-
     ity.  These sources are based on X.Org.  Binary sets for the
     X Window System are distributed with NetBSD.  The sets are:

     xxbbaassee    The basic	files needed for a complete X client
	      environment.  This does not include the X	servers.

     xxccoommpp    The extra	libraries and include files needed to
	      compile X	source code.

     xxddeebbuugg   This distribution	set contains debug information
	      for all X11 binaries.  It	is useful when reporting
	      issues with these	binaries or during development.
	      This set is huge,	if the target disk is small, do
	      not install it.

     xxffoonntt    Fonts needed by the X server and by X clients.

     xxeettcc     Configuration files for X	which could be locally
	      modified.

     xxsseerrvveerr  The X server.  This includes the modular Xorg
	      server.

     The macppc	binary distribution sets are distributed as
     gzipped tar files named with the extension	..ttggzz, e.g.
     _b_a_s_e_._t_g_z.

     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
     _b_e_l_o_w _t_h_e _c_u_r_r_e_n_t _d_i_r_e_c_t_o_r_y.  Therefore, if you want to
     extract the binaries into your system, i.e.  replace the
     system binaries with them,	you have to run	the ttaarr	--xxzzppff
     command from the root directory ( _/ ) of your system.

     _N_o_t_e_:  Each directory in the macppc binary	distribution also
	    has	its own	checksum files,	just as	the source dis-
	    tribution does.

   NNeettBBSSDD//mmaaccppppcc SSyysstteemm	RReeqquuiirreemmeennttss aanndd SSuuppppoorrtteedd DDeevviicceess
     Currently,	NetBSD/macppc requires the use of Open Firmware
     to	boot.  Open Firmware is	a command environment using the
     FORTH language.  The NetBSD kernel	uses Open Firmware to
     gather 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 plat-
     form.  Most machines introduced by	Apple and the clone-mak-
     ers after August 17, 1995 have Open Firmware and are sup-
     ported.

     Apple made	several	revisions of this Open Firmware	environ-
     ment, 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, but easier to
     set up for	NetBSD.

     The minimal configuration requires	16 MB of RAM and 160 MB
     of	disk space.  To	install	the entire system requires con-
     siderably more, plus space	for the	swap partition (usually
     the RAM size, unless you've got a lot of RAM).  To	use X,
     32MB of RAM is required.  NetBSD with 16 MB of RAM	is very
     slow.  Until you have around 32 MB	of RAM,	getting	more RAM
     is	more important than getting a faster CPU.

     _S_u_p_p_o_r_t_e_d _m_o_d_e_l_s

     Find your model from the list below and take note of its
     Open Firmware version:

     _O_p_e_n _F_i_r_m_w_a_r_e _1_._0_._5

	       ++oo   Apple PowerMacintosh	(7200, 7300, 7500, 7600,
		   8500, 8600, 9500, and 9600)
	       ++oo   Apple Workgroup Server 8550
	       ++oo   Power Computing (PowerCenter, PowerCenter Pro,
		   PowerCurve, PowerTower, PowerTower Pro, and
		   PowerWave)
	       ++oo   UMAX	(J700, S900)

     _O_p_e_n _F_i_r_m_w_a_r_e _1_._1_._2_2

	       ++oo   Apple Network Server	(500 and 700)

		   _N_o_t_e_:  Users	have reported that the NetBSD
			  kernel does not work well with the on-
			  board	MACE-based ethernet (the one that
			  requires an Apple AAUI dongle).  If
			  your system does not have the	Apple PCI
			  Ethernet Card, you may need to purchase
			  and install another ethernet card in
			  your Apple Network Server.

     _O_p_e_n _F_i_r_m_w_a_r_e _2_._0_._x

	       ++oo   Apple PowerBook (2400, 3400,	G3, and	G3
		   Series)
	       ++oo   Apple PowerMacintosh/Performa (4400,	54xx,
		   5500, 6300/160, 6360, 6400, and 6500)
	       ++oo   Apple PowerMacintosh	(G3 ``Beige'' models with
		   ATI RageII+:	Desktop, Mini Tower, and All-in-
		   One)
	       ++oo   APS Tech (M*Power 604e/200)
	       ++oo   Motorola StarMax (3000, 4000, 5000, and 5500)
	       ++oo   Power Computing (PowerBase)
	       ++oo   UMAX	(Apus 2000, Apus 3000, C500, and C600)

     _O_p_e_n _F_i_r_m_w_a_r_e _2_._4

	       ++oo   Apple PowerMacintosh	(G3 ``Beige'' models with
		   ATI Rage Pro: Desktop, Mini Tower, and All-in-
		   One)

     _O_p_e_n _F_i_r_m_w_a_r_e _3

	       ++oo   Apple original iBook, iBook SE, iBook (Dual
		   USB), iBook (Late 2001), iBook (16VRAM), iBook
		   (Opaque 16 VRAM), iBook (32 VRAM), iBook (14.1
		   LCD 32 VRAM), and iBook G4
	       ++oo   Apple iMac; Bondi Blue (Rev A and Rev B, 233
		   MHz), 5 Flavors (Rev	C and Rev D, 266 MHz and
		   333 MHz), iMac (Slot	Loading), iMac (Summer
		   2000), iMac (Early 2001), iMac (Summer 2001),
		   and iMac (USB 2.0)
	       ++oo   Apple original eMac and eMac	(ATI Graphics)
	       ++oo   Apple PowerBook (G3 Series (bronze keyboard)
		   and G3 (FireWire))
	       ++oo   Apple PowerBook (G4 (Titanium), G4 (Gigabit
		   Ethernet), G4 (DVI),	G4 (12-inch), G4
		   (17-inch), G4 (12-inch DVI),	PowerBook G4
		   (15-inch FW 800), PowerBook G4 (17-inch
		   1.33GHz/1.5GHz))
	       ++oo   Apple PowerMacintosh	G3 (Blue and White)
	       ++oo   Apple PowerMacintosh	(G4 (PCI), G4 (AGP), G4
		   (Gigabit Ethernet), G4 (Digital Audio), G4
		   (Quicksilver), G4 (Quicksilver 2002), G4 (Mir-
		   rored Drive Doors), G4 (FW 800), and	G4 Cube)
	       ++oo   Apple Mac Mini G4 (1.25GHz/1.42GHz/1.5GHz)
	       ++oo   Apple original Xserve and Xserve (Slot Load)

		   _N_o_t_e_:  Some newer G4	models may not run at
			  their	full CPU speed,	due to the fact
			  Open Firmware	starts the CPU at a
			  reduced frequency.
	       ++oo   Apple iMac G5, PowerMacintosh G5, Xserve G5

		   _N_o_t_e_:  G5 models are	supported as a 32-bit
			  port in bridge mode only.

     _U_n_s_u_p_p_o_r_t_e_d _m_o_d_e_l_s

	   ++oo   Systems with a PowerPC microprocessor, but lacking
	       Open Firmware
	       --   Apple PowerBook (1400, 2300,	and 5300)
	       --   Apple PowerMacintosh/Performa (52xx,	53xx,
		   62xx, and 63xx (except 6300/160 and 6360 which
		   are supported))
	       --   Apple PowerMacintosh/Performa (61xx,	71xx, and
		   81xx)
	       --   PowerComputing (Power 100 and Power 120)
	   ++oo   Systems with broken Open	Firmware (Twentieth
	       Anniversary Macintosh)
	   ++oo   Systems with a Motorola 68k microprocessor (these
	       systems are supported by	NetBSD/mac68k)
	   ++oo   Systems upgraded	from any of the	above (unless the
	       motherboard is replaced as part of the upgrade)

     _S_u_p_p_o_r_t_e_d _d_e_v_i_c_e_s

	   ++oo   CPU upgrades
	       --   Only	one CPU	in a multiprocessor system is
		   supported with the GENERIC kernel.  For the
		   601,	only one CPU is	supported with the
		   GENERIC_601 kernel.	All CPUs (except the 601)
		   are supported with the GENERIC.MP kernel.
	       --   Most	CPU upgrades are supported.  Some older
		   models will not automatically enable	the L2
		   and/or L3 caches on a G3 or G4 processor.  See
		   the FAQ entry
			 hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//ffaaqq..hhttmmll##ccppuu--uuppggrraaddee

	   ++oo   Ethernet
	       --   On-board 79C950-based MACE Ethernet interface
		   (_m_c)
	       --   On-board bmac Ethernet interface (_b_m)
	       --   On-board gmac Ethernet interface (_g_e_m)
	       --   Apple PCI Ethernet Card (option for Apple Net-
		   work	Server)	(_t_l_p)
	       --   Asante Mac 10/100 PCI Rev A,	part number
		   09-00169-01 (_t_l_p)
	       --   Farallon Fast EtherTX 10/100, part number
		   PN996L-TX (_t_l_p)
	       --   SMC Etherpower II (9432TX) (_e_p_i_c)
	       --   SMC 83c170 (_e_p_i_c)
	       --   3Com	3c905 (_e_x)
	       --   Intel EtherExpress PRO/10+ PCI LAN Adapter
		   (_f_x_p)
	       --   Realtek 8029	Ethernet (_n_e)
	       --   VIA Technologies VT86C926 (_n_e)
	       --   D-Link DFE-530TX+ (_r_t_k)
	       --   Realtek 8139	(_r_t_k)
	       --   Netgear FA-311 (_s_i_p)
	       --   Lite-On PNIC	(_t_l_p)
	       --   D-Link DFE-530TX (_v_r)
	       --   Many	other PCI and Cardbus Ethernet inter-
		   faces, such as Tulip-compatible (_t_l_p), 3Com
		   (_e_p), SMC (_e_p_i_c), Intel (_f_x_p), NE2000-compati-
		   ble (_n_e), and Realtek (_r_t_k)
	       --   Many	USB Ethernet interfaces	(_a_u_e, _c_u_e and
		   _k_u_e)

	   ++oo   Wireless
	       --   On-board AirPort or AirMac 802.11b (_w_i)
	       --   AT&T/Lucent WaveLan IEEE PCMCIA card	(_w_i)

	   ++oo   SCSI
	       --   On-board NCR	53c94 SCSI controller (_e_s_p)
	       --   On-board MESH SCSI controller (_m_e_s_h)
	       --   Adaptec PCI controllers 291x, 2920, 2930C,
		   294x, 295x, 39xx, 19160, 29160 and AIC-78xx
		   (_a_h_c)

		   _N_o_t_e_:  The 294x models are not bootable in
			  Open Firmware, even though they can
			  boot MacOS 9 and earlier.

	       --   AdvanSys 1200[A,B], 9xx[U,UA] SCSI controller
		   (_a_d_v)
	       --   AMD 53c974 (_p_c_s_c_p)
	       --   Apple 53c875	Ultra Wide SCSI	(shipped in some
		   Beige G3 models) (_n_c_r or _s_i_o_p)

		   _N_o_t_e_:  This card may	need a firmware	update to
			  boot NetBSD.	Use the	Mac OS X SCSI
			  Card Updater from
				hhttttpp::////ddooccss..iinnffoo..aappppllee..ccoomm//aarrttiiccllee..hhttmmll??aarrttnnuumm==2255117766
	       --   NCR/Symbios 53C8xx (_s_i_o_p or _e_s_i_o_p)
	       --   Many	other PCI SCSI controllers should work,
		   but no one has tried	them
	       --   Most	SCSI disk/tape/CD-ROM devices should work

	   ++oo   IDE
	       --   On-board IDE	controllers
	       --   Promise Ultra66 (_p_c_i_i_d_e) (this, and other PC-
		   based cards are not bootable	on macppc)
	       --   Acard ATP-850/860 based IDE controllers
		   (_p_c_i_i_d_e) (including the Acard AEC-6210/6260
		   and the Sonnet Tempo	ATA/66 cards)
	       --   Some	other PCI IDE controllers should work,
		   although no one has had much	success

	       --   Most	IDE disk/CD-ROM/ATAPI devices should work

	   ++oo   Input devices
	       --   Most	ADB keyboards, mice, trackballs, and
		   trackpads
	       --   Most	USB keyboards, mice, trackballs, and
		   trackpads
	       --   Most	PS/2 keyboards,	mice, and trackballs
		   (middle button on 3-button mice may not work)

	   ++oo   Video
	       --   On-board video on most models (_o_f_b)

		   _N_o_t_e_:  Several models have been reported to
			  not work with	NetBSD if the on-board
			  video	is in use, such	as the Performa
			  54xx,	6360, 6400, PowerComputing Power-
			  Center and PowerTower, and UMAX C600
			  and Apus 3000.  Also,	the video card
			  that shipped with the	PowerMacintosh
			  9500/150, 9500/180, and 9500/200 sys-
			  tems is reported to have the same prob-
			  lem.

	       --   PCI frame buffers which have	Open Firmware
		   support (ATI, IMS, Matrox, and NVIDIA have
		   several models which	work)
	       --   Valkyrie and	Platinum framebuffer drivers
		   (_v_a_l_k_y_r_i_e_f_b _a_n_d _p_l_a_t_i_n_u_m_f_b)
	       --   Full	wscons capabilities, such as virtual ter-
		   minals and color text are available.	 (Note
		   however that	switching between virtual termi-
		   nals	while running an X session may not be
		   supported by	all drivers.)

	   ++oo   Audio
	       --   On-board audio on most models (_a_w_a_c_s	or
		   _s_n_a_p_p_e_r)

	       --   USB audio devices (_u_a_u_d_i_o)

	       --   PCI audio cards, although only the Ensoniq
		   AudioPCI (_e_a_p) has been thoroughly tested

	   ++oo   Serial ports
	       NetBSD/macppc refers to the on-board serial ports
	       as (_t_t_y_0_0) and (_t_t_y_0_1).	Firmware uses the names
	       listed below.
	       --   On-board serial ports (the modem and	printer
		   ports) (_t_t_y_a	and _t_t_y_b)
		   _t_t_y_a	is the mini-DIN	8 serial port with the
		   `Modem' icon, and _t_t_y_b is has the `Printer'
		   icon.  Some models with internal modems have
		   the serial port with	the `Modem' icon covered
		   over, and the modem is _t_t_y_a.

		   _N_o_t_e_:  The on-board serial ports can	be used
			  for console (38400 bps, 8 bits, no par-
			  ity, 1 stop bit, no handshaking),
			  although many	users have reported prob-
			  lems trying to run ppp or other high
			  speed	serial applications

	       --   The Xserve serial port.

		   _N_o_t_e_:  This serial port can be used for con-
			  sole (57600 bps, 8 bits, no parity, 1
			  stop bit, no handshaking).  Use (_s_c_c_a)
			  for the Open Firmware	`input-device'
			  and `output-device' variables.  Alter-
			  natively, if you remove your video
			  card,	Open Firmware will default to
			  using	the serial port	for the	console.

	       --   The Gee Three Stealth Serial	Port, possibly
		   the Griffin Technology gPort

		   _N_o_t_e_:  These	serial ports can be used for con-
			  sole (57600 bps, 8 bits, no parity, 1
			  stop bit, no handshaking).  Use (_s_c_c_a)
			  for the Open Firmware	`input-device'
			  and `output-device' variables.

	       --   Some	USB, PCI, and Cardbus serial ports should
		   work, but no	one has	tried them

	   ++oo   USB devices
	       --   Most	MI USB devices should work (such as
		   disks, printers, input devices, SCSI	adapters,
		   and ethernet	interfaces)
			 hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ssuuppppoorrtt//hhaarrddwwaarree//uussbb..hhttmmll

	   ++oo   PCMCIA and Cardbus cards
	       --   Most	MI PCMCIA and Cardbus cards should work,
		   although very few have been tested with
		   NetBSD/macppc
			 hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ssuuppppoorrtt//hhaarrddwwaarree//ccaarrddbbuuss..hhttmmll
			 hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ssuuppppoorrtt//hhaarrddwwaarree//ppccmmcciiaa..hhttmmll

	   ++oo   PCI cards
	       --   Most	MI PCI cards should work, although very
		   few have been tested	with NetBSD/macppc
			 hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ssuuppppoorrtt//hhaarrddwwaarree//ppccii..hhttmmll

	       _N_o_t_e_:  While the	NetBSD kernel may support the
		      various Cardbus, PCI, PCMCIA, and	USB
		      devices you may have, Open Firmware does
		      _n_o_t unless it has	a specific Open	Firmware
		      ROM.  This means you cannot boot from these
		      devices.	Some Adaptec SCSI controllers
		      have bootable Open Firmware ROMs.

     _U_n_s_u_p_p_o_r_t_e_d _d_e_v_i_c_e_s

	   ++oo   Floppy disk

	       _N_o_t_e_:  Though NetBSD/macppc can boot from a
		      floppy, there is no kernel support yet

	   ++oo   Advanced	power management (cannot put system to
	       `sleep')

	   ++oo   On-board	video capture

	   ++oo   AirPort Extreme

	   ++oo   On-board	SATA controller	on G5 systems (these
	       machines	must be	netbooted)

     _S_u_p_p_o_r_t_e_d _b_o_o_t _d_e_v_i_c_e_s _a_n_d	_m_e_d_i_a

     Each version of Open Firmware supports different devices and
     media that	you may	boot from.  We define the terms
     ``bootable	media''	as the media (hard drive, floppy, CD-R,
     ethernet) that will be used to bootstrap your macppc system
     into NetBSD, and ``distribution sets'' or ``distribution
     media'' as	the media (hard	drive, CD-R, ethernet) that con-
     tains the files that will be installed to generate	a working
     NetBSD system onto	your destination media.

     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 pro-
     cedure.
	   hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//mmooddeellss..hhttmmll

   GGeettttiinngg tthhee NNeettBBSSDD SSyysstteemm oonn	ttoo UUsseeffuull MMeeddiiaa
     You should	wait to	decide where to	put the	NetBSD distribu-
     tion sets until you have figured out how you are going to
     boot your system.	Refer back to this section after you have
     done so.

     _N_o_t_e_:  Some Mac OS	ffttpp clients default to downloading files
	    in `ASCII' mode.  This will	render the NetBSD files
	    useless.  Make sure	to set your ftp	program	to down-
	    load in `binary' mode.

     Installation is supported from several media types, includ-
     ing:

	   ++oo   CD-ROM /	DVD / USB stick
	   ++oo   FTP
	   ++oo   Remote NFS partition
	   ++oo   Tape
	   ++oo   Existing	NetBSD or MacOS	X UFS partitions, if per-
	       forming an upgrade

     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.

     _C_D_-_R_O_M _/ _D_V_D _/ _U_S_B	_s_t_i_c_k  Find out	where the distribution
			       set files are on	the CD-ROM, DVD
			       or USB stick.  Likely locations
			       are _b_i_n_a_r_y_/_s_e_t_s and
			       _m_a_c_p_p_c_/_b_i_n_a_r_y_/_s_e_t_s.  (You only
			       need to know this if you	are mix-
			       ing installer and installation
			       media from different versions -
			       the installer will know the proper
			       default location	for the	sets it
			       comes with).

			       Proceed to the instructions on
			       installation.

     _F_T_P		       The preparations	for this instal-
			       lation/upgrade method are easy;
			       all you need to do is make sure
			       that there's an FTP site	from
			       which you can retrieve the NetBSD
			       distribution when you're	about to
			       install or upgrade.  If you don't
			       have DHCP available on your net-
			       work, you will need to know the
			       numeric IP address of that site,
			       and, if it's 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 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 upgrad-
			       ing.

     _N_F_S		       Place the NetBSD	distribution sets
			       you wish	to install into	a direc-
			       tory on an NFS server, and make
			       that directory mountable	by the
			       machine on which	you are
			       installing or upgrading NetBSD.
			       This will probably require modify-
			       ing the _/_e_t_c_/_e_x_p_o_r_t_s file on 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
			       you don't have DHCP available on
			       your network and	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 informa-
			       tion mentioned above, you can pro-
			       ceed to the next	step in	the
			       installation or upgrade process.
			       If you're installing NetBSD from
			       scratch,	go to the section on pre-
			       paring your hard	disk, below.  If
			       you're upgrading	an existing
			       installation, go	directly to the
			       section on upgrading.

     _T_a_p_e		       To install NetBSD from a	tape, you
			       need to make a tape that	contains
			       the distribution	set files, in
			       `tar' format.

			       If you're making	the tape on a
			       UNIX-like system, the easiest way
			       to do so	is probably something
			       like:

				     # ttaarr --ccff _t_a_p_e___d_e_v_i_c_e
				     _d_i_s_t___s_e_t_s

			       where _t_a_p_e___d_e_v_i_c_e is the	name of
			       the tape	device that represents
			       the tape	drive you're using.  This
			       might be	_/_d_e_v_/_r_s_t_0, or something
			       similar,	but it will vary from
			       system to system.  In the above
			       example,	_d_i_s_t___s_e_t_s is a list of
			       filenames corresponding to the
			       distribution sets that you wish to
			       place on	the tape.  For instance,
			       to put the kkeerrnn--GGEENNEERRIICC,,	bbaassee,, and
			       eettcc distributions on tape (the
			       absolute	minimum	required for
			       installation), you would	do the
			       following:

				     # ccdd ......//NNeettBBSSDD--1100..11__SSTTAABBLLEE
				     # ccdd mmaaccppppcc//bbiinnaarryy
				     # ttaarr --ccff _t_a_p_e___d_e_v_i_c_e
				     kkeerrnn--GGEENNEERRIICC..ttggzz bbaassee..ttggzz
				     eettcc..ttggzz

			       _N_o_t_e_:  You still	need to	fill in
				      _t_a_p_e___d_e_v_i_c_e in the example.

			       Once you	have the files on the
			       tape, 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 installa-
			       tion, go	directly to the	section
			       on upgrading.

   PPrreeppaarriinngg yyoouurr SSyysstteemm ffoorr NNeettBBSSDD iinnssttaallllaattiioonn
     _P_r_e_p_a_r_e _y_o_u_r_s_e_l_f

     Take a deep breath.

     Good.  Now, make sure you are reading the PostScript or HTML
     version of	this document, as the _._t_x_t and _._m_o_r_e versions
     lack important formatting information that	will prevent you
     from following the	twisted	path documented	below.	OK, good.
     Now, print	out this document.

     While it's	printing, get some coffee, relax a bit,	and men-
     tally 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:
	   hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//ffaaqq..hhttmmll##mmaaccooss--nneewwbbiiee

     It's done printing?  Fine,	time to	get started.

     The recommended installation procedure is as follows:

     1.	  Go to	the NetBSD/macppc model	support	page and look up
	  your model information and issues (I can't stress this
	  enough times).
		hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//mmooddeellss..hhttmmll

     2.	  Spend	about 15 minutes and read through this document
	  from this point onward.  There will be many pages of
	  instructions that apply to Open Firmware versions that
	  you do not have.  Throw them out.  Do	not read them --
	  at best you will be confused,	at worst you may damage
	  your system, requiring repairs.

     3.	  Now create your bootable media and media for the dis-
	  tribution sets.

     4.	  Prepare your machine,	depending on the instructions for
	  your model (for example: partition your drive, download
	  and run System Disk, or hook up a serial console).

     5.	  Boot into Open Firmware and verify that it has the ver-
	  sion of Open Firmware	you think it does.  Also make
	  sure that the	other variables	are set	correctly.

     6.	  Figure out the correct boot command and boot your
	  machine from the bootable media you just created.  If
	  you're having	trouble, be sure to read the section on
	  _C_o_m_m_o_n _P_r_o_b_l_e_m_s _a_n_d _E_r_r_o_r _M_e_s_s_a_g_e_s

     7.	  Celebrate!  The worst	is over, but you've still got
	  some work to do.  Take a break, maybe	more coffee,
	  maybe	a quick	walk around the	block, whatever	turns
	  your fancy.

     8.	  Now use the installer	to install the distribution sets
	  onto your system and do some initial configuration.

     9.	  Figure out how to boot from the installed partition.
	  Boot into NetBSD for the first time.

     10.  You may then boot into Open Firmware and set it to
	  always boot your favorite operating system.

     11.  Configure to your preferences, install your favorite
	  packages, and	have fun with your new NetBSD/macppc
	  machine!

     _N_o_t_e_:  You	really actually	truly do need to follow	the pro-
	    cedure listed in this document in the order	that we
	    describe.  These systems are rather	tricky to boot
	    for	the novice and expert alike.  Once you cross off
	    the	sections that don't apply to you, it will make
	    more sense.

     _N_o_t_e_:  If the instructions	in a subsection	below do not
	    apply to _a_l_l versions of Open Firmware.  There will
	    be a line listing which versions of	Open Firmware
	    they apply to, such	as:
	    (Open Firmware 1.0.5, Open Firmware	1.1.22,	Open
	    Firmware 2.0.x, Open Firmware 2.4, Open Firmware 3)
     If	you do not have	an Open	Firmware 3 system, skip	down to
     _P_r_e_p_a_r_i_n_g _y_o_u_r _O_p_e_n _F_i_r_m_w_a_r_e _1_._x _o_r _2_._x _S_y_s_t_e_m _f_o_r	_N_e_t_B_S_D

   PPrreeppaarriinngg yyoouurr OOppeenn FFiirrmmwwaarree	33 SSyysstteemm ffoorr NNeettBBSSDD
     _U_p_d_a_t_i_n_g _y_o_u_r _B_o_o_t_R_O_M

     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	_n_o_t 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 Support Downloads' website at
	   hhttttpp::////ssuuppppoorrtt..aappppllee..ccoomm//ddoowwnnllooaaddss//
     and search	for `firmware' and install the most recent ver-
     sion for your model. For most G3 and G4 models, you will
     need to run the FirmWare updater from MacOS 9.

     _N_o_t_e_:  If you accidentally	change the llooaadd--bbaassee or	rreeaall--bbaassee
	    Open Firmware variables and	reset your machine you
	    will, in effect, rewrite the BootROM with garbage.
	    This will permanently damage your machine.	We recom-
	    mend not doing this.

     _N_o_t_e_:  The	most recent BootROMs available (4.1.7 and later)
	    are	a little picky about RAM.  Initially, some Power-
	    Macintosh G3 users found that their	third-party RAM
	    had	been disabled, but the RAM vendors brought their
	    RAM	up to spec and it hasn't been much of an issue
	    since then.

	    There is one report	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
	    _w_d_c_0_:_0_:_1_: _l_o_s_t _i_n_t_e_r_r_u_p_t problems.

     _G_e_t_t_i_n_g _t_o	_O_p_e_n _F_i_r_m_w_a_r_e _3

     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 > sseetteennvv aauuttoo--bboooott?? ffaallssee

     Alternatively, if you are currently running MacOS X or
     Darwin, you can use the nnvvrraamm command to set this variable
     before rebooting.

	   # nnvvrraamm aauuttoo--bboooott\\??==ffaallssee

     You will need to escape the question-mark or enclose the
     whole nnvvrraamm argument in double-quotes to prevent your shell
     from trying to interpret it.

     _S_e_t_t_i_n_g _u_p	_O_p_e_n _F_i_r_m_w_a_r_e _3	_t_o _b_o_o_t	_N_e_t_B_S_D

     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:
	   hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//ffaaqq..hhttmmll##ooffww--aacccceessss
	   hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//ffaaqq..hhttmmll##ooffww--vvaarriiaabblleess

     Double-check your Open Firmware version:

	   0 > ddeevv //ooppeennpprroomm
	   0 > ..pprrooppeerrttiieess
	   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 > ddeevv eenneett
	   0 > ..pprrooppeerrttiieess
	   [...]
	   local-mac-address   CCCCCCCC	CCCC
	   [...]

     _N_o_t_e_:  Some Open Firmware 3 machines have their MAC address
	    stored incorrectly (little-	vs. big-endian problem).
	    If you look	up your	MAC address in MacOS, it will be
	    different than what	Open Firmware 3	uses to	contact
	    your netboot server.  Your machine will still work,
	    but	its MAC	address	may conflict with another ether-
	    net	device on your network.

     You can check your	Open Firmware settings with the	_p_r_i_n_t_e_n_v
     command:

	   0 > pprriinntteennvv
	   -------------- 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

     _A_v_a_i_l_a_b_l_e _B_o_o_t _M_e_d_i_a

     Open Firmware is capable of booting from a	variety	of media
     (such as hard drives, CD-ROMs, and	ethernet).  Open Firmware
     is	able to	boot files from	a variety of file systems (such
     as	ISO9660, HFS, HFS+, and	MS-DOS FAT).  Unfortunately, Open
     Firmware is _n_o_t able to directly boot from	the NetBSD file
     system (FFS) or Apple's BSD-based file system (UFS), so we
     must put the bootloader in	a location that	Open Firmware is
     capable of	understanding.

     Therefore,	to boot	the NetBSD kernel, Open	Firmware must
     first load	a `bootloader' (_o_f_w_b_o_o_t_._x_c_f) which knows how to
     load the NetBSD kernel.

     _N_o_t_e_:  Despite a note to the contrary in earlier releases
	    that _o_f_w_b_o_o_t_._e_l_f is	obsoleted, that	is no longer the
	    case.  It has been observed	that on	some newish
	    machines (notably at least some Mac	Minis),	use of
	    _o_f_w_b_o_o_t_._x_c_f	will result in an early	kernel panic when
	    loading the	GENERIC	kernel from disk.  For these
	    machines it	appears	to be a	workaround to use
	    _o_f_w_b_o_o_t_._e_l_f	instead	of _o_f_w_b_o_o_t_._x_c_f as the boot
	    loader.  The root cause for	this problem has unfortu-
	    nately yet to be found.

     The following bootable media are available	for loading the
     bootloader:

	   ++oo   _H_F_S _o_r _H_F_S_+ _f_i_l_e	_s_y_s_t_e_m

	       This method loads _o_f_w_b_o_o_t_._x_c_f from an HFS or HFS+
	       partition which then loads the kernel from an
	       acceptable location.  The kernel	(compressed or
	       non-compressed) may be on an HFS	or HFS+	parti-
	       tion.  Due to Open Firmware pickiness, it must be
	       on the same partition as	_o_f_w_b_o_o_t_._x_c_f.

	   ++oo   _M_S_-_D_O_S _f_i_l_e _s_y_s_t_e_m

	       In this method, Open Firmware loads the
	       _o_f_w_b_o_o_t_._x_c_f bootloader from an MS-DOS file system.
	       It may then load	a NetBSD kernel	from the same MS-
	       DOS file	system.	 This has only been thoroughly
	       tested on floppy	disks, but may work on Zip disks
	       or FDISK-formatted hard drives.	This does not
	       work for	MS-DOS partitions on a hard drive with an
	       Apple Partition Map.

	   ++oo   _E_t_h_e_r_n_e_t	_(_n_e_t_w_o_r_k _b_o_o_t_)

	       You can run your	entire system diskless or netboot
	       only the	files necessary	to boot	(i.e. the boot-
	       loader and the installation kernel).  You must
	       have root access	for the	UNIX-like netboot server,
	       which must be on	the same subnet	as your
	       NetBSD/macppc machine.

	       _N_o_t_e_:  You must use your	on-board ethernet device
		      for netbooting.  While there may be some
		      PCI or Cardbus ethernet interfaces with
		      Open Firmware ROMs, no one has reported
		      success netbooting using these devices

	   ++oo   _H_y_b_r_i_d _H_F_S_/_I_S_O_9_6_6_0 _C_D_-_R_O_M _f_i_l_e _s_y_s_t_e_m

	       Load the	_o_f_w_b_o_o_t_._x_c_f 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.

	       _N_o_t_e_:  Open Firmware can	only open files	on the
		      first session of a multi-session CD-R

     Once the bootloader is loaded, it can open	the kernel from
     one of the	following sources:

	   ++oo   _E_t_h_e_r_n_e_t	_(_N_F_S_)

	   ++oo   _N_e_t_B_S_D _F_F_S _f_i_l_e _s_y_s_t_e_m

	   ++oo   _M_a_c_O_S _X _U_F_S _f_i_l_e	_s_y_s_t_e_m

	   ++oo   _H_F_S _o_r _H_F_S_+ _f_i_l_e	_s_y_s_t_e_m

	   ++oo   _I_S_O_9_6_6_0 _C_D_-_R_O_M _f_i_l_e _s_y_s_t_e_m

	   ++oo   _M_S_-_D_O_S _f_i_l_e _s_y_s_t_e_m

     The boot CD image provided	has both a `partition zero' boot-
     loader and	_o_f_w_b_o_o_t_._x_c_f on a hybrid	partition so it	can be
     booted on all Open	Firmware versions.  It also has	an
     ISO9660 file system with an installation kernel and the dis-
     tribution sets.

     _P_a_r_t_i_t_i_o_n_i_n_g _y_o_u_r _h_a_r_d _d_r_i_v_e _f_o_r _N_e_t_B_S_D

     You must have at least one	disk that was partitioned before
     running the NetBSD	installer.

     This is the drive that will have the bootloader,
     _o_f_w_b_o_o_t_._x_c_f.  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.

     This section describes how	to make	a single disk usable by
     both MacOS	and NetBSD -- this is necessary	for machines
     which have	only one hard drive (such as the eMac, iBook,
     iMac, PowerBook, and PowerMacintosh Cube systems).	 If you
     do	not want MacOS you must	still follow this procedure, but
     create only a small HFS+ partition	(large enough for the
     bootloader).

     There are two partitioning	tools available	for
     NetBSD/macppc, disklabel(8) and pdisk(8).	The former is
     used in the NetBSD	ssyyssiinnsstt	installer, and will render your
     disk unusable by MacOS.  It will also prevent Open	Firmware
     3 machines	from booting from that disk.  When running the
     installer,	you will need to use the installer's ``Re-install
     sets'' option to skip the ddiisskkllaabbeell step.

     Do	not use	ddiisskkllaabbeell or ``Re-install sets'' unless	you will
     use one drive for NetBSD only and have another drive which
     will have the bootloader.

     The process is more fully detailed	in the Partitioning HOW-
     TO:
	   hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//ppaarrttiittiioonniinngg..hhttmmll

     You can create a partition	map with pdisk(8), but the disk
     will not be usable	with MacOS 9 and earlier.  If this is a
     concern, you will need to use Apple's Drive Setup or Disk
     Utility.

     If	you are	using Apple's Drive Setup tool,	make sure you
     have version 1.8.1	or later.  This	tool only runs under
     MacOS 9 and earlier.  Drive Setup will erase the contents of
     your drive	-- it does not preserve	data from any of your
     partitions.

     Apple's Disk Utility only runs under MacOS	X 10.0.0 and
     later.  Make sure you click the ``Install Mac OS 9	Disk
     Drivers'' checkbox.  Also,	keep in	mind that Disk Utility
     does _n_o_t create the partitions that NetBSD/macppc requires.
     After creating the	initial	partition map with Disk	Utility,
     you will need to use the NetBSD ppddiisskk to change the parti-
     tion types.  Also,	Disk Utility will erase	the contents of
     your drive	-- it does not preserve	data from any of your
     partitions.

     ppddiisskk is the most flexible	(and most difficult to use) par-
     titioning tool available.	It runs	on almost all OSes that
     macppc machines support.  Download	it:
	   hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD//aarrcchh//mmaaccppppcc//nneettbbssdd--ppddiisskk//
	   hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD//aarrcchh//mmaaccppppcc//mmaaccooss--uuttiillss//ppddiisskk..sseeaa..hhqqxx

     There is built-in help describing how it works.  When it
     asks you to enter the ``Type of partition'', use
     Apple_UNIX_SVR2 for NetBSD	partitions, Apple_HFS for HFS and
     HFS+ partitions, and Apple_UFS for	UFS partitions.

     After you've written the partition	map with ppddiisskk,	you will
     need to create the	file systems.  Use newfs(8) and	mount(8)
     for NetBSD	file systems, and hhffssttoooollss to create and mount
     HFS file systems.
	   hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD//ppaacckkaaggeess//ppkkggssrrcc//ssyyssuuttiillss//hhffssuuttiillss//

     Make the following	partitions:

	   _H_F_S or _H_F_S_+		     Must be large enough to hold
				     the bootloader, over 100 KB.
				     May be as large as	you
				     desire for	MacOS usage.

	   _A_/_U_X	_R_o_o_t		     Must be at	least 20 MB.
				     Alternatively, you	may
				     decide to use one partition
				     for your entire NetBSD
				     installation, in which case
				     it	should be at least 200
				     MB.  NetBSD interprets an
				     _A_/_U_X _R_o_o_t partition as the
				     first partition (_a) on the
				     disk.  This partition is not
				     readable from MacOS.

	   _A_/_U_X	_S_w_a_p		     Any size.	The recommenda-
				     tion is your RAM size,
				     although this is not
				     strictly necessary	for
				     machines with a lot of RAM.
				     NetBSD interprets an _A_/_U_X
				     _S_w_a_p partition as the second
				     partition (_b) on the disk.
				     This partition is not read-
				     able from MacOS.

	   _A_/_U_X	_U_s_e_r and _A_/_U_X _F_r_e_e_1  Use these for any additional
				     partitions	you may	want to
				     use under NetBSD, such as
				     _/_u_s_r (at least 200	MB),
				     _/_h_o_m_e, _/_u_s_r_/_l_o_c_a_l,	or
				     _/_u_s_r_/_p_k_g.	NetBSD interprets
				     these partitions as normal
				     NetBSD-style partitions.
				     These partitions are not
				     readable from MacOS.

	   _H_F_S			     Any size.	You may	want to
				     leave an additional parti-
				     tion available to transfer
				     files between MacOS and
				     NetBSD.  If would like to
				     create such a partition,
				     then see the Partitioning
				     HOW-TO.
					   hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//ppaarrttiittiioonniinngg..hhttmmll##mmssddooss

	   _U_F_S			     Any size.	_U_F_S partitions
				     are not readable from MacOS
				     versions prior to X 10.0.0.
				     If	you use	an _U_F_S partition
				     as	your root, then	it may
				     not be recognized by the
				     NetBSD kernel as the first
				     partition (_a) on the disk.
				     You will need to compile a
				     new kernel	with the root
				     partition explicitly defined
				     to	be the _U_F_S partition.

     Now would be a good time to use ppddiisskk to determine	the par-
     tition numbers for	your bootloader	and kernel.

     _P_r_e_p_a_r_i_n_g _t_h_e _O_p_e_n	_F_i_r_m_w_a_r_e _3 _B_o_o_t_a_b_l_e _M_e_d_i_a

     The purpose of this section is to prepare the media from
     which your	system will boot the installer.	 We'll describe
     how to put	the files in the right places on your disk(s) or
     netboot server and	prepare	it for use on your system.

     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 dis-
     tribution sets on the diskless server.

     To	get the	distribution sets onto appropriate media, see the
     above section entitled _G_e_t_t_i_n_g _t_h_e	_N_e_t_B_S_D _S_y_s_t_e_m _o_n _t_o
     _U_s_e_f_u_l _M_e_d_i_a.  You	may want to get	the distribution sets
     when you create the bootable media.

     _N_o_t_e_:  Some MacOS ffttpp clients default to downloading files
	    in `ASCII' mode.  This will	render the NetBSD files
	    useless.  Make sure	to set your ftp	program	to down-
	    load in `binary' mode.

     What follows are the steps	to create different types of
     bootable media for	the NetBSD install kernel. You should
     only need to create one of	these to get your system to boot
     the installer

     ++oo	 _C_r_e_a_t_i_n_g _t_h_e _N_e_t_B_S_D_/_m_a_c_p_p_c _C_D_-_R

	 Go to one of the NetBSD mirror	sites and download the
	 CD-R image _N_e_t_B_S_D_-_1_0_._1___S_T_A_B_L_E_-_m_a_c_p_p_c_._i_s_o from the
	 _p_u_b_/_N_e_t_B_S_D_/_i_m_a_g_e_s directory.
	       hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//mmiirrrroorrss//##iissoo

	 --   _F_r_o_m _a_n _U_N_I_X_-_l_i_k_e _m_a_c_h_i_n_e

	     Get and install cdrecord.	NetBSD users should
	     install it	from the package collection.  Other
	     UNIX-like systems should get it from the official
	     website:
		   hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD//ppaacckkaaggeess//ppkkggssrrcc//ssyyssuuttiillss//ccddrrttoooollss//
		   hhttttpp::////wwwwww..ffookkuuss..ggmmdd..ddee//rreesseeaarrcchh//cccc//gglloonnee//eemmppllooyyeeeess//jjooeerrgg..sscchhiilllliinngg//pprriivvaattee//ccddrreeccoorrdd..hhttmmll

		   # ccddrreeccoorrdd --vv ssppeeeedd==44 ddeevv==//ddeevv//ccdd11cc NNeettBBSSDD--1100..11__SSTTAABBLLEE--mmaaccppppcc..iissoo

	     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
	     _/_d_e_v_/_c_d_1_d).

	 --   _F_r_o_m _a _M_a_c_O_S _m_a_c_h_i_n_e _(_u_s_i_n_g _T_o_a_s_t_)

	     1.	  Click	the `Other' button in the main window.

	     2.	  Open the contextual menu on the `Other' button
		  and select `Disk Image'

	     3.	  Click	the `Select' button and	select the disk
		  image	you downloaded.

	     4.	  Click	the `Record' button

	 Skip forward to _I_n_s_t_a_l_l_i_n_g _t_h_e	_N_e_t_B_S_D _S_y_s_t_e_m

     ++oo	 _P_r_e_p_a_r_i_n_g _a_n _H_F_S _o_r _H_F_S_+ _p_a_r_t_i_t_i_o_n

	 Place _o_f_w_b_o_o_t_._x_c_f and the installation	kernel
	 _n_e_t_b_s_d_-_G_E_N_E_R_I_C___M_D_._g_z 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 _I_n_s_t_a_l_l_i_n_g _t_h_e	_N_e_t_B_S_D _S_y_s_t_e_m

     ++oo	 _P_r_e_p_a_r_i_n_g _a _c_u_s_t_o_m _h_y_b_r_i_d _H_F_S_/_I_S_O_9_6_6_0 _C_D_-_R

	 This section describes	how to create your own bootable
	 NetBSD/macppc CD-R. We	recommend that you use the offi-
	 cial NetBSD/macppc-10.1_STABLE	CD-R image, as described
	 in the	section	above.

	 Place _o_f_w_b_o_o_t_._x_c_f and the installation	kernel
	 _n_e_t_b_s_d_-_G_E_N_E_R_I_C___M_D_._g_z at the top level of the CD.  Make
	 sure that the bootloader is present on	the HFS	parti-
	 tion, and the kernel is on both the ISO9660 and HFS par-
	 titions.  Due to restrictions in the way that Open
	 Firmware deals	with ISO filenames, you	may wish to name
	 your kernel _n_e_t_b_s_d_._g_z.	 You may also place the
	 NetBSD	10.1_STABLE distribution sets on the ISO9660 par-
	 tition	(not only on the HFS partition).

	 --   _F_r_o_m _a_n _U_N_I_X_-_l_i_k_e _m_a_c_h_i_n_e

	     Get and install mkisofs.  This is now part	of the
	     cdrecord package.	NetBSD users should install it
	     from the package collection.  Other UNIX-like sys-
	     tems should get it	from the official website:
		   hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD//ppaacckkaaggeess//ppkkggssrrcc//ssyyssuuttiillss//ccddrrttoooollss//
		   hhttttpp::////wwwwww..ffookkuuss..ggmmdd..ddee//rreesseeaarrcchh//cccc//gglloonnee//eemmppllooyyeeeess//jjooeerrgg..sscchhiilllliinngg//pprriivvaattee//ccddrreeccoorrdd..hhttmmll

		   # mmkkiissooffss --oo	NNeettBBSSDD--1100..11__SSTTAABBLLEE--mmaaccppppcc..iissoo --hhffss --ppaarrtt --ll --JJ --rr --LL --NN	//ccddssoouurrcceess
		   # ccddrreeccoorrdd --vv ssppeeeedd==44 ddeevv==//ddeevv//ccdd11cc NNeettBBSSDD--1100..11__SSTTAABBLLEE--mmaaccppppcc..iissoo

	     You will need to substitute the correct speed for
	     your CD writer, and the correct device for	your sys-
	     tem (for i386 it would be _/_d_e_v_/_c_d_1_d).

	     See the NetBSD Bootable CD-ROM HOW-TO for more
	     detail:
		   hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ddooccss//bboooottccdd..hhttmmll

	 --   _F_r_o_m _a _M_a_c_O_S _m_a_c_h_i_n_e _(_u_s_i_n_g _T_o_a_s_t_)

	     1.	  Click	the `Data' button in the main window

	     2.	  Pick `Mac OS and PC (Hybrid) CD' from	the popup
		  menu between the four	buttons	and the	file and
		  folder area.

	     3.	  Drag _i_n_s_t_a_l_l_a_t_i_o_n_/_o_f_w_b_o_o_t_._x_c_f	and
		  _b_i_n_a_r_y_/_k_e_r_n_e_l_/_n_e_t_b_s_d_-_G_E_N_E_R_I_C___M_D_._g_z into the
		  window.  You may also	want to	drag the
		  NetBSD 10.1_STABLE distribution sets to this
		  window as well.

	     4.	  Click	the `Record' button

	 Skip forward to _I_n_s_t_a_l_l_i_n_g _t_h_e	_N_e_t_B_S_D _S_y_s_t_e_m

     ++oo	 _C_r_e_a_t_i_n_g _a_n _M_S_-_D_O_S _d_i_s_k

	 Open Firmware 3 cannot	boot from a floppy disk, but you
	 can still create a bootable Zip disk with this	method.

	 1.   First, make sure you have	done a low-level format
	      on the disk.  A bad disk can produce Open	Firmware
	      errors similar to	other problems.

	 2.   Mount the	disk on	your computer.
	      --	  Insert it into a Windows or DOS machine.
	      --	  Use `File Exchange or	`PC Exchange'' with MacOS
		  versions prior to X 10.0.0
	      --	  Use mount_msdos(8) on	any UNIX-like machine.

	 3.   Copy _n_e_t_b_s_d_-_I_N_S_T_A_L_L_._g_z and _o_f_w_b_o_o_t_._x_c_f to	the disk.
	      PowerPC 601 machines need	to use
	      _n_e_t_b_s_d_-_I_N_S_T_A_L_L___6_0_1_._g_z.

	 4.   Rename _n_e_t_b_s_d_-_I_N_S_T_A_L_L_._g_z to _n_e_t_b_s_d_._g_z, since Open-
	      Firmware can't deal with MS-DOS filenames	longer
	      than eight characters.

	 Skip forward to _I_n_s_t_a_l_l_i_n_g _t_h_e	_N_e_t_B_S_D _S_y_s_t_e_m

     ++oo	 _P_r_e_p_a_r_i_n_g _t_h_e _n_e_t_b_o_o_t _s_e_r_v_e_r

	 1.   Introduction

	      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 man-
	      ual 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 con-
	      figure the netboot services on a variety of plat-
	      forms:
		    hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ddooccss//nneettwwoorrkk//nneettbboooott//

	      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 execut-
	      ing 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 exe-
	      cuting 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, _o_f_w_b_o_o_t_._x_c_f.  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
	      _/_e_x_p_o_r_t_/_c_l_i_e_n_t_/_r_o_o_t.  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.

	 2.   dhcpd(8) in bootpd(8) compatible mode

	      Put the following	lines in your _/_e_t_c_/_d_h_c_p_d_._c_o_n_f
	      (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;  # master DHCP server for this subnet
				    #
		    subnet 192.168.1.0 netmask 255.255.255.0 {
				    # Which network interface to listen	on.
				    # The zeros	indicate the range of addresses
				    # that 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";

				    #
				    # The host address of the NFS server. This is mandatory for
				    # NetBSD kernels even it's the same	host as	the DHCP server.
		    #
				    # macppc machines will look	for their bootloader,
				    # ofwboot.xcf, on the next-server as well.
				    #
				    next-server	server.test.net;
			    }
		     #you may paste another "host" entry here for additional
		     #clients on this network
		    }

	      You will need to make sure that the _d_h_c_p_d_._l_e_a_s_e_s
	      file exists.

		    # ttoouucchh //vvaarr//ddbb//ddhhccppdd..lleeaasseess

	      You will need to start the ddhhccppdd.	 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 NetBSD, you can achieve this with:

		    # //eettcc//rrcc..dd//ddhhccppdd rreessttaarrtt

	 3.   tftpd(8)

	      The default configuration	of the TFTP server is to
	      run in a chroot(8) environment in	the _/_t_f_t_p_b_o_o_t
	      directory.  Thus,	the first order	of business is to
	      create this directory:

		    # mmkkddiirr --pp //ttffttppbboooott

	      Next, edit _/_e_t_c_/_i_n_e_t_d_._c_o_n_f 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
	      NetBSD, you can achieve this with:

		    # //eettcc//rrcc..dd//iinneettdd rreessttaarrtt

	      Now, you need to copy the	bootloader for your
	      macppc machine to	_/_t_f_t_p_b_o_o_t.  Get	ofwboot.xcf(8)
	      from the _i_n_s_t_a_l_l_a_t_i_o_n directory of the distribu-
	      tion.

		    # ccpp ooffwwbboooott..xxccff //ttffttppbboooott
	      Just to be sure, let's make everything readable.

		    # cchhmmoodd --RR aa++rrXX //ttffttppbboooott

	      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 _/_v_a_r_/_l_o_g_/_m_e_s_s_a_g_e_s saying: `tftpd:
	      write: Host is down'.  If	this is	the case, you may
	      need to force the	server to map your client's eth-
	      ernet address to its IP address:

		    # aarrpp --ss cclliieenntt CCCC::CCCC::CCCC::CCCC::CCCC::CCCC

	 4.   nfsd(8), mountd(8), and rpcbind(8)

	      Now your system should be	able to	load the boot-
	      strap program and	start looking for the kernel.
	      Let's set	up the NFS server.  Create the directory
	      you are exporting	for the	netboot	client:

		    # mmkkddiirr --pp //eexxppoorrtt//cclliieenntt//rroooott

	      Put the following	line in	_/_e_t_c_/_e_x_p_o_r_t_s 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	NetBSD,	you can	achieve	this
	      with:

		    # //eettcc//rrcc..dd//rrppccbbiinndd	ssttaarrtt
		    # //eettcc//rrcc..dd//nnffssdd ssttaarrtt
		    # //eettcc//rrcc..dd//mmoouunnttdd rreessttaarrtt

	 5.   NetBSD kernel and	installation tools

	      Now, if you place	a kernel named _n_e_t_b_s_d in
	      _/_e_x_p_o_r_t_/_c_l_i_e_n_t_/_r_o_o_t your client should boot the
	      kernel.  If you are netbooting the installer, use
	      _b_i_n_a_r_y_/_k_e_r_n_e_l_/_n_e_t_b_s_d_-_G_E_N_E_R_I_C___M_D_._g_z (this has the
	      installation tools in a RAM disk).  Also,	copy the
	      distribution files to the	client's root directory.

	      _N_o_t_e_:  Some combinations of Open Firmware	version
		     and _o_f_w_b_o_o_t_._x_c_f version have trouble loading
		     compressed	kernels.  If you have trouble
		     loading a kernel, try uncompressing it with
		     gunzip(1)

		    # ccpp **..ttggzz //eexxppoorrtt//cclliieenntt//rroooott
		    # gguunnzziipp nneettbbssdd--GGEENNEERRIICC__MMDD..ggzz
		    # mmvv nneettbbssdd--GGEENNEERRIICC__MMDD //eexxppoorrtt//cclliieenntt//rroooott//nneettbbssdd

	      If you are running your macppc diskless, simply use
	      _b_i_n_a_r_y_/_k_e_r_n_e_l_/_n_e_t_b_s_d_-_G_E_N_E_R_I_C_._g_z.

	 6.   Client file system

	      You can skip this	step if	you do not plan	to run
	      your client diskless after installation.	Other-
	      wise, 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.  See _f_o_r _d_e_t_a_i_l_s_:
		    hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ddooccss//nneettwwoorrkk//nneettbboooott//nnffss..hhttmmll.
	      --	  Extracting distribution sets

			# ccdd //eexxppoorrtt//cclliieenntt//rroooott
			# ttaarr --xxppzzff //ppaatthh//ttoo//ffiilleess//bbaassee..ttggzz
			# ttaarr --xxppzzff //ppaatthh//ttoo//ffiilleess//eettcc..ttggzz

		  Continue with	the other non-essential	distribu-
		  tion sets if desired.

	      --	  Set up swap

			# mmkkddiirr	//eexxppoorrtt//cclliieenntt//rroooott//sswwaapp
			# dddd iiff==//ddeevv//zzeerroo ooff==//eexxppoorrtt//cclliieenntt//sswwaapp bbss==44kk ccoouunntt==44kk
			# eecchhoo ''//eexxppoorrtt//cclliieenntt//sswwaapp --mmaapprroooott==rroooott::wwhheeeell	cclliieenntt..tteesstt..nneett'' >>>> //eettcc//eexxppoorrttss
			# //eettcc//rrcc..dd//mmoouunnttdd rreessttaarrtt
		  This creates a 16 MB swap file and exports it
		  to the client.

	      --	  Create device	nodes

			# ccdd //eexxppoorrtt//cclliieenntt//rroooott//ddeevv
			# ..//MMAAKKEEDDEEVV aallll

		  This procedure only works on NetBSD hosts.

	      --	  Set up the client's fstab(5)

		  Create a file	in _/_e_x_p_o_r_t_/_c_l_i_e_n_t_/_r_o_o_t_/_e_t_c_/_f_s_t_a_b
		  with the following lines:

			server:/export/client/swap   none  swap	 sw,nfsmntpt=/swap
			server:/export/client/root   /	   nfs	 rw 0 0

	      --	  Set up the client's rc.conf(5)

		  Edit _/_e_x_p_o_r_t_/_c_l_i_e_n_t_/_r_o_o_t_/_e_t_c_/_r_c_._c_o_n_f

			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.

	      --	  Set up the client's hosts(5) file.

		  Edit _/_e_x_p_o_r_t_/_c_l_i_e_n_t_/_r_o_o_t_/_e_t_c_/_h_o_s_t_s

			::1			localhost
			127.0.0.1		localhost
			192.168.1.10 client.test.net client
			192.168.1.5  server.test.net server

	 7.   Setting up the server daemons

	      If you want these	services to start up every time
	      you boot your server, make sure the following lines
	      are present in your _/_e_t_c_/_r_c_._c_o_n_f:

		    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 _t_f_t_p_d line in
	      _/_e_t_c_/_i_n_e_t_d_._c_o_n_f remains uncommented.

	 Skip forward to _I_n_s_t_a_l_l_i_n_g _t_h_e	_N_e_t_B_S_D _S_y_s_t_e_m

     ++oo	 _P_r_e_p_a_r_i_n_g _a _S_C_S_I _o_r _I_D_E _d_r_i_v_e _w_i_t_h _t_h_e	_C_D_-_R _i_m_a_g_e

	 If the	NetBSD/macppc CD-R 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	disk image
	 _N_e_t_B_S_D_-_1_0_._1___S_T_A_B_L_E_-_m_a_c_p_p_c_._i_s_o 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	disk image has an HFS partition
	 with _o_f_w_b_o_o_t_._x_c_f which	loads the installation kernel
	 from the ISO file system on the disk image.

	 --   _F_r_o_m _a_n _U_N_I_X_-_l_i_k_e _m_a_c_h_i_n_e _(_i_n_c_l_u_d_i_n_g _M_a_c_O_S	_X_)

		   # dddd	iiff==NNeettBBSSDD--1100..11__SSTTAABBLLEE--mmaaccppppcc..iissoo ooff==//ddeevv//rrssdd00cc

	     where _/_d_e_v_/_r_s_d_0_c 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.

	 --   _F_r_o_m _a _W_i_n_d_o_w_s _m_a_c_h_i_n_e

	     Get rraawwrriittee3322..eexxee from
		   hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//~~mmaarrttiinn//rraawwrriittee3322//

	     Be	certain	you have selected the correct disk, as it
	     will erase	the contents.

	 --   _F_r_o_m _a _M_a_c_O_S _9 _(_o_r	_e_a_r_l_i_e_r_) _m_a_c_h_i_n_e

	     Get ssuunnttaarr	from
		   hhttttpp::////hhyyppeerraarrcchhiivvee..llccss..mmiitt..eedduu//HHyyppeerrAArrcchhiivvee//AArrcchhiivvee//ccmmpp//ssuunnttaarr--222233..hhqqxx

	     1.	  Open the `Preferences' menu and pick `Expert
		  Mode'

	     2.	  Open the `File' menu and pick	`Open Device ...'

	     3.	  Click	on the ``scan SCSI'' button to get a list
		  of which drives are attached.

	     4.	  Pick the correct drive.  Be certain you have
		  selected the correct disk, as	it will	erase the
		  contents.

	     5.	  Open the `Special' menu and pick `Overwrite
		  Sectors ...'

	     6.	  Hit return (i.e. start at sector number zero)

	     7.	  Select _N_e_t_B_S_D_-_1_0_._1___S_T_A_B_L_E_-_m_a_c_p_p_c_._i_s_o and click
		  ``Open''

	     8.	  Open the `File' menu and pick	`Close Device'

     Skip forward to _I_n_s_t_a_l_l_i_n_g	_t_h_e _N_e_t_B_S_D _S_y_s_t_e_m

   PPrreeppaarriinngg yyoouurr OOppeenn FFiirrmmwwaarree	11..xx oorr 22..xx SSyysstteemm ffoorr NNeettBBSSDD
     _G_e_t_t_i_n_g _t_o	_O_p_e_n _F_i_r_m_w_a_r_e _o_n _A_p_p_l_e _N_e_t_w_o_r_k _S_e_r_v_e_r_s

     (Open Firmware 1.1.22)

     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 con-
     sole) 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 > sseetteennvv aauuttoo--bboooott?? ffaallssee

     Skip down to the section on _S_e_t_t_i_n_g _u_p _O_p_e_n _F_i_r_m_w_a_r_e _1 _a_n_d	_2
     _t_o	_b_o_o_t _N_e_t_B_S_D since the next several pages are instructions
     for MacOS models.

     _O_p_e_n _F_i_r_m_w_a_r_e _1 _a_n_d _2 _S_y_s_t_e_m _P_r_e_p_a_r_a_t_i_o_n

     Open Firmware has two variables, `input-device' and
     `output-device', which specify how	it accepts commands and
     displays 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 _w_i_l_l need to hook up a serial console tempo-
     rarily 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.
	   hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//mmooddeellss..hhttmmll

     In	particular, some models	_m_u_s_t 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:
	   hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//ffaaqq..hhttmmll##ooffww--iinnppuutt--oouuttppuutt--ddeevviicceess

     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.
	   hhttttpp::////hhyyppeerraarrcchhiivvee..llccss..mmiitt..eedduu//HHyyppeerrAArrcchhiivvee//AArrcchhiivvee//ccoommmm//tteerrmm//zztteerrmm--110011..hhqqxx
	   hhttttpp::////hhoommeeppaaggee..mmaacc..ccoomm//ddaallvveerrssoonn//zztteerrmm//

     See the NetBSD Serial Port	Primer for additional help and
     references:
	   hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ddooccss//HHaarrddwwaarree//MMiisscc//sseerriiaall..hhttmmll

     All Open Firmware 1 and 2 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 9 tool called System Disk, which
     patches most of these bugs. We _s_t_r_o_n_g_l_y recommend that you
     use this tool to patch your Open Firmware,	as several sys-
     tems 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 _G_e_t_t_i_n_g _t_o _O_p_e_n _F_i_r_m_w_a_r_e
     _(_H_a_r_d_e_r_, _M_a_c_O_S _7 _t_h_r_u _9_)
     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

     _G_e_t_t_i_n_g _t_o	_O_p_e_n _F_i_r_m_w_a_r_e _(_M_a_c_O_S _X _o_r _D_a_r_w_i_n_)

     When you install MacOS X or Darwin, it will install the nec-
     essary NVRAM bug fixes.  Use the nnvvrraamm command to set your
     system to always stop at the Open Firmware	prompt,	then
     reboot.

	   # nnvvrraamm aauuttoo--bboooott\\??==ffaallssee

     You will need to escape the question-mark or enclose the
     whole nnvvrraamm argument in double-quotes to prevent your shell
     from trying to interpret it.

     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.  You must hook up a serial	console
     (38400 bps, 8 bits, no parity, 1 stop bit,	no handshaking).

     _G_e_t_t_i_n_g _t_o	_O_p_e_n _F_i_r_m_w_a_r_e _(_B_e_s_t_, _M_a_c_O_S _8 _o_r	_9_)

     Download System Disk:
	   ffttpp::////ffttpp..aappppllee..ccoomm//ddeevveellooppeerr//mmaaccoossxxsseerrvveerr//uuttiilliittiieess//SSyysstteemmDDiisskk22..33..11..ssmmii..bbiinn

     For a brief tutorial on how to use	System Disk, see:
	   hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//SSyysstteemmDDiisskk--ttuuttoorriiaall//

     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.

     _N_o_t_e_:  NVRAM patches and Open Firmware settings will be
	    erased if you `zap your PRAM' by holding down
	    COMMAND-OPTION-P-R keys during the boot chimes, or if
	    you	accidentally boot into MacOS 9 or earlier.

     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
	   hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//SSyysstteemmDDiisskk--ttuuttoorriiaall//ooff110055ppaattcchh..hhttmmll

     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).

     _N_o_t_e_:  The	``Stop Boot at Open Firmware prompt'' setting is
	    persistent.	 It is equivalent to the Open Firmware
	    command

		  0 > sseetteennvv aauuttoo--bboooott??	ffaallssee

     _N_o_t_e_:  Unfortunately, there are a few models that are better
	    off	without	the System Disk	patches.  If you find
	    that your machine doesn't boot, then try:

		  0 > sseetteennvv uussee--nnvvrraammrrcc?? ffaallssee
		  0 > rreesseett--aallll

     _G_e_t_t_i_n_g _t_o	_O_p_e_n _F_i_r_m_w_a_r_e _(_H_a_r_d_e_r_, _M_a_c_O_S _7_,	_8_, _o_r _9_)

     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.

	   hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD//aarrcchh//mmaaccppppcc//mmaaccooss--uuttiillss//bboooottvvaarrss//bboooottvvaarrss..ssiitt..hhqqxx

     _N_o_t_e_:  BootVars does _n_o_t apply the	(possibly critical) NVRAM
	    patches that System	Disk does.  Expect some	devices
	    to not work	(such as booting from hard drives and CD-
	    ROMs).

     Look up the proper	`output-device'	for your model on the
     NetBSD/macppc Model Support webpage.
	   hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//mmooddeellss..hhttmmll
     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 kkbbdd 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
	   hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//SSyysstteemmDDiisskk--ttuuttoorriiaall//ooff110055ppaattcchh..hhttmmll

     If	you have a Performa 5500 or 6500, you may need to apply
     NVRAMRC patches to	use your built-in video.  See the infor-
     mation 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 hand-
     shaking).

     _N_o_t_e_:  The	``auto-boot?'' setting is persistent.  Your sys-
	    tem	will always stop at the	Open Firmware prompt.  It
	    is equivalent to the Open Firmware command

		  0 > sseetteennvv aauuttoo--bboooott??	ffaallssee

     _G_e_t_t_i_n_g _t_o	_O_p_e_n _F_i_r_m_w_a_r_e _(_W_i_t_h_o_u_t _u_s_i_n_g _M_a_c_O_S_)

     (Open Firmware 1.0.5, Open	Firmware 2.0.x,	Open Firmware
     2.4)

     If	you don't have MacOS, then you need to hold down a spe-
     cial 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.

     _N_o_t_e_:  Your system	will _n_o_t have the (possibly critical)
	    NVRAM patches that System Disk applies.  Expect some
	    devices to not work	(such as booting from hard drives
	    and	CD-ROMs).

     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 hand-
     shaking).

     Now, set your system to always stop at the	Open Firmware
     prompt.

	   0 > sseetteennvv aauuttoo--bboooott?? ffaallssee

     To	use your on-board video	and keyboard, look up the proper
     `output-device' for your model on the NetBSD/macppc webpage
	   hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//mmooddeellss..hhttmmll
     Run the following commands	to use your screen instead of a
     serial console (replace `screen' with the correct
     `output-device' for your model):

	   0 > sseetteennvv oouuttppuutt--ddeevviiccee ssccrreeeenn
	   0 > sseetteennvv iinnppuutt--ddeevviiccee kkbbdd
	   0 > rreesseett--aallll

     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
	   hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//SSyysstteemmDDiisskk--ttuuttoorriiaall//ooff110055ppaattcchh..hhttmmll

     _S_e_t_t_i_n_g _u_p	_O_p_e_n _F_i_r_m_w_a_r_e _1	_a_n_d _2 _t_o _b_o_o_t _N_e_t_B_S_D

     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:
	   hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//ffaaqq..hhttmmll##ooffww--aacccceessss
	   hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//ffaaqq..hhttmmll##ooffww--vvaarriiaabblleess

     Double-check your Open Firmware version:

	   0 > ddeevv //ooppeennpprroomm
	   0 > ..pprrooppeerrttiieess
	   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 _n_o_t run these commands on Open Firmware 3
     machines, as you may overwrite your firmware requiring a
     trip to Apple for repairs.

	   0 > sseetteennvv llooaadd--bbaassee	660000000000
	   0 > sseetteennvv rreeaall--bbaassee	FF0000000000
	   0 > rreesseett--aallll

     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 > ddeevv eenneett
	   0 > ..pprrooppeerrttiieess
	   [...]
	   local-mac-address   CCCCCCCC	CCCC
	   [...]
	    ok

     _N_o_t_e_:  Some early Open Firmware 1.0.5 machines had	their MAC
	    address stored incorrectly on the motherboard (lit-
	    tle- vs. big-endian	problems).  The	patches	the Sys-
	    tem	Disk installs will correct this.  Without the
	    patch, the machine will still work,	but its	MAC
	    address may	conflict with another ethernet device on
	    your network.

     You can check your	Open Firmware settings with the	_p_r_i_n_t_e_n_v
     command:

	   0 > pprriinntteennvv
	   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

     _N_o_t_e_:  All	Open Firmware 1.0.5 settings and nvram patches
	    will be erased if you boot into MacOS 9 or earlier.
	    You	will need to re-enter them before booting NetBSD
	    again.

     _N_o_t_e_:  Open Firmware 2.0.x	and Open Firmware 2.4 systems
	    will set the real-base environment variable	to its
	    default value (which prevents NetBSD from booting) if
	    you	boot into MacOS	9 or earlier.

     _A_v_a_i_l_a_b_l_e _B_o_o_t _M_e_d_i_a

     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, and MS-DOS FAT).	 Unfortunately,
     Open Firmware is _n_o_t able to directly boot	from the NetBSD
     file system (FFS) or Apple's file systems (HFS, HFS+, or
     UFS), so we must put the bootloader in a location that Open
     Firmware is capable of understanding.

     Therefore,	to boot	the NetBSD kernel, Open	Firmware must
     first load	a `bootloader' which knows how to load the NetBSD
     kernel.  Open Firmware 1 and 2 take either	a two or three
     stage approach, depending on the boot media.  In the two
     step approach, Open Firmware loads	_o_f_w_b_o_o_t_._x_c_f from the boot
     media, which then loads the kernel.  In the three step
     approach (used in the `partition zero' method), Open
     Firmware loads a primary bootloader _b_o_o_t_x_x	from a disk which
     then loads	the secondary bootloader _o_f_w_b_o_o_t (which	is func-
     tionally identical	to _o_f_w_b_o_o_t_._x_c_f)	which then loads the ker-
     nel.

     _N_o_t_e_:  Despite a note to the contrary in earlier releases
	    that _o_f_w_b_o_o_t_._e_l_f is	obsoleted, that	is no longer the
	    case.  It has been observed	that on	some newish
	    machines (notably at least some Mac	Minis),	use of
	    _o_f_w_b_o_o_t_._x_c_f	will result in an early	kernel panic when
	    loading the	GENERIC	kernel from disk.  For these
	    machines it	appears	to be a	workaround to use
	    _o_f_w_b_o_o_t_._e_l_f	instead	of _o_f_w_b_o_o_t_._x_c_f as the boot
	    loader.  The root cause for	this problem has unfortu-
	    nately yet to be found.

     The following bootable media are available	for loading the
     bootloader:

	   ++oo   `_P_a_r_t_i_t_i_o_n _z_e_r_o'

	       This method loads the primary bootloader	_b_o_o_t_x_x
	       located in the Apple Partition Map, which then
	       loads the secondary bootloader _o_f_w_b_o_o_t which then
	       loads the kernel.  This is what ssyyssiinnsstt will place
	       on your hard drive during the installation proce-
	       dure.  Additionally, the	NetBSD/macppc CD-R images
	       and boot	floppies use this method, loading a ker-
	       nel from	the floppy's FFS partition or the CD-R's
	       ISO9660 partition.

	   ++oo   _M_S_-_D_O_S _f_i_l_e _s_y_s_t_e_m

	       In this method, Open Firmware loads the
	       _o_f_w_b_o_o_t_._x_c_f bootloader from an MS-DOS file system.
	       It may then load	a NetBSD kernel	from the same MS-
	       DOS file	system.	 This has only been thoroughly
	       tested on floppy	disks, but may work on Zip disks
	       or FDISK-formatted hard drives.	This does not
	       work for	MS-DOS partitions on a hard drive with an
	       Apple Partition Map.

	   ++oo   _E_t_h_e_r_n_e_t	_(_n_e_t_w_o_r_k _b_o_o_t_)

	       You can run your	entire system diskless or netboot
	       only the	files necessary	to boot	(i.e. the boot-
	       loader and the installation kernel).  You must
	       have root access	for the	UNIX-like netboot server,
	       which must be on	the same subnet	as your
	       NetBSD/macppc machine.

	       _N_o_t_e_:  You must use your	on-board ethernet device
		      for netbooting.  While there may be some
		      PCI or Cardbus ethernet interfaces with
		      Open Firmware ROMs, no one has reported
		      success netbooting using these devices

	   ++oo   _I_S_O_9_6_6_0 _C_D_-_R_O_M _f_i_l_e _s_y_s_t_e_m

	       Load the	_o_f_w_b_o_o_t_._x_c_f 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 _n_o_t
	       boot from the ISO9660 file system if you	create a
	       hybrid HFS/ISO format CD-R.  Make sure that the CD
	       _o_n_l_y has	ISO9660	data and does not have an Apple
	       Partition Map.

	       _N_o_t_e_:  Open Firmware can	only open files	on the
		      first session of a multi-session CD-R

     Once the bootloader is loaded, it can open	the kernel from
     one of the	following sources:

	   ++oo   _E_t_h_e_r_n_e_t	_(_N_F_S_)

	   ++oo   _N_e_t_B_S_D _F_F_S _f_i_l_e _s_y_s_t_e_m

	       Such as the boot	floppy,	or an installed	NetBSD
	       partition.

	   ++oo   _M_a_c_O_S _X _U_F_S _f_i_l_e	_s_y_s_t_e_m

	   ++oo   _I_S_O_9_6_6_0 _C_D_-_R_O_M _f_i_l_e _s_y_s_t_e_m

	   ++oo   _M_S_-_D_O_S _f_i_l_e _s_y_s_t_e_m

     In	theory,	Open Firmware 2.4 systems should be able to load
     the bootloader from an HFS	or HFS+	partition or a hybrid CD-
     R,	but users have reported	that it	doesn't	work.

     The boot floppy images provided have a `partition zero'
     bootloader	and a NetBSD file system with an installation
     kernel.  The boot CD image	provided has both a `partition
     zero' bootloader and _o_f_w_b_o_o_t_._x_c_f on a hybrid partition so it
     can be booted on all Open Firmware	versions.  It also has an
     ISO9660 file system with an installation kernel and the dis-
     tribution sets.

     _P_a_r_t_i_t_i_o_n_i_n_g _y_o_u_r _h_a_r_d _d_r_i_v_e _f_o_r _N_e_t_B_S_D

     You must use the NetBSD installer to partition your disk if
     you want it to be bootable.  With this release of NetBSD,
     there is no way to	dual-boot MacOS	and NetBSD on one hard
     drive.

     You can use the instructions in this section to partition a
     disk that may also	be used	with MacOS, although a disk pre-
     pared in this way _w_i_l_l _n_o_t	_b_o_o_t 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 _/_u_s_r,	_/_h_o_m_e, or _/_e_x_p_o_r_t) may be on the same
     disk as MacOS.

     Unless you	are planning to	use partitions on the same disk
     as	MacOS, skip forward to _P_r_e_p_a_r_i_n_g _t_h_e _O_p_e_n _F_i_r_m_w_a_r_e _1 _o_r	_2
     _B_o_o_t_a_b_l_e _M_e_d_i_a

     There are two partitioning	tools available	for
     NetBSD/macppc, disklabel(8) and pdisk(8).	The former is
     used in the NetBSD	ssyyssiinnsstt	installer, and will render your
     disk unusable by MacOS.

     The process is more fully detailed	in the Partitioning HOW-
     TO:
	   hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//ppaarrttiittiioonniinngg..hhttmmll

     You can create a partition	map with pdisk(8), but the disk
     will not be usable	with MacOS 9 and earlier.  If this is a
     concern, you will need to use Apple's Drive Setup or Disk
     Utility.

     If	you are	using Apple's Drive Setup tool,	make sure you
     have version 1.8.1	or later.  This	tool only runs under
     MacOS 9 and earlier.  Drive Setup will erase the contents of
     your drive	-- it does not preserve	data from any of your
     partitions.

     Apple's Disk Utility only runs under MacOS	X 10.0.0 and
     later.  Make sure you click the ``Install Mac OS 9	Disk
     Drivers'' checkbox.  Also,	keep in	mind that Disk Utility
     does _n_o_t create the partitions that NetBSD/macppc requires.
     After creating the	initial	partition map with Disk	Utility,
     you will need to use the NetBSD ppddiisskk to change the parti-
     tion types.  Also,	Disk Utility will erase	the contents of
     your drive	-- it does not preserve	data from any of your
     partitions.

     ppddiisskk is the most flexible	(and most difficult to use) par-
     titioning tool available.	It runs	on almost all OSes that
     macppc machines support.  Download	it:
	   hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD//aarrcchh//mmaaccppppcc//nneettbbssdd--ppddiisskk//
	   hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD//aarrcchh//mmaaccppppcc//mmaaccooss--uuttiillss//ppddiisskk..sseeaa..hhqqxx

     There is built-in help describing how it works.  When it
     asks you to enter the ``Type of partition'', use
     Apple_UNIX_SVR2 for NetBSD	partitions, Apple_HFS for HFS and
     HFS+ partitions, and Apple_UFS for	UFS partitions.

     After you've written the partition	map with ppddiisskk,	you will
     need to create the	file systems.  Use newfs(8) and	mount(8)
     for NetBSD	file systems, and hhffssttoooollss to create and mount
     HFS file systems.
	   hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD//ppaacckkaaggeess//ppkkggssrrcc//ssyyssuuttiillss//hhffssuuttiillss//

     Make the following	partitions:

	   _A_/_U_X	_S_w_a_p		     Any size.	The recommenda-
				     tion is your RAM size,
				     although this is not
				     strictly necessary	for
				     machines with a lot of RAM.
				     NetBSD interprets an _A_/_U_X
				     _S_w_a_p partition as the second
				     partition (_b) on the disk.
				     This partition is not read-
				     able from MacOS.

	   _A_/_U_X	_U_s_e_r and _A_/_U_X _F_r_e_e_1  Use these for any additional
				     partitions	you may	want to
				     use under NetBSD, such as
				     _/_u_s_r (at least 200	MB),
				     _/_h_o_m_e, _/_u_s_r_/_l_o_c_a_l,	or
				     _/_u_s_r_/_p_k_g.	NetBSD interprets
				     these partitions as normal
				     NetBSD-style partitions.
				     These partitions are not
				     readable from MacOS.

	   _H_F_S			     Any size.	You may	want to
				     leave an additional parti-
				     tion available to transfer
				     files between MacOS and
				     NetBSD.  If would like to
				     create such a partition,
				     then see the Partitioning
				     HOW-TO.
					   hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//ppaarrttiittiioonniinngg..hhttmmll##mmssddooss

	   _U_F_S			     Any size.	_U_F_S partitions
				     are not readable from MacOS
				     versions prior to X 10.0.0.
				     If	you use	an _U_F_S partition
				     as	your root, then	it may
				     not be recognized by the
				     NetBSD kernel as the first
				     partition (_a) on the disk.
				     You will need to compile a
				     new kernel	with the root
				     partition explicitly defined
				     to	be the _U_F_S partition.

     Now would be a good time to use ppddiisskk to determine	the par-
     tition numbers for	your bootloader	and kernel.

     _P_r_e_p_a_r_i_n_g _t_h_e _O_p_e_n	_F_i_r_m_w_a_r_e _1 _o_r _2	_B_o_o_t_a_b_l_e _M_e_d_i_a

     The purpose of this section is to prepare the media from
     which your	system will boot the installer.	 We'll describe
     how to put	the files in the right places on your disk(s) or
     netboot server and	prepare	it for use on your system.

     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 dis-
     tribution sets on the diskless server.

     To	get the	distribution sets onto appropriate media, see the
     above section entitled _G_e_t_t_i_n_g _t_h_e	_N_e_t_B_S_D _S_y_s_t_e_m _o_n _t_o
     _U_s_e_f_u_l _M_e_d_i_a.  You	may want to get	the distribution sets
     when you create the bootable media.

     _N_o_t_e_:  Some MacOS ffttpp clients default to downloading files
	    in `ASCII' mode.  This will	render the NetBSD files
	    useless.  Make sure	to set your ftp	program	to down-
	    load in `binary' mode.

     What follows are the steps	to create different types of
     bootable media for	the NetBSD install kernel. You should
     only need to create one of	these to get your system to boot
     the installer

     ++oo	 _C_r_e_a_t_i_n_g _t_h_e _N_e_t_B_S_D_/_m_a_c_p_p_c _C_D_-_R

	 Go to one of the NetBSD mirror	sites and download the
	 CD-R image _N_e_t_B_S_D_-_1_0_._1___S_T_A_B_L_E_-_m_a_c_p_p_c_._i_s_o from the
	 _p_u_b_/_N_e_t_B_S_D_/_i_m_a_g_e_s directory.
	       hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//mmiirrrroorrss//##iissoo

	 --   _F_r_o_m _a_n _U_N_I_X_-_l_i_k_e _m_a_c_h_i_n_e

	     Get and install cdrecord.	NetBSD users should
	     install it	from the package collection.  Other
	     UNIX-like systems should get it from the official
	     website:
		   hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD//ppaacckkaaggeess//ppkkggssrrcc//ssyyssuuttiillss//ccddrrttoooollss//
		   hhttttpp::////wwwwww..ffookkuuss..ggmmdd..ddee//rreesseeaarrcchh//cccc//gglloonnee//eemmppllooyyeeeess//jjooeerrgg..sscchhiilllliinngg//pprriivvaattee//ccddrreeccoorrdd..hhttmmll

		   # ccddrreeccoorrdd --vv ssppeeeedd==44 ddeevv==//ddeevv//ccdd11cc NNeettBBSSDD--1100..11__SSTTAABBLLEE--mmaaccppppcc..iissoo

	     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
	     _/_d_e_v_/_c_d_1_d).

	 --   _F_r_o_m _a _M_a_c_O_S _m_a_c_h_i_n_e _(_u_s_i_n_g _T_o_a_s_t_)

	     1.	  Click	the `Other' button in the main window.

	     2.	  Open the contextual menu on the `Other' button
		  and select `Disk Image'

	     3.	  Click	the `Select' button and	select the disk
		  image	you downloaded.

	     4.	  Click	the `Record' button

	 Skip forward to _I_n_s_t_a_l_l_i_n_g _t_h_e	_N_e_t_B_S_D _S_y_s_t_e_m

     ++oo	 _C_r_e_a_t_i_n_g _t_h_e _N_e_t_B_S_D_/_m_a_c_p_p_c _i_n_s_t_a_l_l _f_l_o_p_p_i_e_s

	 1.   First, make sure you have	done a low-level format
	      on the disks.  A bad floppy can produce Open
	      Firmware errors similar to other problems.

	 2.   If the boot floppy images	are compressed,	then you
	      will need	to uncompress them first.

	 3.   Use a tool to write the boot floppy images
	      _i_n_s_t_a_l_l_a_t_i_o_n_/_f_l_o_p_p_y_/_b_o_o_t_1_._f_s and
	      _i_n_s_t_a_l_l_a_t_i_o_n_/_f_l_o_p_p_y_/_b_o_o_t_2_._f_s to two floppy disks.
	      PowerPC 601 machines should use
	      _i_n_s_t_a_l_l_a_t_i_o_n_/_f_l_o_p_p_y_/_b_o_o_t_6_0_1___1_._f_s and
	      _i_n_s_t_a_l_l_a_t_i_o_n_/_f_l_o_p_p_y_/_b_o_o_t_6_0_1___2_._f_s instead.

	      --	  _F_r_o_m _a_n _U_N_I_X_-_l_i_k_e _m_a_c_h_i_n_e

			# dddd iiff==bboooott11..ffss ooff==//ddeevv//rrffdd00aa bbss==3366kk
			# dddd iiff==bboooott22..ffss ooff==//ddeevv//rrffdd00aa bbss==3366kk

	      --	  _F_r_o_m _a _W_i_n_d_o_w_s _m_a_c_h_i_n_e

		  Get either the rraawwrriittee..eexxee program from the
		  NetBSD/i386 distribution or rraawwrriittee3322..eexxee from
			hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//~~mmaarrttiinn//rraawwrriittee3322//

	      --	  _F_r_o_m _a _M_a_c_O_S _9 _(_o_r _e_a_r_l_i_e_r_) _m_a_c_h_i_n_e

		  Get ssuunnttaarr from
			hhttttpp::////hhyyppeerraarrcchhiivvee..llccss..mmiitt..eedduu//HHyyppeerrAArrcchhiivvee//AArrcchhiivvee//ccmmpp//ssuunnttaarr--222233..hhqqxx

		  1.   Open the	`Preferences' menu and pick
		       `Expert Mode'

		  2.   Open the	`Special' menu and pick
		       `Overwrite Sectors ...'

		  3.   Insert the first	floppy disk

		  4.   Hit return (i.e.	start at sector	number
		       zero)

		  5.   Select _b_o_o_t_1_._f_s and click ``Open''

		  6.   Open the	`File' menu and	pick `Eject'

		  7.   Repeat the process for the second floppy

	 Skip forward to _I_n_s_t_a_l_l_i_n_g _t_h_e	_N_e_t_B_S_D _S_y_s_t_e_m

     ++oo	 _C_r_e_a_t_i_n_g _a _c_u_s_t_o_m _I_S_O_9_6_6_0 _C_D_-_R

	 This section describes	how to create your own bootable
	 NetBSD/macppc CD-R. We	recommend that you use the offi-
	 cial NetBSD/macppc-10.1_STABLE	CD-R image, as described
	 in the	section	above.

	 Place _o_f_w_b_o_o_t_._x_c_f and the installation	kernel
	 _n_e_t_b_s_d_-_G_E_N_E_R_I_C___M_D_._g_z 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
	 _n_e_t_b_s_d_._g_z.  You may also place	the NetBSD 10.1_STABLE
	 distribution sets on the disk.

	 --   _F_r_o_m _a_n _U_N_I_X_-_l_i_k_e _m_a_c_h_i_n_e

	     Get and install mkisofs.  This is now part	of the
	     cdrecord package.	NetBSD users should install it
	     from the package collection.  Other UNIX-like sys-
	     tems should get it	from the official website:
		   hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD//ppaacckkaaggeess//ppkkggssrrcc//ssyyssuuttiillss//ccddrrttoooollss//
		   hhttttpp::////wwwwww..ffookkuuss..ggmmdd..ddee//rreesseeaarrcchh//cccc//gglloonnee//eemmppllooyyeeeess//jjooeerrgg..sscchhiilllliinngg//pprriivvaattee//ccddrreeccoorrdd..hhttmmll

		   # mmkkiissooffss --oo	NNeettBBSSDD--1100..11__SSTTAABBLLEE--mmaaccppppcc..iissoo --ll --JJ --rr --LL --NN //ccddssoouurrcceess
		   # ccddrreeccoorrdd --vv ssppeeeedd==44 ddeevv==//ddeevv//ccdd11cc NNeettBBSSDD--1100..11__SSTTAABBLLEE--mmaaccppppcc..iissoo

	     You will need to substitute the correct speed for
	     your CD writer, and the correct device for	your sys-
	     tem (for i386 it would be _/_d_e_v_/_c_d_1_d).

	     See the NetBSD Bootable CD-ROM HOW-TO for more
	     detail:
		   hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ddooccss//bboooottccdd..hhttmmll

	 --   _F_r_o_m _a _M_a_c_O_S _m_a_c_h_i_n_e _(_u_s_i_n_g _T_o_a_s_t_)

	     1.	  Click	the `Other' button in the main window

	     2.	  Open the contextual menu on the `Other' button
		  and select `ISO 9660'

	     3.	  Click	the `Select' button.

	     4.	  Click	the `Settings' tab, open the `Naming'
		  popup	menu, and pick `Allow Macintosh	Names'

	     5.	  Click	on the `Files' tab

	     6.	  Drag _i_n_s_t_a_l_l_a_t_i_o_n_/_o_f_w_b_o_o_t_._x_c_f	and
		  _b_i_n_a_r_y_/_k_e_r_n_e_l_/_n_e_t_b_s_d_-_G_E_N_E_R_I_C___M_D_._g_z into the
		  window.  You may also	want to	drag the
		  NetBSD 10.1_STABLE distribution sets to this
		  window as well.

	     7.	  Click	the `Done' button

	     8.	  Click	the `Record' button

	 Skip forward to _I_n_s_t_a_l_l_i_n_g _t_h_e	_N_e_t_B_S_D _S_y_s_t_e_m

     ++oo	 _C_r_e_a_t_i_n_g _a_n _M_S_-_D_O_S _d_i_s_k

	 Unfortunately,	the installation kernel	is now too large
	 to fit	onto a floppy disk, but	you can	still create a
	 bootable Zip disk with	this method.

	 1.   First, make sure you have	done a low-level format
	      on the disk.  A bad disk can produce Open	Firmware
	      errors similar to	other problems.

	 2.   Mount the	disk on	your computer.
	      --	  Insert it into a Windows or DOS machine.
	      --	  Use `File Exchange or	`PC Exchange'' with MacOS
		  versions prior to X 10.0.0
	      --	  Use mount_msdos(8) on	any UNIX-like machine.

	 3.   Copy _n_e_t_b_s_d_-_I_N_S_T_A_L_L_._g_z and _o_f_w_b_o_o_t_._x_c_f to	the disk.
	      PowerPC 601 machines need	to use
	      _n_e_t_b_s_d_-_I_N_S_T_A_L_L___6_0_1_._g_z.

	 4.   Rename _n_e_t_b_s_d_-_I_N_S_T_A_L_L_._g_z to _n_e_t_b_s_d_._g_z, since Open-
	      Firmware can't deal with MS-DOS filenames	longer
	      than eight characters.

	 Skip forward to _I_n_s_t_a_l_l_i_n_g _t_h_e	_N_e_t_B_S_D _S_y_s_t_e_m

     ++oo	 _P_r_e_p_a_r_i_n_g _t_h_e _n_e_t_b_o_o_t _s_e_r_v_e_r

	 1.   Introduction

	      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 man-
	      ual 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 con-
	      figure the netboot services on a variety of plat-
	      forms:
		    hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ddooccss//nneettwwoorrkk//nneettbboooott//

	      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 execut-
	      ing 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 exe-
	      cuting 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, _o_f_w_b_o_o_t_._x_c_f.  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
	      _/_e_x_p_o_r_t_/_c_l_i_e_n_t_/_r_o_o_t.  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.

	 2.   dhcpd(8) in bootpd(8) compatible mode

	      Put the following	lines in your _/_e_t_c_/_d_h_c_p_d_._c_o_n_f
	      (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;  # master DHCP server for this subnet
				    #
		    subnet 192.168.1.0 netmask 255.255.255.0 {
				    # Which network interface to listen	on.
				    # The zeros	indicate the range of addresses
				    # that 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";

				    #
				    # The host address of the NFS server. This is mandatory for
				    # NetBSD kernels even it's the same	host as	the DHCP server.
		    #
				    # macppc machines will look	for their bootloader,
				    # ofwboot.xcf, on the next-server as well.
				    #
				    next-server	server.test.net;
			    }
		     #you may paste another "host" entry here for additional
		     #clients on this network
		    }

	      You will need to make sure that the _d_h_c_p_d_._l_e_a_s_e_s
	      file exists.

		    # ttoouucchh //vvaarr//ddbb//ddhhccppdd..lleeaasseess

	      You will need to start the ddhhccppdd.	 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 NetBSD, you can achieve this with:

		    # //eettcc//rrcc..dd//ddhhccppdd rreessttaarrtt

	 3.   tftpd(8)

	      The default configuration	of the TFTP server is to
	      run in a chroot(8) environment in	the _/_t_f_t_p_b_o_o_t
	      directory.  Thus,	the first order	of business is to
	      create this directory:

		    # mmkkddiirr --pp //ttffttppbboooott

	      Next, edit _/_e_t_c_/_i_n_e_t_d_._c_o_n_f 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
	      NetBSD, you can achieve this with:

		    # //eettcc//rrcc..dd//iinneettdd rreessttaarrtt

	      Now, you need to copy the	bootloader for your
	      macppc machine to	_/_t_f_t_p_b_o_o_t.  Get	ofwboot.xcf(8)
	      from the _i_n_s_t_a_l_l_a_t_i_o_n directory of the distribu-
	      tion.

		    # ccpp ooffwwbboooott..xxccff //ttffttppbboooott
	      Just to be sure, let's make everything readable.

		    # cchhmmoodd --RR aa++rrXX //ttffttppbboooott

	      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 _/_v_a_r_/_l_o_g_/_m_e_s_s_a_g_e_s saying: `tftpd:
	      write: Host is down'.  If	this is	the case, you may
	      need to force the	server to map your client's eth-
	      ernet address to its IP address:

		    # aarrpp --ss cclliieenntt CCCC::CCCC::CCCC::CCCC::CCCC::CCCC

	 4.   nfsd(8), mountd(8), and rpcbind(8)

	      Now your system should be	able to	load the boot-
	      strap program and	start looking for the kernel.
	      Let's set	up the NFS server.  Create the directory
	      you are exporting	for the	netboot	client:

		    # mmkkddiirr --pp //eexxppoorrtt//cclliieenntt//rroooott

	      Put the following	line in	_/_e_t_c_/_e_x_p_o_r_t_s 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	NetBSD,	you can	achieve	this
	      with:

		    # //eettcc//rrcc..dd//rrppccbbiinndd	ssttaarrtt
		    # //eettcc//rrcc..dd//nnffssdd ssttaarrtt
		    # //eettcc//rrcc..dd//mmoouunnttdd rreessttaarrtt

	 5.   NetBSD kernel and	installation tools

	      Now, if you place	a kernel named _n_e_t_b_s_d in
	      _/_e_x_p_o_r_t_/_c_l_i_e_n_t_/_r_o_o_t your client should boot the
	      kernel.  If you are netbooting the installer, use
	      _b_i_n_a_r_y_/_k_e_r_n_e_l_/_n_e_t_b_s_d_-_G_E_N_E_R_I_C___M_D_._g_z (this has the
	      installation tools in a RAM disk).  Also,	copy the
	      distribution files to the	client's root directory.

	      _N_o_t_e_:  Some combinations of Open Firmware	version
		     and _o_f_w_b_o_o_t_._x_c_f version have trouble loading
		     compressed	kernels.  If you have trouble
		     loading a kernel, try uncompressing it with
		     gunzip(1)

		    # ccpp **..ttggzz //eexxppoorrtt//cclliieenntt//rroooott
		    # gguunnzziipp nneettbbssdd--GGEENNEERRIICC__MMDD..ggzz
		    # mmvv nneettbbssdd--GGEENNEERRIICC__MMDD //eexxppoorrtt//cclliieenntt//rroooott//nneettbbssdd

	      If you are running your macppc diskless, simply use
	      _b_i_n_a_r_y_/_k_e_r_n_e_l_/_n_e_t_b_s_d_-_G_E_N_E_R_I_C_._g_z.

	 6.   Client file system

	      You can skip this	step if	you do not plan	to run
	      your client diskless after installation.	Other-
	      wise, 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.  See _f_o_r _d_e_t_a_i_l_s_:
		    hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ddooccss//nneettwwoorrkk//nneettbboooott//nnffss..hhttmmll.
	      --	  Extracting distribution sets

			# ccdd //eexxppoorrtt//cclliieenntt//rroooott
			# ttaarr --xxppzzff //ppaatthh//ttoo//ffiilleess//bbaassee..ttggzz
			# ttaarr --xxppzzff //ppaatthh//ttoo//ffiilleess//eettcc..ttggzz

		  Continue with	the other non-essential	distribu-
		  tion sets if desired.

	      --	  Set up swap

			# mmkkddiirr	//eexxppoorrtt//cclliieenntt//rroooott//sswwaapp
			# dddd iiff==//ddeevv//zzeerroo ooff==//eexxppoorrtt//cclliieenntt//sswwaapp bbss==44kk ccoouunntt==44kk
			# eecchhoo ''//eexxppoorrtt//cclliieenntt//sswwaapp --mmaapprroooott==rroooott::wwhheeeell	cclliieenntt..tteesstt..nneett'' >>>> //eettcc//eexxppoorrttss
			# //eettcc//rrcc..dd//mmoouunnttdd rreessttaarrtt
		  This creates a 16 MB swap file and exports it
		  to the client.

	      --	  Create device	nodes

			# ccdd //eexxppoorrtt//cclliieenntt//rroooott//ddeevv
			# ..//MMAAKKEEDDEEVV aallll

		  This procedure only works on NetBSD hosts.

	      --	  Set up the client's fstab(5)

		  Create a file	in _/_e_x_p_o_r_t_/_c_l_i_e_n_t_/_r_o_o_t_/_e_t_c_/_f_s_t_a_b
		  with the following lines:

			server:/export/client/swap   none  swap	 sw,nfsmntpt=/swap
			server:/export/client/root   /	   nfs	 rw 0 0

	      --	  Set up the client's rc.conf(5)

		  Edit _/_e_x_p_o_r_t_/_c_l_i_e_n_t_/_r_o_o_t_/_e_t_c_/_r_c_._c_o_n_f

			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.

	      --	  Set up the client's hosts(5) file.

		  Edit _/_e_x_p_o_r_t_/_c_l_i_e_n_t_/_r_o_o_t_/_e_t_c_/_h_o_s_t_s

			::1			localhost
			127.0.0.1		localhost
			192.168.1.10 client.test.net client
			192.168.1.5  server.test.net server

	 7.   Setting up the server daemons

	      If you want these	services to start up every time
	      you boot your server, make sure the following lines
	      are present in your _/_e_t_c_/_r_c_._c_o_n_f:

		    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 _t_f_t_p_d line in
	      _/_e_t_c_/_i_n_e_t_d_._c_o_n_f remains uncommented.

	 Skip forward to _I_n_s_t_a_l_l_i_n_g _t_h_e	_N_e_t_B_S_D _S_y_s_t_e_m

     ++oo	 _P_r_e_p_a_r_i_n_g _a _S_C_S_I _o_r _I_D_E _d_r_i_v_e _w_i_t_h _t_h_e	_C_D_-_R _i_m_a_g_e

	 If the	NetBSD/macppc CD-R 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	disk image
	 _N_e_t_B_S_D_-_1_0_._1___S_T_A_B_L_E_-_m_a_c_p_p_c_._i_s_o 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	disk image has a `partition zero'
	 bootloader which ultimately loads the installation ker-
	 nel from the ISO file system on the disk image.

	 --   _F_r_o_m _a_n _U_N_I_X_-_l_i_k_e _m_a_c_h_i_n_e _(_i_n_c_l_u_d_i_n_g _M_a_c_O_S	_X_)

		   # dddd	iiff==NNeettBBSSDD--1100..11__SSTTAABBLLEE--mmaaccppppcc..iissoo ooff==//ddeevv//rrssdd00cc

	     where _/_d_e_v_/_r_s_d_0_c 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.

	 --   _F_r_o_m _a _W_i_n_d_o_w_s _m_a_c_h_i_n_e

	     Get rraawwrriittee3322..eexxee from
		   hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//~~mmaarrttiinn//rraawwrriittee3322//

	     Be	certain	you have selected the correct disk, as it
	     will erase	the contents.

	 --   _F_r_o_m _a _M_a_c_O_S _9 _(_o_r	_e_a_r_l_i_e_r_) _m_a_c_h_i_n_e

	     Get ssuunnttaarr	from
		   hhttttpp::////hhyyppeerraarrcchhiivvee..llccss..mmiitt..eedduu//HHyyppeerrAArrcchhiivvee//AArrcchhiivvee//ccmmpp//ssuunnttaarr--222233..hhqqxx

	     1.	  Open the `Preferences' menu and pick `Expert
		  Mode'

	     2.	  Open the `File' menu and pick	`Open Device ...'

	     3.	  Click	on the ``scan SCSI'' button to get a list
		  of which drives are attached.

	     4.	  Pick the correct drive.  Be certain you have
		  selected the correct disk, as	it will	erase the
		  contents.

	     5.	  Open the `Special' menu and pick `Overwrite
		  Sectors ...'

	     6.	  Hit return (i.e. start at sector number zero)

	     7.	  Select _N_e_t_B_S_D_-_1_0_._1___S_T_A_B_L_E_-_m_a_c_p_p_c_._i_s_o and click
		  ``Open''

	     8.	  Open the `File' menu and pick	`Close Device'

   IInnssttaalllliinngg tthhee NNeettBBSSDD SSyysstteemm
     _O_p_e_n _F_i_r_m_w_a_r_e _b_o_o_t	_s_y_n_t_a_x

     The syntax	of the Open Firmware bboooott command is:

	   boot	boot-device [boot-file]	[-as]

     where the boot-device describes where to find the boot-
     loader, 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(8)	by listing the device, the partition (if it's a
     disk), and	the filename of	the bootloader (if using
     _o_f_w_b_o_o_t_._x_c_f).

     If	the boot-file is on the	same device and	partition (if
     it's a disk) 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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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 net-
     booted 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 ddeevv
     and llss commands.  ddeevv is similar to the unix ccdd command and
     is	used to	change between the nodes in the	Open Firmware
     device tree (similar to a file system).  llss of course is
     similar to	the unix llss command and	is used	to list	the con-
     tents of the current device node.	To get a listing of all
     the devices available in your system, use the following com-
     mands:

	   0 > ddeevv //
	   0 > llss

     Open Firmware has device aliases which are	simple names for
     the full hardware path to a device	(similar to aalliiaass in
     csh(1) ). You can find out	what device aliases Apple created
     on	your machine with the ddeevvaalliiaass command.	 For example,
     here are the devaliases on	a PowerMacintosh 7300:

	   0 > ddeevvaalliiaass
	   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		      internal hard drive
	    cd		      CD-ROM drive
	    zip		      internal Zip drive
	    enet	      ethernet
	    fd		      floppy drive
	    scsi	      SCSI bus
	    scsi-int	      internal SCSI bus	(on systems with
											 multiple
											 SCSI
											 busses)
	    ata		      ATA/IDE bus
	    ideN	      ATA/IDE bus number N
	    ultraN	      Ultra/66 or Ultra/100 IDE	bus
											 number
											 N

     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 ddeevv and llss commands.
     For example, here are the devices on the internal SCSI bus
     of	a PowerMacintosh 7300:

	   0 > ddeevv ssccssii--iinntt
	   0 > llss
	   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 infor-
     mation 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
     sshhooww--cchhiillddrreenn command:

	   0 > ddeevv ssccssii--iinntt
	   0 > sshhooww--cchhiillddrreenn
	   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'' num-
     ber 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 > ddeevv ssccssii--iinntt//ssdd@@33
	   0 > wwoorrddss
	   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 wwoorrdd ``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''	boot-
     loader, 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 (or earlier).  You	can use	ppddiisskk to get a listing of
     the partitions on a disk.	See the	Partitioning HOW-TO for
     help:
	   hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//ppaarrttiittiioonniinngg..hhttmmll##ppddiisskk

     Typically,	MS-DOS and ISO9660 formatted disks have	their
     file systems at partition 1.  Typically, Drive Setup format-
     ted disks have their file systems starting	at partition num-
     ber 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 _\ char-
     acter) to separate	directories.  The bootloader uses forward
     slashes (the _/ character) to separate directories when spec-
     ifying the	boot-file.  Thus, to specify the top of	the file
     system on a CD-ROM	in the example PowerMacintosh 7300 sys-
     tem, 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 ddiirr	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 ddiirr	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.  The one exception
     to	this rule is that Open Firmware	cannot list files on a
     disk with a `partition zero' bootloader (including	the
     NetBSD/macppc CD-R	image and installation floppies).

	   0 > ddiirr ffdd::,,\\
	   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
     You can see that this MS-DOS formatted disk has a bunch of
     stuff, as well as the two important files:	_N_E_T_B_S_D_~_1_._G_Z and
     _O_F_W_B_O_O_T_._X_C_F.  Note	that MacOS shortened _n_e_t_b_s_d_-_G_E_N_E_R_I_C___M_D_._g_z
     to	_N_E_T_B_S_D_~_1_._G_Z since MS-DOS file systems can only natively
     hold 8 characters for the filename.

     _N_o_t_e_:  Keep in mind that Open Firmware is often case-sensi-
	    tive when it comes to filenames.

     _N_o_t_e_:  You	may need to append a _;_1	to the filename	when
	    using a ISO	9660 file system.  This	``version
	    number'' is	part of	the ISO	9660 specification and
	    will show up in the	directory listing if it	is
	    present on the disk.  For example:

		  0 > bboooott ccdd::,,\\OOFFWWBBOOOOTT..XXCCFF;;11 NNEETTBBSSDD..MMAACCPPPPCC;;11

     _N_o_t_e_:  PowerPC 601	machines need to specify the _N_E_T_B_S_D_._6_0_1
	    kernel when	booting	from the install CD, and use the
	    _k_e_r_n_-_G_E_N_E_R_I_C___6_0_1_._t_g_z and _n_e_t_b_s_d_-_I_N_S_T_A_L_L___6_0_1_._g_z ker-
	    nels.

     If	the ddiirr	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(8) 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:
	   hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//ffaaqq..hhttmmll##ooffww--uussee
	   hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//ffaaqq..hhttmmll##bboooott--ppccii

     _E_x_a_m_p_l_e_s _o_f _O_p_e_n _F_i_r_m_w_a_r_e _b_o_o_t _c_o_m_m_a_n_d_s

     Here are some examples of the commands you	might use to boot
     your system:

     ++oo	 _B_o_o_t_i_n_g _t_h_e _N_e_t_B_S_D_/_m_a_c_p_p_c _i_n_s_t_a_l_l _C_D_-_R
	 (Open Firmware	1.0.5, Open Firmware 1.1.22, Open
	 Firmware 2.0.x, Open Firmware 2.4)

	 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 > bboooott	ccdd::00 NNEETTBBSSDD..MMAACCPPPPCC
	       0 > bboooott	ccdd::00 NNEETTBBSSDD..660011
	       0 > bboooott	ssccssii--iinntt//ssdd@@33::00	NNEETTBBSSDD..MMAACCPPPPCC
	       0 > bboooott	ssccssii//ssdd@@33::00 NNEETTBBSSDD..MMAACCPPPPCC
	       0 > bboooott	aattaa//aattaappii--ddiisskk::00 NNEETTBBSSDD..MMAACCPPPPCC
	       0 > bboooott	iiddee11//ddiisskk@@00::00 NNEETTBBSSDD..MMAACCPPPPCC

     ++oo	 _B_o_o_t_i_n_g _t_h_e _N_e_t_B_S_D_/_m_a_c_p_p_c _i_n_s_t_a_l_l _C_D_-_R
	 (Open Firmware	3)

	       0 > bboooott	ccdd::,,\\ooffwwbboooott..xxccff nneettbbssdd..mmaaccppppcc

     ++oo	 _B_o_o_t_i_n_g _t_h_e _N_e_t_B_S_D _i_n_s_t_a_l_l _f_l_o_p_p_i_e_s
	 (Open Firmware	1.0.5, Open Firmware 1.1.22, Open
	 Firmware 2.0.x, Open Firmware 2.4)

	 The first floppy disk has a `partition	zero' bootloader.
	 When it has loaded the	kernel,	it will	ask you	to insert
	 the second floppy disk.

	 _N_o_t_e_:	This is	not a normal MacOS boot	floppy -- you
		must enter Open	Firmware and type a boot command.
	 All you need to do is:

	       0 > bboooott	ffdd::00

	 It is common to see ``READ TIMEOUT@'' from the	floppy.
	 This means that Open Firmware is having difficulty read-
	 ing the media.	 See the section below on _C_o_m_m_o_n _P_r_o_b_l_e_m_s
	 _a_n_d _E_r_r_o_r _M_e_s_s_a_g_e_s for	more information about this and
	 what you can do to get	a successful boot.

	 You can eject a floppy	by typing:

	       0 > eejjeecctt ffdd

     ++oo	 _B_o_o_t_i_n_g _a_n _I_D_E	_o_r _S_C_S_I	_d_r_i_v_e _w_i_t_h _a_n _H_F_S _o_r _H_F_S_+
	 _p_a_r_t_i_t_i_o_n
	 (Open Firmware	2.4, Open Firmware 3)

	 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 parti-
	 tion 9.  You may need to keep trying higher partition
	 numbers until you find	the one	that has your bootloader.
	 You can use ppddiisskk to print out	your partition map:
	       hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//ppaarrttiittiioonniinngg..hhttmmll##ppddiisskk

	 You should use	the Open Firmware ddiirr 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 > bboooott	hhdd::99,,\\ooffwwbboooott..xxccff nneettbbssdd--GGEENNEERRIICC__MMDD..ggzz
	       0 > bboooott	ssccssii//ssdd@@00::99,,\\ooffwwbboooott..xxccff nneettbbssdd--GGEENNEERRIICC__MMDD..ggzz
	       0 > bboooott	iiddee00//ddiisskk@@00::1100,,\\ooffwwbboooott..xxccff nneettbbssdd--GGEENNEERRIICC__MMDD..ggzz
	       0 > bboooott	uullttrraa11::99,,ooffwwbboooott..xxccff nneettbbssdd--GGEENNEERRIICC__MMDD..ggzz

     ++oo	 _B_o_o_t_i_n_g _a _c_u_s_t_o_m _C_D_-_R_O_M
	 (All Open Firmware versions)

	 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 ddiirr command to get a listing of
	 the files on your CD.

	 For instance, TTooaasstt for MacOS creates CDs with	long
	 filenames, but	uses MS-DOS style short	names as well.
	 Instead of referencing	_n_e_t_b_s_d_-_G_E_N_E_R_I_C you would need to
	 open _N_E_T_B_S_D_-_G_._E_N_E The mmkkiissooffss program has a similar
	 problem, _n_e_t_b_s_d_-_G_E_N_E_R_I_C___M_D_._g_z becomes
	 _N_E_T_B_S_D_-_G_E_N_E_R_I_C___M_D_._G_Z.

	 Another thing to note is that you _m_u_s_t	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
	 _n_e_t_b_s_d_._g_z 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 > bboooott	ccdd::,,\\ooffwwbboooott..xxccff nneettbbssdd..ggzz
	       0 > bboooott	ssccssii--iinntt//ssdd@@33::,,\\OOFFWWBBOOOOTT..XXCCFF NNEETTBBSSDD..GGZZ
	       0 > bboooott	ssccssii//ssdd@@33::,,\\OOFFWWBBOOOOTT..XXCCFF	NNEETTBBSSDD..GGZZ
	       0 > bboooott	aattaa//aattaappii--ddiisskk::,,\\OOFFWWBBOOOOTT..XXCCFF NNEETTBBSSDD..GGZZ
	       0 > bboooott	iiddee11//ddiisskk@@00::,,\\OOFFWWBBOOOOTT..XXCCFF NNEETTBBSSDD..GGZZ

     ++oo	 _B_o_o_t_i_n_g _a_n _M_S_-_D_O_S _f_l_o_p_p_y
	 (Open Firmware	1.0.5, Open Firmware 1.1.22, Open
	 Firmware 2.0.x, Open Firmware 2.4)

	 _N_o_t_e_:	This is	not a normal MacOS boot	floppy -- you
		must enter Open	Firmware and type a boot command.

	 Use the Open Firmware ddiirr command to get a listing of
	 the files on the floppy.  Typically you'll find file-
	 names like OFWBOOT.XCF	and NETBSD~1.GZ.

	       0 > bboooott	ffdd::,,\\OOFFWWBBOOOOTT..XXCCFF NNEETTBBSSDD~~11..GGZZ

	 You can eject a floppy	by typing:

	       0 > eejjeecctt ffdd

     ++oo	 _B_o_o_t_i_n_g _o_v_e_r _t_h_e _e_t_h_e_r_n_e_t
	 (Open Firmware	1.0.5, Open Firmware 1.1.22, Open
	 Firmware 2.0.x, Open Firmware 2.4)

	 You can try the simple	form (i.e. that	you are	booting
	 from ethernet):

	       0 > bboooott	eenneett::,,ooffwwbboooott..xxccff

	 Or you	may be more specific, specifying the bootloader
	 filename and the kernel name:

	       0 > bboooott	eenneett::,,ooffwwbboooott..xxccff eenneett::,,//nneettbbssdd--GGEENNEERRIICC__MMDD..ggzz

	 _N_o_t_e_:	Some Open Firmware 1.0.5 machines have their MAC
		address	stored incorrectly.  Make sure that your
		netboot	server is using	the same MAC address that
		your macppc client is using.  See the section on
		_S_e_t_t_i_n_g	_u_p _O_p_e_n	_F_i_r_m_w_a_r_e _1 _a_n_d _2 _t_o _b_o_o_t _N_e_t_B_S_D
		to figure out your MAC address.

	 _N_o_t_e_:	Some machines cannot load compressed kernels over
		ethernet.  Uncompress them first.

     ++oo	 _B_o_o_t_i_n_g _o_v_e_r _t_h_e _e_t_h_e_r_n_e_t
	 (Open Firmware	3)

	 You can try the simple	form (i.e. that	you are	booting
	 from ethernet):

	       0 > bboooott	eenneett::00

	 Or you	may be more specific, specifying the bootloader
	 filename and the kernel name:

	       0 > bboooott	eenneett::00,,ooffwwbboooott..xxccff eenneett::00,,//nneettbbssdd--GGEENNEERRIICC__MMDD..ggzz

     ++oo	 _B_o_o_t_i_n_g _a_n _I_D_E	_o_r _S_C_S_I	_d_r_i_v_e _w_i_t_h _a `_p_a_r_t_i_t_i_o_n	_z_e_r_o'
	 _b_o_o_t_l_o_a_d_e_r
	 (Open Firmware	1.0.5, Open Firmware 1.1.22, Open
	 Firmware 2.0.x, Open Firmware 2.4)

	 You do	not specify a file to load, since the `partition
	 zero' bootloader knows	what to	do.  You would boot such
	 a system if you have dumped the CD-R 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 > bboooott	zziipp::00
	       0 > bboooott	ssccssii--iinntt//ssdd@@00::00
	       0 > bboooott	ssccssii//ssdd@@00::00
	       0 > bboooott	aattaa//aattaa--ddiisskk@@00::00
	       0 > bboooott	aattaa//AATTAA--DDiisskk@@00::00
	       0 > bboooott	iiddee00//ddiisskk@@00::00

     _E_x_a_m_p_l_e _o_f	_a _n_o_r_m_a_l _b_o_o_t

     Of	course,	a lot of the information in this example depends
     on	your model and what your boot method is, but we'll
     include this anyways just so you get an idea of what to
     expect (user-typed	commands are in	bboolldd).

	    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 > bboooott eenneett::,,ooffwwbboooott..xxccff nneettbbssdd--GGEENNEERRIICC__MMDD..ggzz
	    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 ?

     _C_o_m_m_o_n _P_r_o_b_l_e_m_s _a_n_d _E_r_r_o_r _M_e_s_s_a_g_e_s

     This is a brief list of some of the Open Firmware problems
     you may run into.	See the	NetBSD/macppc FAQ for a	thorough
     list.
	   hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//ffaaqq..hhttmmll##bboooott--ttrroouubbllee

     _N_o_t_e_:  You	may find it necessary to remove	all non-Apple
	    devices from your machine.	Some users have	found
	    this necessary.

     ++oo	 Black screen

	 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.

	 Open Firmware 3.x and newer often won't setup the con-
	 sole if you don't drop	to a prompt, and NetBSD	doesn't
	 know how to setup the console itself.	To get the system
	 to boot when you have auto-boot? set to true, you can
	 try this workaround.  First, try one of the following
	 commands:

	       setenv boot-command " screen" output boot
	       setenv boot-command ." screen" output boot
	       setenv boot-command ." Booting NetBSD..." cr "
	       screen" output boot

	 You should follow the command with:

	       reset-all

	 This will cause Open Firmware to output some text to the
	 screen	prior to booting, thus forcing it to setup the
	 console.

	 Otherwise, you	need a serial console.	See the	section
	 entitled _O_p_e_n _F_i_r_m_w_a_r_e	_1 _a_n_d _2	_S_y_s_t_e_m _P_r_e_p_a_r_a_t_i_o_n

     ++oo	 Grey screen with flashing question mark

	 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 has
	 bad syntax.

	 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	globe icon means that
	 your machine is looking for a netboot server.	A happy
	 face or spinning disc means it's starting to boot MacOS.

	 The boot floppy does not have a bootable MacOS	file sys-
	 tem, it has a bootable	NetBSD file system.

	 Reboot, re-enter Open Firmware	and check your syntax
	 carefully.

	 _N_o_t_e_:	Don't forget to	check your Open	Firmware environ-
		ment variables,	as they	may have been changed by
		your brief excursion into MacOS.

     ++oo	 Information on	your screen seems garbled or out of sync

	 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 _O_p_e_n _F_i_r_m_w_a_r_e _1
	 _a_n_d _2 _S_y_s_t_e_m _P_r_e_p_a_r_a_t_i_o_n

	 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.

     ++oo	 ``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.

     ++oo	 ``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 _S_e_t_t_i_n_g _u_p _O_p_e_n _F_i_r_m_w_a_r_e _1 _a_n_d _2 _t_o
	 _b_o_o_t _N_e_t_B_S_D

	 Do not	change load-base on an Open Firmware 3 system.

	 Reset your system and try using a different boot command
	 (this is the only way some people have	gotten their Open
	 Firmware 2.4 systems to work):

	       0 > 00 bboooottrr bboooott--ddeevviiccee bboooott--ffiillee

	 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 rreesseett--aallll command.

	 Contradictorily, if your machine is Open Firmware ver-
	 sion 1.0.5, 2.0.x or 2.4, this	error does sometimes
	 appear	randomly.  You might try the boot command a sec-
	 ond 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.

     ++oo	 ``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 NetBSD	ppddiisskk command to list the partition map
	 and the Open Firmware ddiirr command to verify that the
	 file(s) you tried accessing are really	there.

     ++oo	 ``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 _o_f_w_b_o_o_t_._x_c_f)
	 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.

     ++oo	 ``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 parti-
	 tions).

     ++oo	 ``READ	TIMEOUT@''

	 Open Firmware is having trouble reading your floppy
	 disk.	Things to try:
	 --   Try booting from the floppy again
	 --   Try a different floppy disk
	 --   Try writing the floppy on the same	machine	you're
	     trying to boot
	 --   Clean the floppy drive
	 --   Use another boot method

	 As disk drives	get older, especially with portables,
	 they can get a	little bit out of alignment so that they
	 do not	consistently read disks	written	on other floppy
	 drives.  Strongly consider writing the	floppies on the
	 same machine that will	be reading them.

     ++oo	 ``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	specify-
	 ing the location of the bootloader.  Unfortunately, on
	 the early models, _o_f_w_b_o_o_t_._x_c_f 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 com-
	 mand like:

	       0 > bboooott	eenneett::,,ooffwwbboooott..xxccff

     ++oo	 ``enet:,/netbsd.ram.gz: Inappropriate file type or
	 format''

	 Some systems booting over ethernet can't load compressed
	 kernels.  Use gunzip(1) to uncompress the kernel before
	 attempting to netboot.

     ++oo	 Bootloader hangs before the copyright notice and the
	 kernel	configuration

	 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
	 _S_e_t_t_i_n_g _u_p _O_p_e_n _F_i_r_m_w_a_r_e _1 _a_n_d	_2 _t_o _b_o_o_t _N_e_t_B_S_D

	 Do not	set real-base on an Open Firmware 3 system.

     ++oo	 Hang after configuring	devices, but before doing any-
	 thing else

	 Actually, this	can have many causes.  The most	likely is
	 a keyboard problem.  First, try plugging the USB key-
	 board directly	into the computer (i.e.	not through a
	 hub) and unplugging the mouse.

	 If you're trying a model that's not on	the supported
	 list (such as a new laptop model), they keyboard may not
	 be supported yet.

     _M_i_l_e_s_t_o_n_e

     If	you've reached this point, then	you must've gotten the
     NetBSD installer to boot.	Congratulations!  That was the
     hard part.	 From now through the rest of this document,
     there should be no	more Open Firmware specific problems, so
     read everything because it	applies	to all models.

     _R_u_n_n_i_n_g _t_h_e _s_y_s_i_n_s_t _i_n_s_t_a_l_l_a_t_i_o_n _p_r_o_g_r_a_m

     1.	  _I_n_t_r_o_d_u_c_t_i_o_n

	  Using	ssyyssiinnsstt, installing NetBSD is a	relatively easy
	  process.  Still, you should read this	document and have
	  it available during the installation process.	 This
	  document tries to be a good guide to the installation,
	  and as such, covers many details for the sake	of com-
	  pleteness.  Do not let this discourage you; the install
	  program is not hard to use.

     2.	  _G_e_n_e_r_a_l

	  The following	is a walk-through of the steps you will
	  take while installing	NetBSD on your hard disk.
	  ssyyssiinnsstt is a menu-driven program that	guides you
	  through the installation process.  Sometimes questions
	  will be asked, and in	many cases the default answer
	  will be displayed in brackets	(``[ ]'') after	the ques-
	  tion.	 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 _/_s_y_s_i_n_s_t program from the	command	prompt.
	  It is	not necessary to reboot.

     3.	  _Q_u_i_c_k	_i_n_s_t_a_l_l

	  First, let's describe	a quick	install.  The other sec-
	  tions	of this	document go into the installation proce-
	  dure 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 / DVD as the	install	medium.

	  ++oo   What you need.

	      --	  The distribution sets	(in this example, they
		  are on the CD	or DVD).

	      --	  Some form of bootable	media, described above.

	      --	  A minimum of 16 MB of	memory installed.

	      --	  An optical drive.

	      --	  A hard drive with at least 600 MB of free space
		  for a	complete base install, not including room
		  for swap.  If	you wish to install the	X Window
		  System as well, you will need	at least 225 MB
		  more.

	  ++oo   The Quick	Installation

	      --	  Boot the system as described above.  You should
		  be at	the ssyyssiinnsstt main menu.

			  .***********************************************.
			  * NetBSD-10.1_STABLE 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				  *
			  * f: Config menu				  *
			  * x: Exit Install System			  *
			  .***********************************************.

	      --	  If you wish, you can configure some network
		  settings immediately by choosing the UUttiilliittyy
		  mmeennuu and then	CCoonnffiigguurree nneettwwoorrkk.  It isn't
		  actually required at this point, but it may be
		  more convenient.  Go back to the main	menu.

	      --	  Choose UUttiilliittyy mmeennuu then RRuunn //bbiinn//sshh for Open
		  Firmware 3 systems.  You'll need to create the
		  NetBSD filesystem(s) and an _f_s_t_a_b.  Now exit
		  the shell, return to the main	menu, and choose
		  RRee--iinnssttaallll.

		  Choose IInnssttaallll for Open Firmware 1.0.5, 1.1.22,
		  2.0.x, and 2.4 systems.

	      --	  You will be guided through the setup of your
		  disk.

	      --	  You will be asked to choose which distribution
		  sets to install.

	      --	  When prompted, choose	CCDD--RROOMM as the install
		  medium if booted from	CD-ROM.	 The default val-
		  ues for the path and device should be	OK.

	      --	  After	the installation process has completed,
		  you will be brought back to the main menu,
		  where	you should select RReebboooott..

	      --	  Once the system reaches the Open Firmware
		  prompt, you will need	to type	the correct com-
		  mand to boot from your hard drive.

	      --	  NetBSD will now boot.	 If you	didn't set a
		  password for the root	user when prompted by
		  ssyyssiinnsstt, logging in as root and setting a pass-
		  word should be your first task.  You are also
		  advised to read afterboot(8).

     4.	  _B_o_o_t_i_n_g _N_e_t_B_S_D

	  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	ssyyssiinnsstt	which disk to use.  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 mes-
	  sages, you will be presented with a welcome message and
	  a main menu.	It will	also include instructions for
	  using	the menus.

     5.	  _N_e_t_w_o_r_k _c_o_n_f_i_g_u_r_a_t_i_o_n

	  If you do not	intend to use networking during	the
	  installation,	but you	do want	your machine to	be con-
	  figured for networking once the system is installed,
	  you should first go to the UUttiilliittyy mmeennuu and select the
	  CCoonnffiigguurree nneettwwoorrkk option.  If	you only want to tempo-
	  rarily 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 when	asked to provide a server.

     6.	  _P_r_e_p_a_r_i_n_g _a _d_i_s_k _w_h_i_c_h _w_i_l_l _b_e _u_s_e_d _f_o_r _O_p_e_n _F_i_r_m_w_a_r_e	_3
	  _s_y_s_t_e_m_s

	  Skip this step if you	are installing NetBSD on an Open
	  Firmware 1 or	2 system.

	  Go to	the UUttiilliittyy MMeennuu, and select the RRuunn //bbiinn//sshh
	  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.	Unfortu-
	  nately, at the moment, our install tools aren't smart
	  enough to deal with drives with Apple	Partition Maps
	  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:
		# ssttttyy eerraassee ''^^hh''
		# ssttttyy eerraassee ''^^??''

	  Type the following command (replacing	_w_d_0 with the name
	  of your destination hard drive):
		# ddiisskkllaabbeell wwdd00

	  This will print out the partition info that was gener-
	  ated by ppddiisskk, Drive Setup, or Disk Utility.	Note
	  that,	as discussed above in the _P_a_r_t_i_t_i_o_n_i_n_g _y_o_u_r _h_a_r_d
	  _d_r_i_v_e	_f_o_r _N_e_t_B_S_D section, your _A_/_U_X _R_o_o_t typically is
	  the first partition (_a) and your _A_/_U_X	_S_w_a_p typically is
	  the second partition (_b).  You may also find that your
	  _A_/_U_X _U_s_e_r partition is the seventh partition (_g).  For
	  example:

		      #	ddiisskkllaabbeell wwdd00
		[...]
		#	 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.

	  _D_o _n_o_t _m_o_d_i_f_y	_a_n_y _p_a_r_t_i_t_i_o_n_s _l_a_b_e_l_e_d _H_F_S, _U_F_S, _o_r
	  _u_n_k_n_o_w_n.  The	partitions you will be using have their
	  _f_s_t_y_p_e listed	as _4_._2_B_S_D.

	  Run the nneewwffss	command	on the _4_._2_B_S_D partitions:

		      #	nneewwffss //ddeevv//wwdd00aa
		newfs: /dev/wd0a: not a	character-special device
		Warning: 120 sector(s) in last cylinder	unallocated
		/dev/wd0a:	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/wd0a: can't	rewrite	disk label
	  You can ignore the _~ `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:
		# mmoouunntt	//ddeevv//wwdd00aa //mmnntt

	  Make an _f_s_t_a_b	file for your new system (right	now, you
	  only really need to include _/, _/_u_s_r, and _s_w_a_p), for
	  example:
		# mmkkddiirr	//mmnntt//eettcc
		# ccaatt >>	//mmnntt//eettcc//ffssttaabb
		/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.
	  CONTROL-D finishes and writes	the file to disk.

	  Great, now create the	mountpoints for	the file systems
	  you listed in	the _f_s_t_a_b:
		# mmkkddiirr	//mmnntt//uussrr

	  Clean	up and return to ssyyssiinnsstt:
		# ccdd //
		# uummoouunntt //mmnntt
		# eexxiitt

     7.	  _I_n_s_t_a_l_l_a_t_i_o_n _d_r_i_v_e _s_e_l_e_c_t_i_o_n _a_n_d _p_a_r_a_m_e_t_e_r_s

	  To start the installation onto a dedicated NetBSD drive
	  (Open	Firmware 1 or 2), select IInnssttaallll NNeettBBSSDD	ttoo hhaarrdd
	  ddiisskk from the	main menu.  To start the installation
	  onto a drive with an Apple Partition Map (Open Firmware
	  3), select RRee--iinnssttaallll	sseettss oorr	iinnssttaallll	aaddddiittiioonnaall sseettss
	  from the main	menu.

	  The first thing is to	identify the disk on which you
	  want to install NetBSD.  ssyyssiinnsstt will	report a list of
	  disks	it finds and ask you for your selection.  You
	  should see disk names	like wd0, wd1, sd0 or sd1.

	  If ssyyssiinnsstt 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 _F_A_Q _e_n_t_r_y_:
		hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//ffaaqq..hhttmmll##nnooddiisskk.

     8.	  _S_e_l_e_c_t_i_n_g _w_h_i_c_h _s_e_t_s _t_o _i_n_s_t_a_l_l

	  The next step	is to choose which distribution	sets you
	  wish to install.  Options are	provided for full, mini-
	  mal, and custom installations.  If you choose	sets on
	  your own, bbaassee, eettcc, and a kernel must be selected.

     9.	  _P_a_r_t_i_t_i_o_n_i_n_g _t_h_e _d_i_s_k

	  You can skip a few steps, down to `_G_e_t_t_i_n_g _t_h_e
	  _d_i_s_t_r_i_b_u_t_i_o_n _s_e_t_s', if you are installing onto a drive
	  with an Apple	Partition Map (Open Firmware 3), i.e.,
	  you selected RRee--iinnssttaallll sseettss oorr iinnssttaallll aaddddiittiioonnaall sseettss
	  from the main	menu.

     10.  _E_d_i_t_i_n_g _t_h_e _N_e_t_B_S_D _d_i_s_k_l_a_b_e_l

	  The partition	table of the NetBSD part of a disk is
	  called a _d_i_s_k_l_a_b_e_l.  In actuality, NetBSD/macppc uses
	  an Apple Partition Map.  The installer creates some-
	  thing	like a real Apple Partition Map, but it	is not
	  compatible with Mac OS or Open Firmware, which is one
	  of the reasons why you cannot	use this installer to
	  partition a disk that	can be used with Mac OS	or Open
	  Firmware 3 systems.

	  If your disk already has a disklabel written to it, you
	  can choose UUssee eexxiissttiinngg ppaarrttiittiioonn ssiizzeess.  Otherwise,
	  select SSeett ssiizzeess ooff NNeettBBSSDD ppaarrttiittiioonnss.

	  After	you have chosen	your partitions	and their sizes
	  (or if you opted to use the existing partitions), you
	  will be presented with the layout of the NetBSD diskla-
	  bel and given	one more 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4..22BBSSDD.
	  A swap partition has a special type called sswwaapp.  Some
	  partitions in	the disklabel have a fixed purpose.

		a	Root partition (_/)

		b	Swap partition.

		c	The entire disk.

		d-p	Available for other use.  Traditionally,
			g is the partition mounted on _/_u_s_r, but
			this is	historical practice and	not a
			fixed value.

	  You will then	be asked to name your disk's disklabel.
	  The default response will be OK for most purposes.  If
	  you choose to	name it	something different, make sure
	  the name is a	single word and	contains no special char-
	  acters.  You don't need to remember this name.

     11.  _P_r_e_p_a_r_i_n_g _y_o_u_r _h_a_r_d _d_i_s_k

	  _Y_o_u _a_r_e _n_o_w _a_t _t_h_e _p_o_i_n_t _o_f _n_o _r_e_t_u_r_n.  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, select
	  yyeess.

	  The install program will now label your disk and create
	  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.  Other-
	  wise,	you can	continue the installation program after
	  pressing the return key.

	  _N_o_t_e_:	 The bootstrapping code	installed in this step
		 will _n_o_t boot a machine with Open Firmware 3.
		 You will still	need to	have _o_f_w_b_o_o_t_._x_c_f on an
		 HFS or	HFS+ partition.

     12.  _G_e_t_t_i_n_g _t_h_e _d_i_s_t_r_i_b_u_t_i_o_n _s_e_t_s

	  The NetBSD distribution consists of a	number of _s_e_t_s
	  that come in the form	of gzipped tar files.  At this
	  point, 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
	  transfer the sets to your hard disk, others will
	  extract the sets directly.

	  For all these	methods, the first step	is to make the
	  sets available for extraction.  The sets can be made
	  available in a few different ways.  The following sec-
	  tions	describe each of the methods.  After reading
	  about	the method you will be using, you can continue to
	  the section labeled `Extracting the distribution sets'.

     13.  _I_n_s_t_a_l_l_a_t_i_o_n _f_r_o_m _C_D_-_R_O_M

	  When installing from a CD-ROM, you will be asked to
	  specify the device name for your CD-ROM drive	(usually
	  cd0) and the directory name on the CD-ROM where the
	  distribution files are.

	  ssyyssiinnsstt will then check that the files are actually
	  present in the specified location and	proceed	to the
	  extraction of	the sets.

     14.  _I_n_s_t_a_l_l_a_t_i_o_n _u_s_i_n_g _F_T_P

	  To install using FTP,	you first need to configure your
	  network setup	if you haven't already done so.	 ssyyssiinnsstt
	  will help you	with this, asking if you want to use
	  DHCP.	 If you	do not use DHCP, you can enter network
	  configuration	details	yourself.  If you do not have DNS
	  set up for the machine that you are installing on, you
	  can just press RETURN	in answer to this question, 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, you will need to spec-
	  ify an IP address instead of a hostname for the FTP
	  server.

	  ssyyssiinnsstt will then transfer the set files from	the
	  remote site to your hard disk.

     15.  _I_n_s_t_a_l_l_a_t_i_o_n _u_s_i_n_g _N_F_S

	  To install using NFS,	you first need to configure your
	  network setup	if you haven't already done so.	 ssyyssiinnsstt
	  will do this for you,	asking you if you want to use
	  DHCP.	 If you	do not use DHCP, you can enter network
	  configuration	details	yourself.  If you do not have DNS
	  set up for the machine that you are installing on, you
	  can just press RETURN	in answer to this question, 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, you will need to specify an
	  IP address instead of	a hostname for the NFS server.

     16.  _I_n_s_t_a_l_l_a_t_i_o_n _f_r_o_m _a_n _u_n_m_o_u_n_t_e_d _f_i_l_e _s_y_s_t_e_m

	  In order to install from a local file	system,	you will
	  need to specify the device that the file system resides
	  on (for example wd1e), the type of the file system, and
	  the directory	on the specified file system where the
	  sets are located.  ssyyssiinnsstt will then check if	it can
	  indeed access	the sets at that location.  Remember,
	  NetBSD/macppc	doesn't	grok HFS or HFS+ partitions

     17.  _I_n_s_t_a_l_l_a_t_i_o_n _f_r_o_m _a _l_o_c_a_l _d_i_r_e_c_t_o_r_y

	  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.
	  ssyyssiinnsstt will ask you for the name of this directory.

     18.  _E_x_t_r_a_c_t_i_n_g _t_h_e _d_i_s_t_r_i_b_u_t_i_o_n _s_e_t_s

	  A progress bar will be displayed while the distribution
	  sets are being extracted.

	  After	all the	files have been	extracted, the device
	  node files will be created.  If you have already con-
	  figured 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	configu-
	  ration files.

     19.  _C_o_n_f_i_g_u_r_e _a_d_d_i_t_i_o_n_a_l _i_t_e_m_s

	  The next menu	will allow you to select a number of
	  additional items to configure, including the time zone
	  that you're in, to make sure your clock has the right
	  offset from UTC, the root user's shell, and the initial
	  root password.

	  You can also enable installation of binary packages,
	  which	installs the pkgin(1) tool for managing	binary
	  packages for third-party software.  This will	feel
	  familiar to users of package tools such as aapptt--ggeett or
	  yyuumm.	If you prefer to install third-party software
	  from source, you can install the pkgsrc(7) tree.

	  Finally, you can enable some daemons such as sshd(8),
	  ntpd(8), or mdnsd(8).

     20.  _F_i_n_a_l_i_z_i_n_g _y_o_u_r _i_n_s_t_a_l_l_a_t_i_o_n

	  Congratulations, you have successfully installed NetBSD
	  10.1_STABLE.

     _F_i_n_a_l_i_z_i_n_g	_O_p_e_n _F_i_r_m_w_a_r_e _s_e_t_t_i_n_g_s

     Now, you can reboot to get	to the Open Firmware prompt.  You
     still need	to figure out how to get Open Firmware to boot
     the operating system(s) of	your choice.  First, try to get
     NetBSD/macppc running.  Using the methods described in the
     section _E_x_a_m_p_l_e_s _o_f _O_p_e_n _F_i_r_m_w_a_r_e _b_o_o_t _c_o_m_m_a_n_d_s figure out
     the boot command for your installation of NetBSD.	Try boot-
     ing.  Once	you've got the syntax worked out, decide which
     operating systems you'll be using regularly.

     ++oo	 _B_o_o_t_i_n_g _N_e_t_B_S_D	_e_x_c_l_u_s_i_v_e_l_y
	 If you'll only	be using NetBSD	on your	macppc system,
	 then simply set the Open Firmware `boot-device' and
	 `boot-file' variables to the values you just determined.
	 Also, you might want to enable	the system to always boot
	 NetBSD	when powered on	or reset.  Once	you set	up auto-
	 booting you can get to	the Open Firmware prompt again by
	 using the shutdown(8) command to halt the system.

	 If you	are not	using a	`partition zero' style boot
	 scheme	(e.g. Open Firmware 3 models), then you	would
	 type something	like the following:

	       0 > sseetteennvv aauuttoo--bboooott?? ttrruuee
	       0 > sseetteennvv bboooott--ddeevviiccee iiddee00//ddiisskk@@00::88,,\\ooffwwbboooott..xxccff
	       0 > sseetteennvv bboooott--ffiillee iiddee00//ddiisskk@@00::1133,,//nneettbbssdd
	       0 > rreesseett--aallll

	 The last command resets the system so that these set-
	 tings are stored.

	 If you	are using a `partition zero' style boot	scheme,
	 you would type	something like the following:

	       0 > sseetteennvv aauuttoo--bboooott?? ttrruuee
	       0 > sseetteennvv bboooott--ddeevviiccee ssccssii//ssdd@@00::00
	       0 > sseetteennvv bboooott--ffiillee nneettbbssdd
	       0 > rreesseett--aallll

	 Replace ssccssii//ssdd@@00::00 with the actual device you	will be
	 booting from.

     ++oo	 _A_d_d_i_t_i_o_n_a_l _O_p_e_n _F_i_r_m_w_a_r_e _t_i_p_s
	 If you	find that your system tries booting before your
	 hard drive has	spun up, try one of the	two following
	 `boot-command'	settings:

	       0 > sseetteennvv bboooott--ccoommmmaanndd ccaattcchh 55000000 mmss bboooott
	       0 > sseetteennvv bboooott--ccoommmmaanndd bbeeggiinn [['']] bboooott ccaattcchh 11000000 mmss ccrr aaggaaiinn

	 Also, you may be able to pause	a system at the	Open
	 Firmware prompt if you	have `auto-boot?' set to `true'
	 by holding down any key while the system is resetting.
	 Set the following `boot-command' (this	may not	work on
	 system	with Open Firmware 1.0.5) (this	method should
	 interrupt booting, even when holding down any key while
	 using a serial	console):

	       0 > sseetteennvv bboooott--ccoommmmaanndd kkeeyy?? iinnvveerrtt iiff bboooott tthheenn

     ++oo	 _B_o_o_t_i_n_g _N_e_t_B_S_D	_a_n_d _M_a_c_O_S _X _o_r _D_a_r_w_i_n
	 Alas, this takes a little more	work.  Usually,	when you
	 select	a system to boot in the	``Startup Disk'' panel of
	 the ``System Preferences'' application, it stores the
	 Open Firmware path to that device in the `boot-device'
	 variable.  So,	instead	of writing the NetBSD device path
	 to Open Firmware, you'll store	the paths to your operat-
	 ing systems in	NVRAM.	Open Firmware cannot deal with
	 nested	ddeevvaalliiaass entries.  You must, therefore,	enter the
	 _e_n_t_i_r_e	path to	your device.  See the NetBSD/macppc
	 nnvveeddiitt	HOW-TO for more	help:
	       hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//nnvveeddiitt..hhttmmll

	       0 > pprriinntteennvv bboooott--ddeevviiccee
	       boot-device /pci@f2000000/mac-io@17/ata-4@1f000/@0:10,\\:tbxi
		ok
	       0 > nnvvaalliiaass oossxx //ppccii@@ff22000000000000//mmaacc--iioo@@1177//aattaa--44@@11ff000000//@@00::1100,,\\\\::ttbbxxii
	       0 > nnvvaalliiaass bbssdd //ppccii@@ff22000000000000//mmaacc--iioo@@1177//aattaa--44@@11ff000000//@@00::99,,ooffwwbboooott..xxccff
	       0 > nnvvssttoorree
	       0 > sseetteennvv uussee--nnvvrraammrrcc?? ttrruuee
	       0 > rreesseett--aallll

	 Now, when the system is reset,	it will	stop at	the Open
	 Firmware prompt and you can type one of the following to
	 boot an operating system:

	       0 > bboooott	oossxx
	       0 > bboooott	bbssdd

     ++oo	 _B_o_o_t_i_n_g _N_e_t_B_S_D	_a_n_d _M_a_c_O_S _9 _o_r _e_a_r_l_i_e_r
	 For Open Firmware 3 systems, the procedure is identical
	 to the	section	above on _B_o_o_t_i_n_g _N_e_t_B_S_D	_a_n_d _M_a_c_O_S _X _o_r
	 _D_a_r_w_i_n

	 For older systems, you're in for more hassle.	Booting
	 an Open Firmware 1.0.5, 2.0.x,	or 2.4 system into MacOS
	 9 or earlier will erase some or all of	your Open
	 Firmware settings.  Try it and	see which Open Firmware
	 variables survive.

	 If only `real-base' is	lost, you can compile a	kernel
	 that does not require changing	the `real-base'.  Just
	 build a kernel	that is	less than 4 MB uncompressed.
	 This is easy if you remove all	of the USB devices from
	 the config file.  Once	you've got a smaller kernel, just
	 follow	the procedure in the section above on _B_o_o_t_i_n_g
	 _N_e_t_B_S_D	_a_n_d _M_a_c_O_S _X _o_r _D_a_r_w_i_n

	 If everything is lost when you	boot into MacOS	9 or ear-
	 lier, you will	need to	make a custom BootVars configura-
	 tion that you run before trying to boot NetBSD/macppc
	 since System Disk does	not preserve enough information
	 when it saves a configuration.

	 1.   If your system supports System Disk, run it and
	      click ``Save'' to	install	the NVRAMRC patches.

	 2.   Run BootVars, click the ``All Variables''	button.

	 3.   Fill in `real-base', `boot-device', `boot-file',
	      `input-device', and `output-device'.

	 4.   From the ``File''	menu, pick ``Save''.  When you
	      run this file, it	will load BootVars with	all your
	      settings.	 To boot NetBSD	click the
	      ``Write&reboot'' button.

	 5.   Now your system will always boot NetBSD.	To boot
	      MacOS, use the shutdown(8) command to halt the sys-
	      tem at the Open Firmware prompt and use the Open
	      Firmware ``bye'' or ``mac-boot'' command to boot
	      MacOS.

     ++oo	 _O_t_h_e_r _b_o_o_t _t_e_c_h_n_i_q_u_e_s
	 See the FAQ for some vague information	on how to use the
	 Linux yyaabboooott system to	boot NetBSD.
	       hhttttpp::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//mmaaccppppcc//ffaaqq..hhttmmll##yyaabboooott

   PPoosstt	iinnssttaallllaattiioonn sstteeppss
     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.  The most important steps are
     described below.

     1.	  Before all else, read	postinstall(8).

     2.	  Configuring _/_e_t_c_/_r_c_._c_o_n_f

	  If you or the	installation software haven't done any
	  configuration	of _/_e_t_c_/_r_c_._c_o_n_f	(ssyyssiinnsstt normally 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 _/_b_i_n_/_s_h prompt.  If you are
	  asked	for a terminal type, respond with vvtt110000	(or what-
	  ever is appropriate for your terminal	type) and press
	  RETURN.  You may need	to type	one of the following com-
	  mands	to get your delete key to work properly, depend-
	  ing on your keyboard:
		# ssttttyy eerraassee ''^^hh''
		# ssttttyy eerraassee ''^^??''
	  At this point, you need to configure at least	one file
	  in the _/_e_t_c directory.  You will need	to mount your
	  root file system read/write with:
		# //ssbbiinn//mmoouunntt --uu --ww //
	  Change to the	_/_e_t_c directory and take	a look at the
	  _/_e_t_c_/_r_c_._c_o_n_f 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 pro-
	  ceed.	 Default values	for the	various	programs can be
	  found	in _/_e_t_c_/_d_e_f_a_u_l_t_s_/_r_c_._c_o_n_f, where	some in-line doc-
	  umentation may be found.  More complete documentation
	  can be found in rc.conf(5).

	  When you have	finished editing _/_e_t_c_/_r_c_._c_o_n_f, type eexxiitt
	  at the prompt	to leave the single-user shell and con-
	  tinue	with the multi-user boot.

	  Other	values that may	need to	be set in _/_e_t_c_/_r_c_._c_o_n_f
	  for a	networked environment are _h_o_s_t_n_a_m_e and possibly
	  _d_e_f_a_u_l_t_r_o_u_t_e.	 You may also need to add an _i_f_c_o_n_f_i_g___i_n_t
	  for your <int> network interface, where your on-board
	  interfaces may be one	of mc0,	bm0, tlp0 or gem0.  For
	  example:

		ifconfig_mc0="inet 192.0.2.123 netmask
		255.255.255.0"

	  or, if you have _m_y_n_a_m_e_._m_y_._d_o_m	in _/_e_t_c_/_h_o_s_t_s:

		ifconfig_mc0="inet myname.my.dom netmask
		255.255.255.0"

	  To enable proper hostname resolution,	you will also
	  want to add an _/_e_t_c_/_r_e_s_o_l_v_._c_o_n_f file or (if you are
	  feeling a little more	adventurous) run named(8).  See
	  resolv.conf(5) or named(8) for more information.

	  Instead of manually configuring networking, DHCP can be
	  used by setting dhcpcd=YES in	_/_e_t_c_/_r_c_._c_o_n_f.

     3.	  Logging in

	  After	reboot,	you can	log in as root at the login
	  prompt.  If you didn't set a password	in ssyyssiinnsstt, there
	  is no	initial	password.  You should create an	account
	  for yourself (see below) and protect it and the
	  ``root'' account with	good passwords.	 By default, root
	  login	from the network is disabled (even via ssh(1)).
	  One way to become root over the network is to	log in as
	  a different user that	belongs	to group ``wheel'' (see
	  group(5)) and	use su(1) to become root.

     4.	  Adding accounts

	  Use the useradd(8) command to	add accounts to	your sys-
	  tem.	Do not edit _/_e_t_c_/_p_a_s_s_w_d	directly! See vipw(8) and
	  pwd_mkdb(8) if you want to edit the password database.

     5.	  The X	Window System

	  If you installed the X Window	System,	you may	want to
	  read the chapter about X in the _N_e_t_B_S_D _G_u_i_d_e_:
		hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ddooccss//gguuiiddee//eenn//cchhaapp--xx..hhttmmll:

     6.	  Installing third-party packages

	  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,
	  pkgsrc.  pkgsrc automatically	handles	any changes nec-
	  essary to make the software run on NetBSD.  This
	  includes the retrieval and installation of any other
	  packages the software	may depend upon.

	  ++oo   More information on the package system is	available
	      at
		    hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ddooccss//ssooffttwwaarree//ppaacckkaaggeess..hhttmmll

	  ++oo   A	list of	available packages suitable for	browsing
	      is at
		    hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//ppkkggssrrcc//ccuurrrreenntt//ppkkggssrrcc//RREEAADDMMEE..hhttmmll

	  ++oo   Precompiled binaries can be found	at
		    hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//ppkkggssrrcc//ppaacckkaaggeess//NNeettBBSSDD//
	      usually in the _m_a_c_p_p_c_/_1_0_._1___S_T_A_B_L_E_/_A_l_l subdir.  If
	      you installed pkgin(1) in	the ssyyssiinnsstt post-instal-
	      lation configuration menu, you can use it	to auto-
	      matically	install	binary packages	over the network.
	      Assuming that _/_u_s_r_/_p_k_g_/_e_t_c_/_p_k_g_i_n_/_r_e_p_o_s_i_t_o_r_i_e_s_._c_o_n_f
	      is correctly configured, you can install them with
	      the following commands:

	      ##	ppkkggiinn iinnssttaallll ttccsshh bbaasshh	ppeerrll aappaacchhee xxffccee44 ffiirreeffooxx
	      ...

	      The above	command	will install the Tenex-csh and
	      Bourne Again shells, the Perl programming	language,
	      Apache web server, Xfce desktop environment and the
	      Firefox web browser as well as all the packages
	      they depend on.

	      If it was	not automatically installed, pkgin(1) can
	      be installed on a	fresh NetBSD system with
	      pkg_add(1):

	      eexxppoorrtt PPKKGG__PPAATTHH==hhttttppss::////ccddnn..nneettbbssdd..oorrgg//ppuubb//ppkkggssrrcc//ppaacckkaaggeess//NNeettBBSSDD//$$((uunnaammee	--pp))//$$((uunnaammee --rr | ccuutt --dd__ --ff11))//AAllll
	      ppkkgg__aadddd ppkkggiinn

	  ++oo   If you wish to use the pkgsrc(7) framework for com-
	      piling packages and did not install it from the
	      sysinst(8) post-installation configuration menu,
	      you can obtain it	by retrieving the file
		    hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//ppkkggssrrcc//ssttaabbllee//ppkkggssrrcc..ttaarr..ggzz.
	      It is typically extracted	into _/_u_s_r_/_p_k_g_s_r_c (though
	      other locations work fine) with the commands:

		    # ccdd //uussrr
		    # ttaarr --zzxxppff	ppkkggssrrcc..ttaarr..ggzz

	      After extracting,	see the	_d_o_c_/_p_k_g_s_r_c_._t_x_t file in
	      the extraction directory (e.g.,
	      _/_u_s_r_/_p_k_g_s_r_c_/_d_o_c_/_p_k_g_s_r_c_._t_x_t) for more information.

     7.	  Misc

	  ++oo   Edit _/_e_t_c_/_m_a_i_l_/_a_l_i_a_s_e_s to	forward	root mail to the
	      right place.  Don't forget to run	newaliases(1)
	      afterwards.

	  ++oo   Edit _/_e_t_c_/_r_c_._l_o_c_a_l to run	any local daemons you
	      use.

	  ++oo   Many of the _/_e_t_c files are documented in section 5
	      of the manual; so	just invoking

		    # mmaann 55 _f_i_l_e_n_a_m_e

	      is likely	to give	you more information on	these
	      files.

   UUppggrraaddiinngg aa pprreevviioouussllyy--iinnssttaalllleedd NNeettBBSSDD SSyysstteemm
     The easiest way to	upgrade	to NetBSD 10.1_STABLE is with
     binaries, and that	is the method documented here.

     To	do the upgrade,	you must boot the install kernel using
     one of the	methods	described above.  You must also	have at
     least the bbaassee and	kkeerrnn binary distribution sets available.
     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	addi-
     tional free space for files which weren't previously
     installed or to account for growth	of the sets between
     releases.

     Since upgrading involves replacing	the kernel, boot blocks,
     and most of the system binaries, it has the potential to
     cause data	loss.  You are strongly	advised	to _b_a_c_k	_u_p any
     important data on the NetBSD partition or on another operat-
     ing system's partition on your disk 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 is similar to an installation, but
     without the hard disk partitioning.

     Fetching the binary sets is done in the same manner as the
     installation procedure; refer to the installation part of
     the document for help.  File systems are checked before
     unpacking the sets.

     After a new kernel	has been copied	to your	hard disk, your
     machine is	a complete NetBSD 10.1_STABLE 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 _/_d_e_v.  If you've	changed	the contents of
     _/_d_e_v by hand, you will need to be careful about this, but if
     not, you can just cd into _/_d_e_v, and run the command:

	   # sshh	MMAAKKEEDDEEVV	aallll

     ssyyssiinnsstt will attempt to merge the settings	stored in your
     _/_e_t_c directory with the new version of NetBSD using the
     postinstall(8) utility.  However, postinstall(8) is only
     able to deal with changes that are	easily automated.  It is
     recommended that you use the etcupdate(8) tool to merge any
     remaining configuration changes.

   CCoommppaattiibbiilliittyy IIssssuueess	WWiitthh PPrreevviioouuss NNeettBBSSDD RReelleeaasseess
     Users upgrading from previous versions of NetBSD may wish to
     bear the following	problems and compatibility issues in mind
     when upgrading to NetBSD 10.1_STABLE.

     Note that ssyyssiinnsstt will automatically invoke

	   postinstall fix
     and thus all issues that are fixed	by ppoossttiinnssttaallll by default
     will be handled.

     In	NetBSD 9 and earlier, filesystems listed in _/_e_t_c_/_f_s_t_a_b
     would be mounted before non-legacy	zzffss filesystems. Starting
     from NetBSD 10 this order has been	reversed.

     If	you have ever run a version of NetBSD -current between
     April 18, 2020 and	September 23, 2022 (the	version	numbers
     used in the affected time range are between 9.99.56 and
     9.99.106) your FFS	file systems might have	broken extended
     attributes	stored.

     You should	follow this _g_u_i_d_e_:
	   hhttttppss::////wwiikkii..nneettbbssdd..oorrgg//ffeeaattuurreess//UUFFSS22eeaa//
     before booting the	updated	system multi-user for the first
     time.

     _N_o_t_e _t_h_a_t _y_o_u _d_o _n_o_t _n_e_e_d _t_o _d_o _a_n_y_t_h_i_n_g _s_p_e_c_i_a_l _i_f _y_o_u
     _n_e_v_e_r _d_i_d _r_u_n _a_n_y _a_f_f_e_c_t_e_d	_k_e_r_n_e_l_,	especially if you have
     never run NetBSD -current.

     The display drivers used for modern GPUs and the whole sub-
     system supporting it (DRM/KMS) have been updated to a newer
     version.  Unfortunately not all issues with this have been
     resolved before the NetBSD	10.0 release. You can find a list
     of	issues in the _O_p_e_n _i_s_s_u_e_s _w_i_t_h _n_e_w _D_R_M_/_K_M_S_:
	   hhttttppss::////wwiikkii..nneettbbssdd..oorrgg//rreelleenngg//nneettbbssdd--1100//
     section of	the release engineering	wiki page.

     A number of things	have been removed from the NetBSD
     10.1_STABLE release.  See the ``Components	removed	from
     NetBSD'' section near the beginning of this document for a
     list.

   UUssiinngg oonnlliinnee	NNeettBBSSDD ddooccuummeennttaattiioonn
     Documentation is available	if you installed the manual dis-
     tribution set.  Traditionally, the	``man pages'' (documenta-
     tion) are denoted by `name(section)'.  Some examples of this
     are

	   ++oo   intro(1),
	   ++oo   man(1),
	   ++oo   apropos(1),
	   ++oo   passwd(1), and
	   ++oo   passwd(5).

     The section numbers group the topics into several cate-
     gories, but three are of primary interest:	user commands are
     in	section	1, file	formats	are in section 5, and administra-
     tive information is in section 8.

     The _m_a_n command is	used to	view the documentation on a
     topic, and	is started by entering mmaann [_s_e_c_t_i_o_n] _t_o_p_i_c.  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 num-
     bered section name	will be	displayed.  For	instance, after
     logging in, enter

	   # mmaann ppaasssswwdd

     to	read the documentation for passwd(1).  To view the docu-
     mentation for passwd(5), enter

	   # mmaann 55 ppaasssswwdd

     instead.

     If	you are	unsure of what man page	you are	looking	for,
     enter

	   # aapprrooppooss _s_u_b_j_e_c_t_-_w_o_r_d

     where _s_u_b_j_e_c_t_-_w_o_r_d	is your	topic of interest; a list of pos-
     sibly related man pages will be displayed.

   AAddmmiinniissttrriivviiaa
     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 _m_a_j_o_r_d_o_m_o_@_N_e_t_B_S_D_._o_r_g.  See
	   hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//mmaaiilliinngglliissttss//
     for details.

     There are various mailing lists set up to deal with comments
     and questions about this release.	Please send comments to:
     _n_e_t_b_s_d_-_c_o_m_m_e_n_t_s_@_N_e_t_B_S_D_._o_r_g.

     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.

     Bugs also can be submitted	and queried with the web inter-
     face at
	   hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ssuuppppoorrtt//sseenndd--pprr..hhttmmll

     There are also port-specific mailing lists, to discuss
     aspects of	each port of NetBSD.  Use majordomo to find their
     addresses,	or visit
	   hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//mmaaiilliinngglliissttss//

     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	NetBSD,	and have an idea as to
     how you could be useful, send us mail or subscribe	to:
     _n_e_t_b_s_d_-_u_s_e_r_s_@_N_e_t_B_S_D_._o_r_g.

     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 appro-
     priate list about it.  If you'd rather not	do that, mail the
     list saying you'll	send the data to those who want	it.

   TThhaannkkss ggoo ttoo
     ++oo	 The former members of UCB's Computer Systems Research
	 Group,	including (but not limited to):

	       Keith Bostic
	       Ralph Campbell
	       Mike Karels
	       Marshall	Kirk McKusick

	 for their work	on BSD systems,	support, and encourage-
	 ment.

     ++oo	 The Internet Systems Consortium, Inc. for hosting the
	 NetBSD	FTP, CVS, AnonCVS, mail, mail archive, GNATS,
	 SUP, Rsync and	WWW servers.

     ++oo	 The Internet Research Institute in Japan for hosting the
	 server	which runs the CVSweb interface	to the NetBSD
	 source	tree.

     ++oo	 The Columbia University Computer Science Department for
	 hosting the build cluster.

     ++oo	 The many organizations	that provide NetBSD mirror sites.

     ++oo	 Without CVS, this project would be impossible to manage,
	 so our	hats go	off to Brian Berliner, Jeff Polk, and the
	 various other people who've had a hand	in making CVS a
	 useful	tool.

     ++oo	 We list the individuals and organizations that	have made
	 donations or loans of hardware	and/or money, to support
	 NetBSD	development, and deserve credit	for it at
	       hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ddoonnaattiioonnss//
	 (If you're not	on that	list and should	be, tell us!  We
	 probably were not able	to get in touch	with you, to ver-
	 ify that you wanted to	be listed.)

     ++oo	 Finally, we thank all of the people who've put	sweat and
	 tears into developing NetBSD since its	inception in Jan-
	 uary, 1993.  (Obviously, there	are a lot more people who
	 deserve thanks	here.  If you're one of	them, and would
	 like to be mentioned, tell us!)

   LLeeggaall MMuummbboo--JJuummbboo
     All product names mentioned herein	are trademarks or regis-
     tered trademarks of their respective owners.

     The following notices are required	to satisfy the license
     terms of the software that	we have	mentioned in this docu-
     ment:

     NetBSD is a registered trademark of The NetBSD Foundation,
     Inc.
     This product includes software developed by the University
     of	California, Berkeley and its contributors.
     This product includes software developed by the NetBSD Foun-
     dation.
     This product includes software developed by The NetBSD Foun-
     dation, Inc. and its contributors.
     This product includes software developed for the NetBSD
     Project.  See https://www.NetBSD.org/ for information about
     NetBSD.
     This product includes cryptographic software written by Eric
     Young (eay@cryptsoft.com)
     This product includes cryptographic software written by Eric
     Young (eay@mincom.oz.au)
     This product includes software designed by	William	Allen
     Simpson.
     This product includes software developed at Ludd, University
     of	Luleoa.
     This product includes software developed at Ludd, University
     of	Luleoa, Sweden and its contributors.
     This product includes software developed at the Information
     Technology	Division, US Naval Research Laboratory.
     This product includes software developed by Aaron Brown and
     Harvard University.
     This product includes software developed by Adam Ciarcinski
     for the NetBSD project.
     This product includes software developed by Adam Glass.
     This product includes software developed by Adam Glass and
     Charles M.	 Hannum.
     This product includes software developed by Alex Zepeda.
     This product includes software developed by Alex Zepeda, and
     Colin Wood	for the	NetBSD Project.
     This product includes software developed by Allen Briggs.
     This product includes software developed by Amancio Hasty
     and Roger Hardiman
     This product includes software developed by Ben Gray.
     This product includes software developed by Berkeley Soft-
     ware Design, Inc.
     This product includes software developed by Bill Paul.
     This product includes software developed by Bodo Moeller.
     This product includes software developed by Boris Popov.
     This product includes software developed by Brini.
     This product includes software developed by Bruce M. Simp-
     son.
     This product includes software developed by Causality Lim-
     ited.
     This product includes software developed by Charles Hannum.
     This product includes software developed by Charles M. Han-
     num.
     This product includes software developed by Charles M. Han-
     num, by the University of Vermont and State Agricultural
     College and Garrett A.  Wollman, by William F. Jolitz, and
     by	the University of California, Berkeley,	Lawrence Berkeley
     Laboratory, and its contributors.
     This product includes software developed by Christian E.
     Hopps.
     This product includes software developed by Christian E.
     Hopps, Ezra Story,	Kari Mettinen, Markus Wild, Lutz Vieweg
     and Michael Teske.
     This product includes software developed by Christopher G.
     Demetriou.
     This product includes software developed by Christopher G.
     Demetriou for the NetBSD Project.
     This product includes software developed by Chuck Silvers.
     This product includes software developed by Cisco Systems,
     Inc.
     This product includes software developed by Colin Wood.
     This product includes software developed by Colin Wood for
     the NetBSD	Project.
     This product includes software developed by Computing Ser-
     vices at Carnegie Mellon University (http://www.cmu.edu/com-
     puting/).
     This product includes software developed by Daan Vreeken.
     This product includes software developed by Daishi	Kato
     This product includes software developed by Daniel	Widenfalk
     and Michael L. Hitch.
     This product includes software developed by Daniel	Widenfalk
     for the NetBSD Project.
     This product includes software developed by David Jones and
     Gordon Ross
     This product includes software developed by David Miller.
     This product includes software developed by Dean Huxley.
     This product includes software developed by Emmanuel Dreyfus
     This product includes software developed by Eric S. Hvozda.
     This product includes software developed by Eric S. Raymond
     This product includes software developed by Eric Young
     (eay@cryptsoft.com)
     This product includes software developed by Eric Young
     (eay@mincom.oz.au)
     This product includes software developed by Ezra Story.
     This product includes software developed by Ezra Story and
     by	Kari Mettinen.
     This product includes software developed by Ezra Story, by
     Kari Mettinen and by Bernd	Ernesti.
     This product includes software developed by Ezra Story, by
     Kari Mettinen, and	Michael	Teske.
     This product includes software developed by Ezra Story, by
     Kari Mettinen, Michael Teske and by Bernd Ernesti.
     This product includes software developed by Frank van der
     Linden for	the NetBSD Project.
     This product includes software developed by Gardner
     Buchanan.
     This product includes software developed by Garrett D'Amore.
     This product includes software developed by Gary Thomas.
     This product includes software developed by Gordon	Ross
     This product includes software developed by Harvard Univer-
     sity.
     This product includes software developed by Harvard Univer-
     sity and its contributors.
     This product includes software developed by Hellmuth
     Michaelis and Joerg Wunsch
     This product includes software developed by Henrik	Vester-
     gaard Draboel.
     This product includes software developed by Herb Peyerl.
     This product includes software developed by Hidetoshi
     Shimokawa.
     This product includes software developed by Hubert	Feyrer
     for the NetBSD Project.
     This product includes software developed by Ian W.	Dall.
     This product includes software developed by Intel Corpora-
     tion and its contributors.
     This product includes software developed by Internet Initia-
     tive Japan	Inc.
     This product includes software developed by Internet
     Research Institute, Inc.
     This product includes software developed by James R. Maynard
     III.
     This product includes software developed by Jared D.
     McNeill.
     This product includes software developed by Jason L. Wright
     This product includes software developed by Jason R. Thorpe
     for And Communications, http://www.and.com/
     This product includes software developed by Joachim Koenig-
     Baltes.
     This product includes software developed by Jochen	Pohl for
     The NetBSD	Project.
     This product includes software developed by Joerg Wunsch
     This product includes software developed by John Birrell.
     This product includes software developed by John P. Wit-
     tkoski.
     This product includes software developed by John Polstra.
     This product includes software developed by Jonathan R.
     Stone for the NetBSD Project.
     This product includes software developed by Jonathan Stone.
     This product includes software developed by Jonathan Stone
     and Jason R. Thorpe for the NetBSD	Project.
     This product includes software developed by Jonathan Stone
     for the NetBSD Project.
     This product includes software developed by Julian	High-
     field.
     This product includes software developed by K. Kobayashi
     This product includes software developed by K. Kobayashi and
     H.	Shimokawa
     This product includes software developed by Kazuhisa
     Shimizu.
     This product includes software developed by Kazuki	Sakamoto.
     This product includes software developed by Kenneth Stailey.
     This product includes software developed by Kiyoshi Ikehara.
     This product includes software developed by Klaus Burkert,by
     Bernd Ernesti, by Michael van Elst, and by	the University of
     California, Berkeley and its contributors.
     This product includes software developed by Kyma Systems.
     This product includes software developed by Leo Weppelman
     and Waldi Ravens.
     This product includes software developed by Lloyd Parkes.
     This product includes software developed by Lutz Vieweg.
     This product includes software developed by Marc Horowitz.
     This product includes software developed by Marcus	Comstedt.
     This product includes software developed by Mark Brinicombe.
     This product includes software developed by Mark Brinicombe
     for the NetBSD Project.
     This product includes software developed by Mark Tinguely
     and Jim Lowe
     This product includes software developed by Markus	Wild.
     This product includes software developed by Marshall M. Mid-
     den.
     This product includes software developed by Masanobu Saitoh.
     This product includes software developed by Masaru	Oki.
     This product includes software developed by Matt DeBergalis
     This product includes software developed by Matthew Fre-
     dette.
     This product includes software developed by Michael Smith.
     This product includes software developed by Microsoft
     This product includes software developed by Mika Kortelainen
     This product includes software developed by Mike Pritchard.
     This product includes software developed by Mike Pritchard
     and contributors.
     This product includes software developed by Minoura Makoto.
     This product includes software developed by MINOURA Makoto,
     Takuya Harakawa.
     This product includes software developed by Niels Provos.
     This product includes software developed by Niklas	Hal-
     lqvist.
     This product includes software developed by Niklas	Hal-
     lqvist, Brandon Creighton and Job de Haas.
     This product includes software developed by Paolo Abeni.
     This product includes software developed by Paul Kranenburg.
     This product includes software developed by Paul Mackerras.
     This product includes software developed by Paul Mackerras
     <paulus@samba.org>.
     This product includes software developed by Pedro Roque Mar-
     ques <pedro_m@yahoo.com>
     This product includes software developed by Per Fogelstrom.
     This product includes software developed by Peter Galbavy.
     This product includes software developed by Phase One, Inc.
     This product includes software developed by Philip	A. Nel-
     son.
     This product includes software developed by QUALCOMM Incor-
     porated.
     This product includes software developed by Ravikanth.
     This product includes software developed by RiscBSD.
     This product includes software developed by Roar Thronaes.
     This product includes software developed by Rodney	W.
     Grimes.
     This product includes software developed by Roger Hardiman
     This product includes software developed by Rolf Grossmann.
     This product includes software developed by Ross Harvey.
     This product includes software developed by Ross Harvey for
     the NetBSD	Project.
     This product includes software developed by Scott Bartram.
     This product includes software developed by Scott Stevens.
     This product includes software developed by Shingo	WATANABE.
     This product includes software developed by Softweyr LLC,
     the University of California, Berkeley, and its contribu-
     tors.
     This product includes software developed by Stephan Thesing.
     This product includes software developed by Steven	M.
     Bellovin
     This product includes software developed by Takashi Hamada.
     This product includes software developed by Takumi	Nakamura.
     This product includes software developed by Tatoku	Ogaito
     for the NetBSD Project.
     This product includes software developed by Tommi Komulainen
     <Tommi.Komulainen@iki.fi>.
     This product includes software developed by TooLs GmbH.
     This product includes software developed by Trimble Naviga-
     tion, Ltd.
     This product includes software developed by Waldi Ravens.
     This product includes software developed by WIDE Project and
     its contributors.
     This product includes software developed by Winning Strate-
     gies, Inc.
     This product includes software developed by Yen Yen Lim and
     North Dakota State	University
     This product includes software developed by Zembu Labs, Inc.
     This product includes software developed by the Alice Group.
     This product includes software developed by the Computer
     Systems Engineering Group at Lawrence Berkeley Laboratory.
     This product includes software developed by the Computer
     Systems Laboratory	at the University of Utah.
     This product includes software developed by the Harvard Uni-
     versity and its contributors.
     This product includes software developed by the Kungliga
     Tekniska Hoegskolan and its contributors.
     This product includes software developed by the Network
     Research Group at Lawrence	Berkeley Laboratory.
     This product includes software developed by the OpenSSL
     Project for use in	the OpenSSL Toolkit.
     (http://www.OpenSSL.org/)
     This product includes software developed by the PocketBSD
     project and its contributors.
     This product includes software developed by the RiscBSD ker-
     nel team
     This product includes software developed by the RiscBSD
     team.
     This product includes software developed by the SMCC Tech-
     nology Development	Group at Sun Microsystems, Inc.
     This product includes software developed by the University
     of	California, Lawrence Berkeley Laboratories.
     This product includes software developed by the University
     of	California, Lawrence Berkeley Laboratory.
     This product includes software developed by the University
     of	California, Lawrence Berkeley Laboratory and its contrib-
     utors.
     This product includes software developed by the University
     of	Vermont	and State Agricultural College and Garrett A.
     Wollman.
     This product includes software developed by the University
     of	Vermont	and State Agricultural College and Garrett A.
     Wollman, by William F.  Jolitz, and by the	University of
     California, Berkeley, Lawrence Berkeley Laboratory, and its
     contributors.
     This product includes software developed by the Urbana-Cham-
     paign Independent Media Center.
     This product includes software developed for the FreeBSD
     project
     This product includes software developed for the NetBSD
     Project by	Allegro	Networks, Inc.,	and Wasabi Systems, Inc.
     This product includes software developed for the NetBSD
     Project by	Bernd Ernesti.
     This product includes software developed for the NetBSD
     Project by	Christopher G. Demetriou.
     This product includes software developed for the NetBSD
     Project by	Eiji Kawauchi.
     This product includes software developed for the NetBSD
     Project by	Frank van der Linden
     This product includes software developed for the NetBSD
     Project by	Genetec	Corporation.
     This product includes software developed for the NetBSD
     Project by	Jason R. Thorpe.
     This product includes software developed for the NetBSD
     Project by	John M.	Vinopal.
     This product includes software developed for the NetBSD
     Project by	Jonathan Stone.
     This product includes software developed for the NetBSD
     Project by	Kyma Systems LLC.
     This product includes software developed for the NetBSD
     Project by	Matthias Drochner.
     This product includes software developed for the NetBSD
     Project by	Perry E. Metzger.
     This product includes software developed for the NetBSD
     Project by	Piermont Information Systems Inc.
     This product includes software developed for the NetBSD
     Project by	Shigeyuki Fukushima.
     This product includes software developed for the NetBSD
     Project by	SUNET, Swedish University Computer Network.
     This product includes software developed for the NetBSD
     Project by	Wasabi Systems,	Inc.
     This product includes software developed or owned by Caldera
     International, Inc.
     This product includes software developed under OpenBSD by
     Per Fogelstrom.
     This product includes software developed under OpenBSD by
     Per Fogelstrom Opsycon AB for RTMX	Inc, North Carolina, USA.
     This software was developed by Holger Veit	and Brian Moore
     for use with "386BSD" and similar operating systems.  "Simi-
     lar operating systems" includes mainly non-profit oriented
     systems for research and education, including but not
     restricted	to "NetBSD", "FreeBSD",	"Mach" (by CMU).
     The Institute of Electrical and Electronics Engineers and
     The Open Group, have given	us permission to reprint portions
     of	their documentation.

     In	the following statement, the phrase ``this text'' refers
     to	portions of the	system documentation.

     Portions of this text are reprinted and reproduced	in
     electronic	form in	NetBSD,	from IEEE Std 1003.1, 2004
     Edition, Standard for Information Technology -- Portable
     Operating System Interface	(POSIX), The Open Group	Base
     Specifications Issue 6, Copyright (C) 2001-2004 by	the
     Institute of Electrical and Electronics Engineers,	Inc and
     The Open Group.  In the event of any discrepancy between
     these versions and	the original IEEE and The Open Group
     Standard, the original IEEE and The Open Group Standard is
     the referee document.

     The original Standard can be obtained online at
     http://www.opengroup.org/unix/online.html.

     This notice shall appear on any product containing	this
     material.

     In	the following statement, "This software" refers	to the
     parallel port driver:
	   This	software is a component	of "386BSD" developed by
	   William F. Jolitz, TeleMuse.

     Some files	have the following copyright:
	   Mach	Operating System
	   Copyright (c) 1991,1990,1989	Carnegie Mellon	Univer-
	   sity
	   All Rights Reserved.

	   Permission to use, copy, modify and distribute this
	   software and	its documentation is hereby granted, pro-
	   vided that both the copyright notice	and this permis-
	   sion	notice appear in all copies of the software, de-
	   rivative works or modified versions,	and any	portions
	   thereof, and	that both notices appear in supporting
	   documentation.

	   CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN
	   ITS CONDITION.  CARNEGIE MELLON DISCLAIMS ANY LIABIL-
	   ITY OF ANY KIND FOR ANY DAMAGES WHATSOEVER RESULTING
	   FROM	THE USE	OF THIS	SOFTWARE.

	   Carnegie Mellon requests users of this software to
	   return to
	   Software Distribution Coordinator  or  Software.Dis-
	   tribution@CS.CMU.EDU
	   School of Computer Science
	   Carnegie Mellon University
	   Pittsburgh PA 15213-3890

	   any improvements or extensions that they make and
	   grant Carnegie the rights to	redistribute these
	   changes.

     Some files	have the following copyright:
	   Copyright (c) 1994, 1995 Carnegie-Mellon University.
	   All rights reserved.

	   Author: Chris G. Demetriou

	   Permission to use, copy, modify and distribute this
	   software and	its documentation is hereby granted, pro-
	   vided that both the copyright notice	and this permis-
	   sion	notice appear in all copies of the software, de-
	   rivative works or modified versions,	and any	portions
	   thereof, and	that both notices appear in supporting
	   documentation.
	   CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN
	   ITS "AS IS" CONDITION.  CARNEGIE MELLON DISCLAIMS ANY
	   LIABILITY OF	ANY KIND FOR ANY DAMAGES WHATSOEVER
	   RESULTING FROM THE USE OF THIS SOFTWARE.

	   Carnegie Mellon requests users of this software to
	   return to
	   Software Distribution Coordinator  or  Software.Dis-
	   tribution@CS.CMU.EDU
	   School of Computer Science
	   Carnegie Mellon University
	   Pittsburgh PA 15213-3890

	   any improvements or extensions that they make and
	   grant Carnegie the rights to	redistribute these
	   changes.

     Some files	have the following copyright:
	   Copyright 1996 The Board of Trustees	of The Leland
	   Stanford Junior University. All Rights Reserved.

	   Permission to use, copy, modify, and	distribute this
	   software and	its documentation for any purpose and
	   without fee is hereby granted, provided that	the above
	   copyright notice appear in all copies.  Stanford Uni-
	   versity makes no representations about the suitability
	   of this software for	any purpose.  It is provided "as
	   is" without express or implied warranty.

   TThhee EEnndd
NetBSD/macppc 10.1_STABLE	     Epoch	     NetBSD/macppc 10.1_STABLE
