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/mac68k.

CCOONNTTEENNTTSS
     About this	Document
     What is NetBSD?
     Changes Between The NetBSD	8 and 9	Releases
	Installation and Partitioning Changes
     Features to be removed in a later release
     The NetBSD	Foundation
     Sources of	NetBSD
     NetBSD 9.3	Release	Contents
	NetBSD/mac68k subdirectory structure
	Binary distribution sets
     NetBSD/mac68k System Requirements and Supported Devices
	Supported models
	Supported devices
	Unsupported models
	Known hardware issues with this	release
     Getting the NetBSD	System on to Useful Media
     Preparing your System for NetBSD installation
     Installing	the NetBSD System (Sysinst Method)
	Running	the sysinst installation program
	   Introduction
	   Possible hardware-specific issues
	   General
	   Quick install
	   Booting NetBSD
	   Preparing your hard disk
	   Getting the distribution sets
	   Installation	from CD-ROM
	   Installation	using FTP
	   Installation	using NFS
	   Installation	from Mac OS file systems
	   Installation	from an	unmounted file system
	   Installation	from a local directory
	   Extracting the distribution sets
	   Configure additional	items
	   Finalizing your installation
     Installing	the NetBSD System (Traditional Method)
	Preparing the file system(s)
	Installing the files
	Installation of	base files
	Booting	the system
     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
     Contributions

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 9.3	on the _m_a_c_6_8_k 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.

   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 UNIX-like operating	system derived from the	Univer-
     sity of California, 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 9.3 release contains complete binary
     releases for most of these	system architectures, with pre-
     liminary support for the others included in source	form.
     Please see	the NetBSD _w_e_b_s_i_t_e_: hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg// for
     information on them.

     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 88	aanndd 99 RReelleeaasseess
     The NetBSD	9.3 release provides many significant changes,
     including support for many	new devices, hundreds of bug
     fixes, new	and updated kernel subsystems, and numerous user-
     land enhancements.	 The result of these improvements is a
     stable operating system fit for production	use that rivals
     most commercially available systems.

     It	is impossible to completely summarize the massive devel-
     opment that went into the NetBSD 9.3 release.  The	complete
     list of changes can be found in the following files:
     _C_H_A_N_G_E_S_:
	   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//NNeettBBSSDD--99..33//CCHHAANNGGEESS
     _C_H_A_N_G_E_S_-_9_._1_:
	   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//NNeettBBSSDD--99..33//CCHHAANNGGEESS--99..11
     _C_H_A_N_G_E_S_-_9_._2_:
	   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//NNeettBBSSDD--99..33//CCHHAANNGGEESS--99..22
     _C_H_A_N_G_E_S_-_9_._3_:
	   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//NNeettBBSSDD--99..33//CCHHAANNGGEESS--99..33
     files in the top level directory of the NetBSD 9.3	release
     tree.

     _I_n_s_t_a_l_l_a_t_i_o_n _a_n_d _P_a_r_t_i_t_i_o_n_i_n_g _C_h_a_n_g_e_s

     The sysinst installation program has been reworked	for this
     release.

     It	now supports arbitrary big disks and offers GPT	parti-
     tions as alternative to MBR/fdisk partitions on a lot archi-
     tectures.

     Unfortunately it has not been tested on all hardware sup-
     ported by NetBSD.	If you have problems partitioning the
     target disk or installing the system, please report bugs
     with as much details as possible.	See the	Administrivia
     section below on how to report bugs or contact other users
     and ask for support.

   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.

   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 99..33 RReelleeaassee CCoonntteennttss
     The root directory	of the NetBSD 9.3 release is organized as
     follows:

     _._._._/_N_e_t_B_S_D_-_9_._3_/

     CHANGES	   Changes between the 8.0 and 9.0 releases.

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

     CHANGES-9.1   Changes between the 9.0 and the 9.1 release.

     CHANGES-9.2   Changes between the 9.1 and the 9.2 release.

     CHANGES-9.3   Changes between the 9.2 and the 9.3 release.

     CHANGES.prev  Changes in previous NetBSD releases.

     LAST_MINUTE   Last	minute changes and notes about the
		   release.

     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 9.3	has a binary distribution.

     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	9.3
	       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 9.3
	       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_6_8_k _s_u_b_d_i_r_e_c_t_o_r_y	_s_t_r_u_c_t_u_r_e

     The mac68k-specific portion of the	NetBSD 9.3 release is
     found in the _m_a_c_6_8_k subdirectory of the distribution:
     _._._._/_N_e_t_B_S_D_-_9_._3_/_m_a_c_6_8_k_/.  It contains the following	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 kernel	containing code
				       for everything supported
				       in this release using the
				       standard	SCSI driver.
			    _n_e_t_b_s_d_-_G_E_N_E_R_I_C_S_B_C_._g_z
				       A kernel	containing code
				       for everything supported
				       in this release using the
				       SBC variant of the SCSI
				       driver.
		   _s_e_t_s_/    mac68k binary distribution sets; see
			    below.
     _i_n_s_t_a_l_l_a_t_i_o_n_/
		   _i_n_s_t_k_e_r_n_e_l_/
			      mac68k boot and installation ker-
			      nels; see	installation section
			      (Sysinst Method),	below.
		   _m_i_s_c_/      Miscellaneous mac68k installation
			      utilities; see the Traditional
			      method installation section 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	mac68k binary distribution sets	contain	the bina-
     ries which	comprise the NetBSD 9.3	release	for mac68k.  The
     binary distribution sets can be found in the
     _m_a_c_6_8_k_/_b_i_n_a_r_y_/_s_e_t_s	subdirectory of	the NetBSD 9.3 distribu-
     tion tree,	and are	as follows:

     bbaassee     The NetBSD 9.3 mac68k bbaassee binary	distribution.
	      You _m_u_s_t install this distribution set.  It con-
	      tains the	base NetBSD utilities that are necessary
	      for the system to	run and	be minimally functional.

     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 develope-
	      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/mac68k	9.3 GENERIC ker-
	      nel, named _/_n_e_t_b_s_d.  You _m_u_s_t install either this
	      distribution set or kern-GENERICSBC.

     kkeerrnn--GGEENNEERRIICCSSBBCC
	      This set contains	a NetBSD/mac68k	9.3 GENERICSBC
	      kernel, named _/_n_e_t_b_s_d.  You _m_u_s_t install either
	      this distribution	set or kern-GENERIC.

     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
	      recover 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 XFree86 4.5.0.  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 developement.
	      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 Xmac68k _m_o_n_o_c_h_r_o_m_e
	      server with man pages.

     The mac68k	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.

     Kernels suitable for booting from an AppleShare server may
     be	found in the _m_a_c_6_8_k_/_b_i_n_a_r_y_/_k_e_r_n_e_l_s subdirectory	of the
     NetBSD 9.3	distribution tree.  These kernels are generally
     named something like _n_e_t_b_s_d_-_G_E_N_E_R_I_C_._g_z and	can be booted as-
     is	by the NetBSD/mac68k Booter utility, if	desired.  Please
     note that these kernels are simply	gzipped	and are	not in
     tar archives.

     The Mac OS	based utilities	necessary for installing and run-
     ning NetBSD can be	found in the _m_a_c_6_8_k_/_i_n_s_t_a_l_l_a_t_i_o_n_/_m_i_s_c
     subdirectory of the NetBSD	9.3 distribution tree.	The
     important files in	this directory are as follows:

     _B_o_o_t_e_r_._s_e_a_._h_q_x	The NetBSD/mac68k Booter utility.  This
			program	is used	to boot	the NetBSD kernel
			from within Mac	OS.
			_1_4_1 _K_B _a_r_c_h_i_v_e_d

     _I_n_s_t_a_l_l_e_r_._s_e_a_._h_q_x	The NetBSD/mac68k Installer utility.
			This program is	used to	install	the dis-
			tribution sets onto your NetBSD	parti-
			tion(s).  This utility is used only in a
			Traditional method installation; it is
			not used or required for an installation
			using the ssyyssiinnsstt method.
			_1_4_7 _K_B _a_r_c_h_i_v_e_d

     _M_k_f_s_._s_e_a_._h_q_x	The Mkfs utility.  This	program	is used
			to format your chosen partitions so that
			they can be used with NetBSD.  This util-
			ity is used only in a Traditional method
			installation; it is not	used or	required
			for an installation using the ssyyssiinnsstt
			method.
			_7_6 _K_B _a_r_c_h_i_v_e_d

     These files are all BinHexed, self-extracting archives.  If
     you need them, the	sources	for these utilities are	in the
     _s_r_c subdirectory.

     _N_o_t_e_:  Each directory in the mac68k 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c6688kk 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
     NetBSD/mac68k 9.3 runs on several of the older Macintosh
     computers.	 About 4 MB of RAM is sufficient to boot a
     stripped-down custom kernel, and a	subset of the system can
     be	squeezed onto a	40 MB hard disk	with considerable cre-
     ativity and persistence. However, 140 MB of disk should be
     considered	a practical minimum, and to do anything	more
     interesting than booting at least 8 MB of RAM and more disk
     space is recommended.

     Please note that to install NetBSD/mac68k 9.3 using the
     ssyyssiinnsstt method, your system must have a minimum of	6 MB of
     RAM and 60	MB of available	disk space (i.e. not part of an
     in-use HFS	partition).

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

	   ++oo   Mac II, IIx, IIcx, SE/30, IIci, IIsi, IIvx, IIvi
	   ++oo   Performa	400/405/410/430, Performa 450, Performa
	       460/466/467
	   ++oo   Performa	520, Performa 550/560, Performa	600/600CD
	   ++oo   LC II, LC III, LC III+, LC 520, LC 550
	   ++oo   MacTV
	   ++oo   Classic II, Color Classic
	   ++oo   Centris 650
	   ++oo   Quadra 610, Quadra 630, Quadra 650, Quadra 700,
	       Quadra 800
	   ++oo   Quadra/Centris 660AV, Quadra 840AV
	   ++oo   PowerBook 140, PowerBook	145/145B, PowerBook 170
	   ++oo   PowerBook 160, PowerBook	165, PowerBook 180
	   ++oo   PowerBook 165c, PowerBook 180c, PowerBook 550c

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

	   ++oo   Onboard SCSI bus	and most SCSI tapes, hard drives,
	       and CD-ROMs
	   ++oo   Internal	sound -- enough	to beep	on some	machines,
	       anyway
	   ++oo   Most basic NuBus	video cards (there have	been some
	       problems	with some 24-bit color cards and with
	       most QuickDraw accelerators)
	   ++oo   Both internal serial ports
	   ++oo   ADB keyboards and mice (both Apple and a	number of
	       third party multi-button	mice and trackballs are
	       supported)
	   ++oo   Ethernet	cards based on the National Semiconductor
	       8390 and	the SONIC (DP83932) chips (Asante, Apple,
	       and a few others	-- problems still with Ethernet
	       and many	NuBus video cards)
	   ++oo   Ethernet	cards based on the SMC 91c92 and 91c100
	       (FEAST) chips.  This includes the AsanteFAST
	       10/100 cards
	   ++oo   Onboard Ethernet	based on the SONIC chip	for
	       Quadra-series Macs
	   ++oo   Onboard Ethernet	based on the MACE (Am79C940) chip
	       for the Quadra AV-series	Macs
	   ++oo   Ethernet	port on	Asante NetDock and Newer Ether
	       MicroDock, for PowerBook	Duo series
	   ++oo   Comm-slot Ethernet should be working for	most
	       machines/cards

     If	your 68030 system is not listed	above, it may be because
     of	a problem with accessing onboard video,	and it may still
     work with a serial	console.  Some of the known ones in this
     category:
	   ++oo   Mac Classic series
	   ++oo   PowerBook Duo series

     If	your 68LC040 system is not listed above, it is due to a
     problem with floating point emulation (FPE) for this type of
     processor.	Machines in this category include:
	   ++oo   Newer LC-series machines	(47x, 57x)
	   ++oo   Newer Performa-series machines (47x, 57x, 58x,
	       63x, 640)
	   ++oo   Some PowerBook 500-series Macs

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

	   ++oo   Macintosh IIfx

	       This machine has	unusual	custom chips for the ADB
	       and serial interfaces which make	support	for it
	       difficult. Work is in progress on this, though.

	   ++oo   Quadra 900/950

	       These machines have I/O processor chips for their
	       ADB interfaces similar to those used in the IIfx
	       and thus	face similar support problems. Note that
	       you can use a serial console on these systems.

	   ++oo   PowerPC-based Macs

	       This is a separate effort from the mac68k port.
	       PowerMacs use hardware that is quite different
	       from that of the	mac68k port.  See the
	       NetBSD/macppc port webpage at
		     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//
	       for more	information.

     _K_n_o_w_n _h_a_r_d_w_a_r_e _i_s_s_u_e_s _w_i_t_h	_t_h_i_s _r_e_l_e_a_s_e

	   ++oo   Real Time Clock

	       Due to oddities of the Macintosh	hardware inter-
	       rupt priority scheme, NetBSD/mac68k keeps very
	       poor time. Under	a high interrupt load (e.g.  SCSI
	       or serial port activity), a machine can lose sev-
	       eral minutes per	hour. A	consequence of this prob-
	       lem is that attempting to run nnttppdd is generally
	       rather pointless.

	   ++oo   SCSI difficulties

	       The NetBSD/mac68k SCSI drivers are not quite as
	       robust as their Mac OS counterparts. Symptoms of
	       these problems are that some SCSI disks will not
	       work under NetBSD that work fine	under Mac OS.
	       Other problems include occasional file system cor-
	       ruption with some types of drives and the general
	       unreliability of	removable SCSI media.  Keep in
	       mind that there are no clear patterns with these
	       problems, and they do not appear	to affect the
	       majority	of users.

   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
     There are currently two installation methods available for
     initial installation of NetBSD on Apple Macintosh
     68000-based systems. Neither supports all installation media
     types at this time, so the	one you	select must be compatible
     with the media you	have available on your system.

     ++oo	 The ssyyssiinnsstt method of installation uses an Installation
	 Kernel	which is a minimal NetBSD system with a	memory
	 resident set of utilities that	are capable of partition-
	 ing the disk, initializing the	file systems, and loading
	 them from the archive files.  Since the installation
	 kernel	does not currently support access to Mac OS HFS
	 file systems this method requires that	the Binary Dis-
	 tribution Sets	be accessible from CD-ROM, remote NFS
	 partition, or via FTP access.

     ++oo	 The Traditional method	of installation	uses Mac OS
	 hosted	utilities to partition your disk, initialize the
	 partitions for	use by NetBSD, and load	the file systems
	 from archive files stored on the Mac OS HFS file system.
	 This method requires that the Binary Distribution Sets
	 reside	on a local Macintosh hard drive, a CD-ROM, or an
	 AppleShare volume.

     The Traditional method of installation is currently sup-
     ported from the local Macintosh hard drive, from a	CD-ROM,
     or	from an	AppleShare volume (however, you	may upgrade a
     system from within	NetBSD;	see the
     _U_p_g_r_a_d_i_n_g _a _p_r_e_v_i_o_u_s_l_y_-_i_n_s_t_a_l_l_e_d _N_e_t_B_S_D _S_y_s_t_e_m section for
     more details).  If	you are	installing from	a local	hard
     drive, this means that you'll need	at least enough	room for
     the largest file that you will have to install.

     If	the install is being done from an AppleShare-mounted vol-
     ume, the NetBSD/mac68k Installer must be in the same folder
     as	the binary distribution	sets.

     Each distribution file is in _r_a_w archive format.

     ++oo	 Distribution files must be downloaded in binary mode.
	 Common	web browsers may not be	suitable for this task;
	 FTP clients such as Fetch and Anarchie	work fine, but be
	 sure to specify a binary file transfer.

     ++oo	 The files should not be unpacked.  If you have	the
	 Internet Config extension installed, you can disable
	 this in the ``Helpers'' dialog	by removing the	entry
	 associated with ``.tgz'' files.  Other	FTP clients may
	 require separate changes; consult your	package's docu-
	 mentation.

     ++oo	 If you	are installing from a CD-ROM, the distribution
	 sets are already in the proper	format.	No special han-
	 dling is required.

     You will also need	to collect the Mac OS installation tools
     from the _m_a_c_6_8_k_/_i_n_s_t_a_l_l_a_t_i_o_n_/_m_i_s_c subdirectory of the
     NetBSD 9.3	distribution: Mkfs, NetBSD/mac68k Installer, and
     NetBSD/mac68k Booter. These three are in BinHexed,	self-
     extracting	archives as Mkfs.sea.hqx, Installer.sea.hqx, and
     Booter.sea.hqx, respectively. Extract them	as you would any
     other Macintosh application.

     _N_o_t_e_:  The	Booter is the only Mac OS application needed if
	    the	ssyyssiinnsstt	method of installation is used.	 The Tra-
	    ditional method of installation is deprecated and
	    will be removed in a future	release, and the Mkfs and
	    Installer tools will be retired.

   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
     No	matter which installation method you use, there	is some
     planning and preparation that is required beforehand.  First
     and foremost, before beginning the	installation process,
     make sure you have	a reliable backup of any data on your
     hard disk that you	wish to	keep.  _M_i_s_t_a_k_e_s	_i_n _p_a_r_t_i_t_i_o_n_i_n_g
     _y_o_u_r _h_a_r_d _d_i_s_k _m_a_y	_l_e_a_d _t_o	_d_a_t_a _l_o_s_s_.

     NetBSD/mac68k uses	the same disk mapping scheme as	Mac OS:
     the Apple Disk Partition Map.  This permits both systems to
     reside on the same	disk, but introduces some installation
     problems unique to	the Macintosh. There are very few, if
     any, reliable ways	to reduce the size of an existing Mac OS
     disk partition, so	partitioning a disk that currently con-
     tains Mac OS will almost always require a backup and reload
     step under	Mac OS.

     If	you are	using the ssyyssiinnsstt method of installation you will
     be	able to	do most, if not	all, of	your disk partitioning
     during the	install	process.  Partitioning the disk	with
     ssyyssiinnsstt will destroy any partition	that is	resized, deleted,
     converted,	or designated for use by NetBSD.  All space not
     planned to	be used	for Mac	OS HFS partitions may be used by
     NetBSD and	can be sub-divided by the ssyyssiinnsstt process.  This
     space may be defined within one or	more existing disk parti-
     tions of any type,	including HFS partitions that are no
     longer needed for Mac OS. However it is best if this space
     is	physically contiguous on the disk as ssyyssiinnsstt is	not capa-
     ble of merging non-contiguous disk	partitions.  If	you are
     using the ssyyssiinnsstt method and have sufficient disk space in
     one or more disk partitions you should skip forward to the
     section labeled
     _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 _(_S_y_s_i_n_s_t _M_e_t_h_o_d_) in this docu-
     ment.

     If	you are	using the Traditional method of	installation you
     must use a	disk partitioning utility to designate the dif-
     ferent partitions you will	want in	your final NetBSD config-
     uration.  It is not necessary to create NetBSD (or	AU/X)
     type partitions at	this stage; the	Mkfs utility can convert
     a partition of any	type to	one usable for NetBSD.

     If	disk partitioning is required because you've selected the
     Traditional method	of installation, or because disk space
     needs to be freed up for use for the ssyyssiinnsstt method of
     installation, follow the directions in the	remainder of this
     section.

     Find your favorite	disk partitioning utility. Any formatter
     capable of	partitioning a SCSI disk should	work. Some of the
     ones that have been tried and seem	to work	are:

	   ++oo   Apple HD	SC Setup
	   ++oo   Hard Disk ToolKit from FWB
	   ++oo   SCSI Director Lite
	   ++oo   Disk Manager Mac	from OnTrack
	   ++oo   Silverlining from LaCie
	   ++oo   APS Disk	Tools

     Apple's HD	SC Setup is probably the easiest to use	and the
     most commonly available. Instructions for patching	HD SC
     Setup so that it will recognize non-Apple drives is avail-
     able at:

	   hhttttpp::////wwwwww..eeuurroonneett..nnll//uusseerrss//eerrnnssttoouudd//ppaattcchh..hhttmmll

     First, you	need to	choose a drive on which	to install
     NetBSD.  Try to pick a drive with a low SCSI target number
     (or "SCSI ID"), especially	if you are likely to add or
     remove drives to your SCSI	chain in the future.

     _N_o_t_e_:  Be certain you have	a reliable backup of any data
	    that you may want to keep.	Repartitioning your hard
	    drive is an	excellent way to destroy important data.

     Second, decide how	you want to set	up your	partitions. At
     minimum, you need a partition to hold the NetBSD installa-
     tion (the root partition -- _/) and	a partition to serve as
     swap space. You may choose	to use more than one partition to
     hold the installation. This allows	you to separate	the more
     vital portions of the file	system (such as	the kernel and
     the _/_e_t_c directory) from the more volatile	parts of the file
     system.  Typical setups place the _/_u_s_r directory on a sepa-
     rate partition from the root partition (_/).  Generally, _/
     can be fairly small while the _/_u_s_r	partition should be
     fairly large.  If you plan	to use this machine as a server,
     you may also want a separate _/_v_a_r partition.

     Once you have decided how to lay out your partitions, you
     need to calculate how much	space to allocate to each parti-
     tion. A minimal install of	NetBSD (i.e.  _b_a_s_e_._t_g_z,	_e_t_c_._t_g_z_,
     and either	_k_e_r_n_-_G_E_N_E_R_I_C_._t_g_z or _k_e_r_n_-_G_E_N_E_R_I_C_S_B_C_._t_g_z) requires
     about 140MB.  A general rule of thumb for sizing the swap
     partition is to allocate twice as much swap space as you
     have real memory.	Having your swap + real	memory total at
     least 20 MB is also a good	idea.  Systems that will be heav-
     ily used or that are low on real memory should have more
     swap space	allocated. Systems that	will be	only lightly used
     or	have a very large amount of real memory	can get	away with
     less.

     Keep in mind that NetBSD currently	requires Mac OS	in order
     to	boot, so it is likely that you will want to keep at least
     a minimal install of Mac OS around	on an HFS partition for
     this purpose.  The	size of	this partition may vary	depending
     on	the size requirements for the version of Mac OS	you are
     using.  Of	course,	if you have Mac	OS on another hard drive
     or	can boot from a	floppy,	feel free to dedicate the entire
     drive to NetBSD.

     Next, use your favorite partitioning utility to make parti-
     tions of the necessary sizes. You can use any type	of parti-
     tion, but partitions of type Apple_Free might save	you some
     confusion in the future.

     You are now set to	install	NetBSD on your hard drive.

   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	((SSyyssiinnsstt MMeetthhoodd))
     _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.	  _P_o_s_s_i_b_l_e _h_a_r_d_w_a_r_e_-_s_p_e_c_i_f_i_c _i_s_s_u_e_s

	  ++oo   _S_C_S_I _d_r_i_v_e_r _p_r_o_b_l_e_m_s

	      The SCSI driver used in the kernel on many older
	      Macintosh	systems	is, by default,	the ncrscsi
	      driver.  It contains a recognized	but as yet
	      unfixed bug that affects some disk drive/controller
	      combinations, usually Quantum disks.  Under heavy
	      load these systems may hang or corrupt the file
	      system; or, you may experience frequent
	      _S_e_g_m_e_n_t_a_t_i_o_n _f_a_u_l_t and _I_l_l_e_g_a_l _i_n_s_t_r_u_c_t_i_o_n errors
	      that may or may not be consistently repeatable.
	      This latter condition is particularly prevalent on
	      systems with minimal RAM installed.

	      If either	of these problems occur	on your	system
	      you are advised to use the SBC variants of the Ker-
	      nel and Installation Kernel.  However, be	aware
	      that this	issue does not affect e.g. Centris or
	      Quadra systems.

	  ++oo   _T_h_e _6_8_L_C_0_4_0 _p_r_o_c_e_s_s_o_r

	      NetBSD has known but unresolved problems running on
	      the 68LC040 processor, the variant of the	68040
	      that does	not contain the	floating point unit
	      (FPU).  The kernel is thus forced	to emulate the
	      missing operations in software.  Unfortunately the
	      68LC040 processor	has a design problem that causes
	      the emulation to fail intermittently.  We	hope to
	      provide a	solution for this issue	in a future
	      NetBSD release.

	      Software emulation of floating point operations is
	      not a problem on the 68020 and 68030 processors.

     3.	  _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.

     4.	  _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	media.

	  ++oo   What you need.

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

	      --	  The Mac OS Booter application	and an Installa-
		  tion Kernel

	      --	  A Macintosh with a 68020 and MMU, 68030 or
		  68RC040 processor.  An FPU is	not required but
		  will be used if present (but see the note above
		  regarding the	68LC040).

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

	      --	  An optical drive.

	      --	  A hard drive with at least 500 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 NetBSD Boot Tools folder.

	      --	  Create a Folder on your Mac OS disk for the
		  NetBSD/mac68k	components.

	      --	  Copy the Booter application into the newly cre-
		  ated Folder.	Expand the file	if necessary to
		  create the Mac OS executable.

	      --	  Copy the Installation	Kernels	into the newly
		  created Folder.  It is not necessary to gguunnzziipp
		  compressed kernel files.

	      --	  Single-click on the Booter application icon
		  then select the "Get Info" from the File Menu
		  list.	 Increase the memory allocation	for the
		  Booter to as much as possible	for your system.
		  Having a large number	of fonts, extensions or
		  sounds installed on your system can cause mem-
		  ory exhaustion problems for the Booter if you
		  don't	do this.  Also,	the extra memory is
		  needed by the	Booter to expand compressed ker-
		  nels while booting.

	  ++oo   The Quick	Installation

	      --	  Double-click on the Booter application icon to
		  start	executing it.  From the	OOppttiioonnss	pull-down
		  menu,	select MMoonniittoorrss, then select CChhaannggee
		  MMoonniittoorr DDeepptthh	and make sure B&W is highlighted.
		  Close	the window using the CClloossee button.

	      --	  From the OOppttiioonnss pull-down menu select BBoooott
		  OOppttiioonnss.  This will bring up an option panel.
		  Set the AAuuttoo--sseett GGMMTT BBiiaass checkbox in	the lower
		  left and then	select the BBoooott	ffrroomm MMaacc OOSS
		  option at the	top of the window.  The	SSeett but-
		  ton on the right will	become active.	Use it to
		  locate and select the	Installation Kernel file
		  appropriate for your hardware.  This will be
		  either _n_e_t_b_s_d_-_I_N_S_T_A_L_L_._g_z or
		  _n_e_t_b_s_d_-_I_N_S_T_A_L_L_S_B_C_._g_z.	 Close the window using
		  the CClloossee button.

	      --	  From the OOppttiioonnss pull-down menu select the BBoooott
		  NNooww, or use the Apple-B (Command-B) key combi-
		  nation to start the NetBSD boot process.  Do
		  not move the mouse while the boot operation is
		  in progress as this may leave	the keyboard
		  locked to NetBSD.

		  The main menu	will be	displayed.  Insert the
		  first	boot floppy you	just created and boot the
		  computer.  After language selection, the main
		  menu will be displayed.

			  .***********************************************.
			  * NetBSD-9.3 Install System			  *
			  *						  *
			  *>a: Install NetBSD to hard disk		  *
			  * b: Upgrade NetBSD on a hard	disk		  *
			  * c: Re-install sets or install additional sets *
			  * d: Reboot the computer			  *
			  * e: Utility menu				  *
			  * 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 IInnssttaallll.

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

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

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

	  Prior	to attempting to boot NetBSD/mac68k verify that
	  all the following are	done:

	  ++oo   Enable 32-bit addressing in the Memory Control
	      Panel [1].

	  ++oo   Disable all forms	of virtual memory (the Memory
	      Control Panel, RAM Doubler, or other software-based
	      memory enhancement products).

	  ++oo   Place the	system in B&W Mode (1-bit color	or
	      grayscale) as shown in the Monitors Control Panel
	      or in the	Monitors options dialog	of the Booter.
	      You may choose to	have the Booter	do this	for you
	      automatically by selecting the appropriate check
	      box and radio button in the MMoonniittoorrss dialog on the
	      OOppttiioonnss menu.

	  It is	probably best to boot your machine with	all
	  extensions turned off	[1].  You can do this by booting
	  into Mac OS with the SHIFT key held down.  You may have
	  to restart your Macintosh for	changes	to take	effect
	  before proceeding.

	  [1]  If your version of the Memory control panel does
	       not have	a 32-bit addressing mode radio button,
	       this means that your system is already 32-bit
	       clean and is running in 32-bit addressing mode by
	       default.	 If the	Booter complains that your are
	       not in 32-bit mode, it may be necessary for you to
	       press the "Use Defaults"	button in the Memory con-
	       trol panel to restore 32-bit addressing.	 You
	       should probably reboot after doing so.  If you
	       have an older II-class system (including	the II,
	       IIx, IIcx, and SE/30), it is necessary to install
	       Connectix's MODE32 to work around ROM issues which
	       prevent you from	enabling 32-bit	addressing.
	       Please see the NetBSD/mac68k _F_A_Q_:
		     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c6688kk//ffaaqq//
	       for more	information.

	  Double-click on the NetBSD/mac68k Booter icon	to start
	  the application.  Select BBoooottiinngg from	the OOppttiioonnss menu.
	  Select the Kernel Location to	be from	Mac OS with the
	  filename corresponding to the	name of	the Installation
	  Kernel you are using.	 Typically this	will be	netbsd-
	  INSTALL.gz.

	  If you haven't already put your Macintosh into B&W
	  mode,	select the MMoonniittoorr OOppttiioonnss from	the OOppttiioonnss menu
	  and check the	box for	B&W mode.

	  Try booting NetBSD by	selecting BBoooott NNooww from	the
	  OOppttiioonnss menu.

	  If the system	does not come up, send mail to
	  _p_o_r_t_-_m_a_c_6_8_k_@_N_e_t_B_S_D_._o_r_g describing your software, your
	  hardware, and	as complete a description of the problem
	  as you can.  As an alternative, try using the	Tradi-
	  tional method	of installation	described in the next
	  section.

     6.	  _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.

     7.	  _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'.

     8.	  _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.

     9.	  _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.

     10.  _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.

     11.  _I_n_s_t_a_l_l_a_t_i_o_n _f_r_o_m _M_a_c	_O_S _f_i_l_e	_s_y_s_t_e_m_s

	  NetBSD/mac68k	does not currently have	in-kernel support
	  for Mac OS HFS/HFS+ or AppleShare filesystems.  ssyyssiinnsstt
	  therefore can	not access the file sets if they are on
	  these	filesystems.

     12.  _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.

     13.  _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.

     14.  _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.

     15.  _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).

     16.  _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
	  9.3.	You can	now reboot the machine and boot	NetBSD
	  from hard disk.

   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	((TTrraaddiittiioonnaall MMeetthhoodd))
     The Traditional method of installation can	be broken down
     into three	basic steps:

     ++oo	 Run Mkfs to build a file system or file systems.
     ++oo	 Run the Installer to load the files onto your file sys-
	 tems.
     ++oo	 Run the Booter	to boot	the system.

     _P_r_e_p_a_r_i_n_g _t_h_e _f_i_l_e	_s_y_s_t_e_m_(_s_)

     Double-click on the Mkfs application icon to start	it up. It
     will ask you for the SCSI-ID (SCSI	target number) of the
     drive that	you are	installing NetBSD on. Once this	is
     selected, it will present a list of the partitions	on that
     disk. You must first convert the partitions to a type which
     NetBSD can	understand. Select each	partition on which you
     wish to build a file system and click on the CChhaannggee button.
     If	you are	placing	the entire installation	on a single par-
     tition, select the	NNeettBBSSDD RRoooott&&UUssrr	radio button. If you are
     using multiple partitions,	select NNeettBBSSDD RRoooott for the root
     partition (_/) and NNeettBBSSDD UUssrr for all the other partitions.
     You should	select NNeettBBSSDD SSwwaapp for the swap	partition.

     When you have finished converting each partition, select
     each partition and	click on the FFoorrmmaatt button. You	will now
     be	asked for a bunch of parameters	for the	hard drive and
     the file system. Usually, you can just take the defaults. If
     you are installing	onto removable media (e.g. a Zip, Jaz, or
     Syquest), please see the FAQ. Note	that although this dialog
     only has the OOKK button, you are not committed, yet. Once you
     get the values you	want, press the	OOKK button. A dialog will
     be	presented at this point	with two options: FFoorrmmaatt and
     CCaanncceell.  If you choose CCaanncceell, nothing will be written to
     your drive. If you	choose FFoorrmmaatt, the program will	proceed
     to	make a file system.

     Mkfs is not a well-behaved	Macintosh application. It will
     not allow any other tasks to run while it does (cooperative
     multitasking at its best).	 When it's finished, the program
     will put up a dialog to ask if you	have scanned the output
     for any error messages. Usually there won't have been any
     errors, but do scan the output to make sure. Simply click on
     the II RReeaadd	IItt button and the program will quit.

     Repeat as necessary for any extra partitions that you wish
     to	make file systems on. Note that	you do _n_o_t need	a file
     system on your swap partition.

     When you are finished, click on the DDoonnee button and choose
     QQuuiitt from the FFiillee	menu to	exit Mkfs.

     _I_n_s_t_a_l_l_i_n_g	_t_h_e _f_i_l_e_s

     Before using the Installer, it is probably	a good idea to
     increase its memory allocation. Select the	Installer icon by
     clicking on it and	choose GGeett IInnffoo	from the File menu.
     Increase both the Minimum and Preferred sizes to as much as
     you can spare.

     Double-click on the Installer icon	to start it up.	The
     Installer will present the	same SCSI-ID menu that Mkfs did.
     Select the	same SCSI-ID (SCSI target number) that you did
     for Mkfs -	i.e., the one you are installing NetBSD	on.

     If	you are	installing onto	a single root partition	(_/), pro-
     ceed to the _I_n_s_t_a_l_l_a_t_i_o_n _o_f _b_a_s_e _f_i_l_e_s section, below.

     If	you have not created file systems for _/	(root),	_u_s_r, and
     any other file systems, go	back to	_P_r_e_p_a_r_i_n_g _t_h_e _f_i_l_e
     _s_y_s_t_e_m_(_s_) above.

     When you started the Installer, it	mounted	your root parti-
     tion (_/).	Just before it printed

	   Mounting partition 'A' as /

     it	printed	lines like:

	   sd1 at scsi ID 5

     This means	that the device	for SCSI target	5 ("SCSI ID 5")
     is	sd1.  The partitions are signified by a	trailing letter.
     For instance, sd1a	would be the root partition (_/)	of the
     second SCSI disk in the chain, and	sd0g would be the first
     Usr partition on the first	SCSI disk.

     You will need to know the proper device to	mount the remain-
     ing partition(s) by hand:

	   1.	Select BBuuiilldd DDeevviicceess from the FFiillee menu.

	   2.	Select MMiinnii SShheellll from the FFiillee	menu.

	   3.	You can	use the	ddiisskkllaabbeell command to get a list-
		ing of the available partitions	and their types
		and sizes.

	   4.	Create the directory mount point(s) with the com-
		mand:

		      #	mmkkddiirr ppaatthh

		E.g. for the _/_u_s_r partition type:

		      #	mmkkddiirr //uussrr

	   5.	Mount the file systems you wish	with the command:

		      #	mmoouunntt ddeevviiccee ppaatthh
		For example, if	you wish to mount a _/_u_s_r parti-
		tion from the first SCSI disk sd0, on _/_u_s_r, you
		would type:

		      #	mmoouunntt //ddeevv//ssdd00gg	//uussrr

	   6.	Type
		      #	ffssttaabb ffoorrccee
		to create a proper _/_e_t_c_/_f_s_t_a_b file.

	   7.	Type qquuiitt after	you have mounted all the file
		systems.

     _I_n_s_t_a_l_l_a_t_i_o_n _o_f _b_a_s_e _f_i_l_e_s

     Select the	IInnssttaallll	menu item from the FFiillee	menu and install
     _b_a_s_e_._t_g_z, _e_t_c_._t_g_z,	_e_i_t_h_e_r _k_e_r_n_-_G_E_N_E_R_I_C_._t_g_z	_o_r
     _k_e_r_n_-_G_E_N_E_R_I_C_S_B_C_._t_g_z, and any other	sets you wish to
     install   at this time (see the _N_e_t_B_S_D _9_._3	_R_e_l_e_a_s_e	_C_o_n_t_e_n_t_s
     for information about what's in each set).	The Installer
     will print	out the	filename of each file as it is installed,
     and will take quite some time to install everything (the
     base package alone	can take over two hours	on a slow hard
     drive).

     As	is the case with Mkfs, this is not a particularly well-
     behaved Macintosh application and the machine will	be com-
     pletely tied up while the installation takes place.

     At	some point after installing the	base set, select the
     BBuuiilldd DDeevviicceess option from the FFiillee	menu if	you have not
     already done so. This will	create a bunch of device nodes
     for you and will create your initial _/_e_t_c_/_f_s_t_a_b.  The
     Installer program also has	an option to give you a	mini-
     shell. Do not use this unless you are sure	know what you are
     doing.

     When you are finished installing all of the sets you wish to
     install, exit the Installer by choosing QQuuiitt from the FFiillee
     menu.

     _B_o_o_t_i_n_g _t_h_e _s_y_s_t_e_m

     Prior to attempting to boot NetBSD/mac68k,	please verify
     that all of the following are true:

     1.	  32-bit addressing is enabled [2] in the Memory control
	  panel;

     2.	  All forms of virtual memory are disabled (the	Memory
	  control panel, RAM Doubler, or other software-based
	  memory enhancement products);	and

     3.	  Your system is in B&W	mode (1-bit color or grayscale)
	  as shown by the Monitors control panel. You may choose
	  to have the Booter do	this for you automatically by
	  selecting the	appropriate check box and radio	button in
	  the MMoonniittoorrss dialog on the OOppttiioonnss menu.

     It	is probably best to boot your machine with all extensions
     turned off	[2]. You can do	this by	booting	into Mac OS with
     the SHIFT key held	down. You may have to restart your Macin-
     tosh for changes to take effect before proceeding.

     [2]  If your version of the Memory	control	panel does not
	  have a 32-bit	addressing mode	radio button, this means
	  that your system is already 32-bit clean and is running
	  in 32-bit addressing mode by default.	 If the	Booter
	  complains that you are not in	32-bit mode, it	may be
	  necessary for	you to press the UUssee DDeeffaauullttss button in
	  the Memory control panel to restore 32-bit addressing.
	  You should probably reboot after doing so.  If you have
	  an older II-class system (including the II, IIx, IIcx,
	  and SE/30), it is necessary to install Connectix's
	  MODE32 to work around	ROM issues which prevent you from
	  enabling 32-bit addressing. Please see the
	  NetBSD/mac68k	FAQ at
		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c6688kk//ffaaqq//
	  for more information.

     Double-click on the NetBSD/mac68k Booter icon to start the
     application.  Select BBoooottiinngg from the OOppttiioonnss menu. Check
     that all of the items in the resulting dialog look	sane -
     especially	the SCSI target	number.	 If not, correct them to
     your preference (the SCSI target number, or "SCSI ID",
     should be the only	thing you need to change). When	you are
     satisfied with your choices, try booting NetBSD by	selecting
     BBoooott NNooww from the OOppttiioonnss menu.

     If	you wish to save your preferences, choose SSaavvee OOppttiioonnss
     from the FFiillee menu	before Booting (your preferences will not
     be	saved if you forget to do this).

     If	the system does	not come up, send mail to
     _p_o_r_t_-_m_a_c_6_8_k_@_N_e_t_B_S_D_._o_r_g describing your software, your hard-
     ware, and as complete a description of the	problem	as you
     can.

     If	the system does	come up, congratulations, you have suc-
     cessfully installed NetBSD	9.3.

   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t22220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,
	  NuBus	or PDS interface may be	ae0, mc0 or sn0.  For
	  example:

		ifconfig_sn0="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_sn0="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:

	  [Color_X]  Some systems are capable of supporting a
		     color X Server in either thousands	or mil-
		     lions of colors.  The mac68k port does not
		     support resolution	switching at this time.
		     If	your system is capable of running the
		     color X Server it can be installed	at this
		     point and the Booter options can be modified
		     to	match the resolution depth.

     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.

	  --   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

	  --   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

	  --   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_6_8_k_/_9_._3_/_A_l_l subdir.  If	you
	      installed	pkgin(1) in the	ssyyssiinnsstt	post-installation
	      configuration menu, you can use it to automatically
	      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 cor-
	      rectly 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
	      ##	ppkkggiinn iinnssttaallll bbaasshh
	      ##	ppkkggiinn iinnssttaallll ppeerrll
	      ##	ppkkggiinn iinnssttaallll aappaacchhee
	      ##	ppkkggiinn iinnssttaallll kkddee
	      ##	ppkkggiinn iinnssttaallll ffiirreeffooxx
	      ...

	      _N_o_t_e_:  Some mirror sites don't mirror the
		     _/_p_u_b_/_p_k_g_s_r_c directory.

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

	  --   If you did not install it	from the ssyyssiinnsstt post-
	      installation configuration menu, the pkgsrc(7)
	      framework	for compiling packages can be obtained 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

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

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

	  --   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 9.3 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.

     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 9.3 system.  However,	that
     doesn't mean that you're finished with the	upgrade	process.
     You will probably want to update the set of device	nodes you
     have in _/_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 9.3.

     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.

     A number of things	have been removed from the NetBSD 9.3
     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

	   --   intro(1),
	   --   man(1),
	   --   apropos(1),
	   --   passwd(1), and
	   --   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
     --	 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.

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

     --	 The Internet Research Institute in Japan for hosting the
	 server	which runs the CVSweb interface	to the NetBSD
	 source	tree.

     --	 The Columbia University Computer Science Department for
	 hosting the build cluster.

     --	 The many organizations	that provide NetBSD mirror sites.

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

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

     --	 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 Projet.
     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 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 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 Yasushi Yamasaki
     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
   CCoonnttrriibbuuttiioonnss
     The following people have made contributions of various
     sorts specifically	for the	Macintosh port (in alphabetical
     order):

     --	 All of	the users who have supplied us with good bug
	 reports and moral support.

     --	 The Alice Group (Allen	K. Briggs, Chris P. Caputo,
	 Michael L. Finch, Bradley A. Grantham,	and Lawrence A.
	 Kesteloot), without whom there	would be no NetBSD port
	 for the Macintosh.

     --	 Steven	R. Allen for keeping our snapshot distributions
	 up-to-date.

     --	 Stephen C. Brown for maintaining the Installer	applica-
	 tion.

     --	 Denton	Gentry and Yanagisawa Takeshi for their	work on
	 the SONIC Ethernet driver.

     --	 Paul Goyette, Taras Ivanenko, Ken Nakata, and Michael R.
	 Zucca for invaluable work towards supporting color X.

     --	 Takashi Hamada	and John Wittkoski beating the direct ADB
	 hardware driver into submission.

     --	 David Huang for getting MACE Ethernet and basic DMA
	 working on the	AV Macs.

     --	 Scott Jann for	acquiring a IIx	and a IIci, used for
	 building and testing release sets.

     --	 Scott Kaplan for lending his IIci and Kensington Turbo
	 Mouse for IIci/IIsi banked memory and internal	video as
	 well as non-Apple ADB devices.

     --	 Noah M. Kieserman for lending a PowerBook 520C	for
	 tracking down several bugs on that platform.

     --	 Markus	Krummenacker for monetary donations.

     --	 Glan Lalonde for an invaluable	IIci page table	dump.

     --	 Dan McMahill for lending a PowerBook 165 to tweak ADB
	 support on the	PowerBook 160 and 180 family laptops.

     --	 Bob Nestor for	(unofficially) maintaining the Mkfs util-
	 ity, and providing a lot of useful information	about the
	 ROM vectors used by different systems.

     --	 Brad Parker for serial	and Ethernet drivers/improve-
	 ments.

     --	 Brian R. Gaeke	and Nigel Pearson for tweaking,	polish-
	 ing, and performing the occasional major refit	on the
	 Booter	application.

     --	 Scott Redman for lending Brad Grantham	a PowerBook 160.

     --	 Craig Ruff for	assembling an '030 pmove ttx instruction.

     --	 Brad Salai for	lending	an Ethernet card to help resolve
	 interrupt conflicts.

     --	 Larry Samuels for monetary donations.

     --	 Peter Siebold for lending his IIvx in support of ADB and
	 IIvx internal video.

     --	 Glen Stewart for lending a Carrera040 accelerator which,
	 while still unsupported, helped to track down memory
	 management bugs for '030-based	machines.

     --	 Bill Studenmund for providing a stable	front end to the
	 machine- independent serial driver.

     --	 Schuyler Stultz for the loan of his Macintosh II when we
	 desperately needed another machine on which to	compile
	 and test during the '93 Xmas vacation.

     --	 Tenon Intersystems for	monetary donations, MachTen, and
	 Brad's	access to several machines and documentation
	 after hours.

     --	 Virginia Tech English Department for loan of a	IIci w/
	 NuBus video and 32 MB of RAM -- the first IIci	to run
	 NetBSD/mac68k.

     --	 Rob Windsor for donating a variety of Macintosh II-fam-
	 ily systems, a	Centris	650, a Quadra 700, and several
	 boxes full of miscellaneous peripherals and parts in the
	 interest of ensuring adequate testing and working out
	 minor (and not-so-minor) problems.

     --	 Colin Wood for	maintaining a host of NetBSD/mac68k docu-
	 mentation, including the FAQ, Meta-FAQ, and OS	Info doc-
	 uments.

NetBSD/mac68k 9.3		 Aug 04, 2022		     NetBSD/mac68k 9.3
