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

CCOONNTTEENNTTSS
     About this	Document
     Quick install notes for the impatient
     What is NetBSD?
     Changes Between The NetBSD	10 and 11 Releases, and	newer
     Features to be removed in a later release
     The NetBSD	Foundation
     Sources of	NetBSD
     NetBSD 11.99.6 Release Contents
	NetBSD/sparc64 subdirectory structure
	Binary distribution sets
     NetBSD/sparc64 System Requirements	and Supported Devices
	Supported machines
	Unsupported machines
	Supported devices
	Unsupported devices
     Getting the NetBSD	System on to Useful Media
     Preparing your System for NetBSD installation
	Deciding on partition sizes
	Setting	up Open	Firmware
	Determining how	to boot	from an	SBUS or	PCI card
	Configuration of network interfaces
     Installing	the NetBSD System
	Installing NetBSD from CD-ROM
	Installing NetBSD by using the NetBSD miniroot
	Installing NetBSD by using a NetBSD kernel on a	Solaris	partition
	Installing NetBSD by using a netboot setup
	Running	the sysinst installation program
	   Introduction
	   General
	   Quick install
	   Booting NetBSD
	   Network configuration
	   Installation	drive selection	and parameters
	   Selecting which sets	to install
	   Partitioning	the disk
	   Preparing your hard disk
	   Getting the distribution sets
	   Installation	from CD-ROM
	   Installation	using FTP
	   Installation	using NFS
	   Installation	from an	unmounted file system
	   Installation	from a local directory
	   Extracting the distribution sets
	   Configure additional	items
	   Ensure you have the correct kernel installed
	   Finalizing your installation
	Manual Installation of NetBSD using Solaris
	   Preparing the disk in Solaris
	   Installing NetBSD Software from Solaris
	   Creating NetBSD Device Nodes	under Solaris
	   Configuring the NetBSD system from Solaris
     Booting NetBSD for	the first time
     Post installation steps
     Upgrading a previously-installed NetBSD System
     Compatibility Issues With Previous	NetBSD Releases
     Using online NetBSD documentation
     Administrivia
     Thanks go to
     Legal Mumbo-Jumbo
     The End

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

	   _._p_s	   PostScript.

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

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

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

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

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

     ++oo	 Fetch files needed to install NetBSD.	This is	either a
	 CD image (_N_e_t_B_S_D_-_1_1_._9_9_._6_-_s_p_a_r_c_6_4_._i_s_o) which can be
	 booted	directly, or the installation kernel and boot-
	 loader	(_s_p_a_r_c_6_4_/_b_i_n_a_r_y_/_k_e_r_n_e_l_/_n_e_t_b_s_d_-_I_N_S_T_A_L_L_._g_z and
	 _s_p_a_r_c_6_4_/_i_n_s_t_a_l_l_a_t_i_o_n_/_m_i_s_c_/_o_f_w_b_o_o_t) which can be booted
	 from a	Solaris	or NetBSD partition.  Alternatively, you
	 may netboot the installation kernel.  This process is
	 covered below,	in detail.

     ++oo	 The actual binary distribution	is in the
	 _s_p_a_r_c_6_4_/_b_i_n_a_r_y_/_s_e_t_s_/ directory.  When you boot	the
	 install CD-ROM	or installation	kernel,	the installation
	 program can fetch these files for you (using, e.g., ftp)
	 if you	have a network connection.  There are several
	 other methods to get the binary sets onto your	machine.

	 You will at a minimum need the	following sets:
	 _k_e_r_n_-_G_E_N_E_R_I_C_._t_g_z, _b_a_s_e_._t_g_z and	_e_t_c_._t_g_z.  In a typical
	 workstation installation you will probably want all the
	 installation sets.

     ++oo	 Burn the CD or	put the	installation kernel and	boot-
	 loader	at the root level of a bootable	Solaris	or NetBSD
	 partition.

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

     ++oo	 You will need to get to the OpenFirmware ``ookk'' prompt.
	 After your system first powers	on and displays	some ini-
	 tial information, press the STOP-A keys, or send a BREAK
	 if you're on a	serial console.	 At the	``ookk'' prompt,
	 type the command to boot your system into NetBSD.  The
	 command to boot from CD is: ``bboooott ccddrroomm''.  The command
	 to boot the NetBSD kernel from	a Solaris or NetBSD par-
	 tition	depends	on which disk and partition it is on.  To
	 boot from the first partition of the first (primary)
	 disk: ``bboooott ddiisskk::aa //ooffwwbboooott --aa''.  When it asks you for
	 a kernel, specify ``nneettbbssdd--IINNSSTTAALLLL..ggzz''

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

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

     NetBSD is a completely integrated system.	In addition to
     its highly	portable, high performance kernel, NetBSD fea-
     tures a complete set of user utilities, compilers for sev-
     eral languages, the X Window System, firewall software and
     numerous other tools, all accompanied by full source code.

     NetBSD is a creation of the members of the	Internet commu-
     nity.  Without the	unique cooperation and coordination the
     net makes possible, NetBSD	would not exist.

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

     Please note that this build is a development snapshot, not	a
     formal release.  You are testing the bleeding edge	of NetBSD
     development, and no formal	or informal testing may	have been
     done for this snapshot (yet).

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

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

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

     If	you are	upgrading from a version of NetBSD-current please
     also check	the _C_o_m_p_a_t_i_b_i_l_i_t_y _I_s_s_u_e_s _W_i_t_h _P_r_e_v_i_o_u_s _N_e_t_B_S_D
     _R_e_l_e_a_s_e_s.	It is impossible to completely summarize the mas-
     sive development that went	into the NetBSD	11.99.6	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::////nnyyccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD--ddaaiillyy//HHEEAADD//llaatteesstt//CCHHAANNGGEESS
     _C_H_A_N_G_E_S_._p_r_e_v_:
	   hhttttppss::////nnyyccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD--ddaaiillyy//HHEEAADD//llaatteesstt//CCHHAANNGGEESS..pprreevv

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

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

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

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

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

   NNeettBBSSDD 1111..9999..66 RReelleeaassee CCoonntteennttss
     The root directory	of the NetBSD 11.99.6 release is orga-
     nized as follows:

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

     CHANGES	   Changes after the netbsd-11 branch.

     CHANGES.prev  Changes in previous NetBSD releases.

     README.files  README describing the distribution's	contents.

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

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

     In	addition to the	files and directories listed above, there
     is	one directory per architecture,	for each of the	architec-
     tures for which NetBSD 11.99.6 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	11.99.6
	       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
	       11.99.6 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.
     Individual	sets may be unpacked into _/_u_s_r_/_s_r_c with	the com-
     mand:
	   # 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_/_s_p_a_r_c_6_4 _s_u_b_d_i_r_e_c_t_o_r_y _s_t_r_u_c_t_u_r_e

     The sparc64-specific portion of the NetBSD	11.99.6	release
     is	found in the _s_p_a_r_c_6_4 subdirectory of the distribution:
     _._._._/_N_e_t_B_S_D_-_1_1_._9_9_._6_/_s_p_a_r_c_6_4_/.  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 gzipped NetBSD	kernel
				       containing code for every
				       system supported	in this
				       release.	 This kernel sup-
				       ports SMP on systems with
				       more than one CPU.
			    _n_e_t_b_s_d_-_G_E_N_E_R_I_C_._U_P_._g_z
				       A gzipped NetBSD	kernel
				       containing code for every
				       system supported	in this
				       release.	 This kernel dis-
				       ables SMP support.
			    _n_e_t_b_s_d_-_I_N_S_T_A_L_L_._g_z
				       The install kernel.
		   _s_e_t_s_/    sparc64 binary distribution	sets; see
			    below.
     _i_n_s_t_a_l_l_a_t_i_o_n_/
		   _m_i_n_i_r_o_o_t_/  sparc64 miniroot file system image;
			      see below.
		   _m_i_s_c_/      Miscellaneous sparc64 installation
			      utilities; see installation section
			      below.
		   _n_e_t_b_o_o_t_/   Netboot bootloader; see below.

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

     The NetBSD	sparc64	binary distribution sets contain the
     binaries which comprise the NetBSD	11.99.6	release	for
     sparc64.  The binary distribution sets can	be found in the
     _s_p_a_r_c_6_4_/_b_i_n_a_r_y_/_s_e_t_s subdirectory of the NetBSD 11.99.6 dis-
     tribution tree.

     _N_o_t_e_:  If you want	to install 32-bit only binaries, you will
	    still need to boot using the sparc64 installation
	    tools.  When sysinst asks you for the distribution
	    set	to install, provide the	NetBSD/sparc _b_i_n_a_r_y_/_s_e_t_s.
	    Be sure to use the 32 bit sparc
	    _k_e_r_n_-_G_E_N_E_R_I_C___S_U_N_4_U_._t_g_z kernel distribution.	 Other-
	    wise, continue to follow the sparc64 installation
	    procedure, not the sparc instructions.
     Most people will want the 64-bit sparc64 distribution tree:

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

     ccoommpp     Things needed for	compiling programs.  This set
	      includes the system include files	(_/_u_s_r_/_i_n_c_l_u_d_e)
	      and the various system libraries (except the shared
	      libraries, which are included as part of the bbaassee
	      set).  This set also includes the	manual pages for
	      all of the utilities it contains,	as well	as the
	      system call and library manual pages.

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

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

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

     kkeerrnn--GGEENNEERRIICC
	      This set contains	a NetBSD/sparc64 11.99.6 GENERIC
	      kernel named _/_n_e_t_b_s_d.  You _m_u_s_t install this or the
	      kern-GENERIC.UP distribution set.

     kkeerrnn--GGEENNEERRIICC..UUPP
	      This set contains	a NetBSD/sparc64 11.99.6
	      GENERIC.UP kernel	named _/_n_e_t_b_s_d, with SMP	support
	      disabled.

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

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

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

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

     tteexxtt     This set includes	NetBSD's text processing tools,
	      including	groff(1), all related programs,	and their
	      manual pages.

     NetBSD maintains its own set of sources for the X Window
     System in order to	assure tight integration and compatibil-
     ity.  These sources are based on X.Org.  Binary sets for the
     X Window System are distributed with NetBSD.  The sets are:

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

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

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

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

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

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

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

     The instructions given for	extracting the source sets work
     equally well for the binary sets, but it is worth noting
     that if you use that method, the filenames	stored in the
     sets are relative and therefore the files are extracted
     _b_e_l_o_w _t_h_e _c_u_r_r_e_n_t _d_i_r_e_c_t_o_r_y.  Therefore, if you want to
     extract the binaries into your system, i.e., replace the
     system binaries with them,	you have to run	the ttaarr	--xxzzppff
     command from the root directory ( _/ ) of your system.

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

   NNeettBBSSDD//ssppaarrcc6644 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
     _S_u_p_p_o_r_t_e_d _m_a_c_h_i_n_e_s

     The minimal configuration requires	32 MB of RAM and ~180 MB
     of	disk space.  To	install	the entire system requires much
     more disk space, and to run X or compile the system, more
     RAM is recommended.  Note that until you have at least 64 MB
     of	RAM, getting more RAM is more important	than getting a
     faster CPU.

     Not all of	the machines listed here have been tested.  Often
     Sun used the same motherboard design in multiple models.
     For example, there	might be a Blade ("workstation") model,
     Enterprise	or Fire	("server") model, and Netra or ft
     ("telco") model with essentially the same devices,	as far as
     NetBSD is concerned.  If one model	in this	scheme works, it
     is	highly likely another will work.

     Sun has also released a few models	with names that	might
     imply the systems are UltraSPARC-based but	actually have an
     i386/amd64	class CPU.  These systems might	be supported by
     the i386 or amd64 ports of	NetBSD.

	   ++oo   Sbus-based UltraSPARC I or II systems
	       --   Ultra 1 family (Ultra 1, Ultra 1 Creator,
		   Ultra 1 Creator 3D, Netra i 150, Netra nfs
		   150,	Enterprise 1, Enterprise 150)
	       --   Ultra 2 family (Ultra 2, Ultra 2 Creator,
		   Ultra 2 Creator 3D, Enterprise 2)
	       --   Enterprise (3000, 3500, 4000, 4500, 500x,
		   5500, 600x, 6500, 10000)

	   ++oo   PCI-based UltraSPARC II,	IIi, IIe, III, or IIIi
	       systems
	       --   Ultra 5/10 family (Ultra 5, Ultra 10, Enter-
		   prise 5, Enterprise 10)
	       --   Ultra 30 family (Ultra 30, Netra T 1100)
	       --   Ultra 60 family (Ultra 60, E220R, Netra T 1120
		   and T 1125)
	       --   Ultra 80 family (Ultra 80, E420R, Netra T 1400
		   and T 1405)
	       --   Ultra 250 family (Enterprise	250 and	E250R)
	       --   Ultra 450 family (Ultra 450,	Enterprise 450,
		   Netra ft 1800)
	       --   SunBlade 100	and 150
	       --   SPARCengine CP1400 or SPARCengine CP1500 sys-
		   tem boards (Netra T1	(models	100 and	105),
		   CT400, CT800, CT1600)
	       --   SPARCengine Ultra AXi family	(Netra X1, Fire
		   v100, Fire v120, Netra 120, Netra AC	200,
		   Netra DC 200)
	       --   SPARCengine Ultra AXe system	board
	       --   SunBlade 1000 and 2000
	       --   SunBlade 1500, 2500 (Red and	Silver)
	       --   Ultra 25 and	45
	       --   Sun Fire v125, v210,	v215, v240, v245, v250,
		   v440, v445, v480

     _U_n_s_u_p_p_o_r_t_e_d _m_a_c_h_i_n_e_s

	   ++oo   Systems with an UltraSPARC IV CPU

	   ++oo   Systems with an UltraSPARC T1-T5	CPU

	   ++oo   Systems with a Fujitsu SPARC64 CPU

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

	   ++oo   Ethernet	devices
	       --   Sbus	LANCE ethernet (_l_e)
	       --   Sbus	BigMac ethernet	(_b_e)
	       --   On-board, PCI, and Sbus HME ethernet	(_h_m_e)
	       --   PCI ERI (_g_e_m)
	       --   Many	other PCI and PCMCIA Ethernet interfaces,
		   including:
		   ++oo   Tulip-compatible	(_t_l_p)
		   ++oo   Intel (_f_x_p)
		   ++oo   Intel gigabit (_w_m)
		   ++oo   NE2000-compatible (_n_e)
		   ++oo   Realtek (_r_t_k or _r_e)
		   ++oo   SysKonnect XMAC II (_s_k)
		   ++oo   Marvell GMAC (_m_s_k)
	       --   Several USB Ethernet	interfaces, such as (_a_u_e,
		   _c_u_e,	and _k_u_e)

	   ++oo   Wireless	network	adapters
	       --   Atheros wireless cards (_a_t_h)

	   ++oo   Video devices
	       --   All on-board	frame buffers
		   Unless otherwise specified, only text console
		   is supported
	       --   On-board and	SBUS card (GX, GX+, TGX, TGX+)
		   (_c_g_s_i_x)
		   8 bpp accelerated framebuffer.  Accelerated X
		   via the integrated Xorg.
	       --   UPA devices (ffb and	afb, also called
		   Creator3D) 24 bpp accelerated framebuffer.
		   Accelerated X via the integrated Xorg.
	       --   On-board ATI	mach64 framebuffers (found in
		   Ultra 5/10).

	   ++oo   SCSI host controllers
	       --   ncr53c9x based controllers (_e_s_p)
	       --   ncr53c8xx based controllers (_s_i_o_p or	_e_s_i_o_p)
	       --   ISP10x0 based controllers (_i_s_p)
	       --   Adaptec AHA-2x4x[U][2][W] cards and onboard
		   PCI designs using the AIC-7770, AIC-7850,
		   AIC-7860, AIC-7870, AIC-7880	and AIC-789x
		   chipsets.

		   _N_o_t_e_:  Some Adaptec cards that support booting
			  on MacOS may be bootable on sparc64
			  systems.
	       --   Many	other PCI SCSI controllers should work,
		   but no one has tried	them
	       --   Most	SCSI disk/tape/CD-ROM devices should work

	   ++oo   PCI IDE host controllers
	       --   Generic IDE controllers (_p_c_i_i_d_e)
	       --   Acard ATP-850/860 based IDE controllers
		   (_p_c_i_i_d_e)
		   (including the Acard	AEC-6210/6260 and the
		   Sonnet Tempo	ATA/66 cards)
	       --   CMD Tech PCI064[3689] and Silicon Image 0680
		   IDE Controllers (_c_m_d_i_d_e)
	       --   Silicon Image 3112, 3114, and 3512 SATA Con-
		   troller (_s_a_t_a_l_i_n_k)

		   _N_o_t_e_:  Some IDE cards that support booting on
			  MacOS	may be bootable	on sparc64 sys-
			  tems.
	       --   Many	other PCI IDE controllers should work,
		   but no one has tried	them
	       --   Most	IDE and	ATAPI disk/tape/CD-ROM devices
		   should work

	   ++oo   Floppy drives
	       --   On-board Floppy Disk	Controller -- SBus
		   machines only for now (_f_d_c)

	   ++oo   Serial devices
	       --   On-board Sbus z8530 serial (_z_s)
	       --   On-board PCI	16550-based su and su-pnp serial
		   (_c_o_m)
	       --   On-board PCI	SAB82532 dual UART serial (_s_a_b)

	   ++oo   Parallel	devices
	       --   On-board and	Sbus parallel ports (_b_p_p)
	       --   On-board PCI/Ebus parallel ports (_l_p_t)

	   ++oo   Audio devices
	       --   On-board, PCI, and SBus based CS4231-based 44
		   KHz,	16 bit,	stereo,	PCM audio (_a_u_d_i_o_c_s)

	   ++oo   Other PCI devices
	       --   PCI ``universal'' communications cards (_p_u_c)

     There are a large number of untested PCI drivers that have
     never been	tested on UltraSPARC PCI systems that may `just
     work'.

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

     Smart card	readers.

   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
     Installation is supported from several media types, includ-
     ing:

	   ++oo   CD-ROM /	DVD / USB stick
	   ++oo   FTP
	   ++oo   Remote NFS partition
	   ++oo   Tape
	   ++oo   Existing	NetBSD partitions, if performing an
	       upgrade

     The steps necessary to prepare the	distribution sets for
     installation depend upon which installation medium	you
     choose.  The steps	for the	various	media are outlined below.

     _N_o_t_e_:  If you are installing the 32-bit sparc distribution
	    sets, you will need	to rename
	    _s_p_a_r_c_/_b_i_n_a_r_y_/_s_e_t_s_/_k_e_r_n_-_G_E_N_E_R_I_C___S_U_N_4_U_._t_g_z to
	    _k_e_r_n_-_G_E_N_E_R_I_C_._t_g_z since the sparc64 installation tools
	    would otherwise attempt to install the kernel for
	    32-bit sparc computers which does not boot on sparc64
	    systems.

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

			       Proceed to the instructions on
			       installation.

     _F_T_P		       The preparations	for this instal-
			       lation/upgrade method are easy;
			       all you need to do is make sure
			       that there's an FTP site	from
			       which you can retrieve the NetBSD
			       distribution when you're	about to
			       install or upgrade.  If you don't
			       have DHCP available on your net-
			       work, you will need to know the
			       numeric IP address of that site,
			       and, if it's not	on a network
			       directly	connected to the machine
			       on which	you're installing or
			       upgrading NetBSD, you need to know
			       the numeric IP address of the
			       router closest to the NetBSD
			       machine.	 Finally, you need to
			       know the	numeric	IP address of the
			       NetBSD machine itself.

			       Once you	have this information,
			       you can proceed to the next step
			       in the installation or upgrade
			       process.	 If you're installing
			       NetBSD from scratch, go to the
			       section on preparing your hard
			       disk, below.  If	you're upgrading
			       an existing installation, go
			       directly	to the section on upgrad-
			       ing.

     _N_F_S		       Place the NetBSD	distribution sets
			       you wish	to install into	a direc-
			       tory on an NFS server, and make
			       that directory mountable	by the
			       machine on which	you are
			       installing or upgrading NetBSD.
			       This will probably require modify-
			       ing the _/_e_t_c_/_e_x_p_o_r_t_s file on the
			       NFS server and resetting	its mount
			       daemon (mountd).	 (Both of these
			       actions will probably require
			       superuser privileges on the
			       server.)

			       You need	to know	the numeric IP
			       address of the NFS server, and, if
			       you don't have DHCP available on
			       your network and	the server is not
			       on a network directly connected to
			       the machine on which you're
			       installing or upgrading NetBSD,
			       you need	to know	the numeric IP
			       address of the router closest to
			       the NetBSD machine.  Finally, you
			       need to know the	numeric	IP
			       address of the NetBSD machine
			       itself.

			       Once the	NFS server is set up
			       properly	and you	have the informa-
			       tion mentioned above, you can pro-
			       ceed to the next	step in	the
			       installation or upgrade process.
			       If you're installing NetBSD from
			       scratch,	go to the section on pre-
			       paring your hard	disk, below.  If
			       you're upgrading	an existing
			       installation, go	directly to the
			       section on upgrading.

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

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

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

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

				     # ccdd ......//NNeettBBSSDD--1111..9999..66
				     # ccdd ssppaarrcc6644//bbiinnaarryy
				     # ttaarr --ccff _t_a_p_e___d_e_v_i_c_e
				     kkeerrnn--GGEENNEERRIICC..ttggzz bbaassee..ttggzz
				     eettcc..ttggzz

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

			       Once you	have the files on the
			       tape, you can proceed to	the next
			       step in the installation	or
			       upgrade process.	 If you're
			       installing NetBSD from scratch, go
			       to the section on preparing your
			       hard disk, below.  If you're
			       upgrading an existing installa-
			       tion, go	directly to the	section
			       on upgrading.

   PPrreeppaarriinngg yyoouurr SSyysstteemm ffoorr NNeettBBSSDD iinnssttaallllaattiioonn
     _D_e_c_i_d_i_n_g _o_n _p_a_r_t_i_t_i_o_n _s_i_z_e_s

     If	you're installing NetBSD/sparc64 for the first time it's
     a good idea to look at the	partition sizes	of the disk you
     plan to install NetBSD on.	 Will you be installing	NetBSD
     onto the same disk	as Solaris, on its own disk, or	will you
     be	netbooting?  While NetBSD can work just	fine on	a disk
     shared with Solaris, the NetBSD installer does not	currently
     support this.  The	limitation is that the NetBSD
     disklabel(8) writes partition info	that Solaris is	not
     familiar with.  Therefore,	if you are sharing a disk with
     Solaris, any time you change a partition table, you must do
     it	from Solaris.

     Assuming a	classic	partition scheme with _/	(root) and _/_u_s_r
     file systems, a comfortable size for the NetBSD _/ partition
     is	about 200 MB.  A full binary installation including X
     takes over	600 MB in _/_u_s_r.	 Since the pkgsrc binaries are
     typically installed in _/_u_s_r_/_p_k_g you may want a significantly
     larger _/_u_s_r partition.  A good initial size for the swap
     partition is the amount of	physical memory	in your	machine
     if	you've got more	than 128 MB RAM.  If you've got	less RAM,
     you may want swap to be at	least 128 MB.

     Note that the OBP on Ultra	1 and Ultra 2 machines can only
     boot from the first 4Gb of	the disk, so this limits the size
     of	the root partition on these models.

     _S_e_t_t_i_n_g _u_p	_O_p_e_n _F_i_r_m_w_a_r_e

     First, you	need to	stop your system from automatically boot-
     ing when powered on. Pressing the STOP key	(sometimes called
     the L1 key, found on the left side	of your	keyboard) and the
     a key will	halt your system and give you the ``ok'' prompt.
     If	you are	using a	serial console,	send a ``BREAK'' signal
     from your terminal	(the method of sending ``BREAK'' varies
     from terminal to terminal).

     If	the ethernet address of	your sparc64 system is
     ff:ff:ff:ff:ff:ff (check with the Open Firmware ``banner''
     command), then your NVRAM battery is dead and you will have
     trouble using ethernet (among other problems).  Read the _S_u_n
     _N_V_R_A_M_/_H_o_s_t_i_d _F_A_Q_:
	   hhttttppss::////wweebb..aarrcchhiivvee..oorrgg//wweebb//2200115500661111009911661166//hhttttppss::////wwwwww..ssqquuiirrrreell..ccoomm//ssqquuiirrrreell//ssuunn--nnvvrraamm--hhoossttiidd..ffaaqq..hhttmmll.

     If	you have a valid ethernet address and you plan to net-
     boot, write down your system's ethernet address.

     You cannot	use the	security modes of the SPARC OpenFirmware.

	   ok sseetteennvv sseeccuurriittyy--mmooddee nnoonnee

     If	you are	using a	serial console,	the NetBSD/sparc64
     installer defaults	to using 9600 bps, 8N1 settings.  You may
     want to configure your system and serial terminal like this
     prior to booting the installer.  A	new installation of
     NetBSD/sparc64 will default to these settings as well.

     SCSI devices are specified	by an Open Firmware ddeevvaalliiaass
     which provides simple mnemonics for the full path to the
     device. Type ddeevvaalliiaass to get a list of all	of the available
     aliases.  At a minimum, the alias and partition are neces-
     sary when booting.

     Therefore,	to boot	from the swap partition	on the internal
     hard drive	one would use:

	   ok bboooott ddiisskk::bb

     To	boot from a CD-ROM (Open Firmware assumes SCSI CD-ROMs
     are at target 6), one would use:

	   ok bboooott ccddrroomm

     And to boot from a	kernel named netbsd-GENERIC on the fourth
     partition ( `d', often the	_/_u_s_r partition)	on an external
     SCSI hard drive (target 2,	partition 3), one would	use:

	   ok bboooott ddiisskk22::dd nneettbbssdd--GGEENNEERRIICC

     If	you get	``.... Fast Data MMU Miss'' when booting after
     the NetBSD	installation, your OpenBoot PROM may need updat-
     ing. It has been reported that version 3.31 lead to a suc-
     cessful boot on an	Ultra Enterprise 420R, while version 3.23
     did not. Exact values may vary, depending on your hardware,
     current OpenBoot PROM version and moon phase.

     _D_e_t_e_r_m_i_n_i_n_g _h_o_w _t_o	_b_o_o_t _f_r_o_m _a_n _S_B_U_S _o_r _P_C_I _c_a_r_d

     Some SBUS and PCI cards have firmware that	lets you use them
     as	boot devices.  These cards do not automatically	create
     ddeevvaalliiaass entries, so you must traverse the	device tree to
     figure out	what Open Firmware calls your card.  You will be
     using Open	Firmware commands at the `ok' prompt. First `cd'
     to	the top	of the device tree and list the	nodes there.  The
     following is the procedure	to boot	from an	IDE card in an
     UltraSPARC	30.

	   ok ccdd //
	   ok llss
	   f006cf08 SUNW,ffb@1e,0
	   f006c32c SUNW,UltraSPARC-II@0,0
	   f006002c counter-timer@1f,1c00
	   f005f410 pci@1f,2000
	   f005eb54 pci@1f,4000
	   f004cf84 virtual-memory
	   f004c9a4 memory@0,0
	   f002ce38 aliases
	   f002cdc8 options
	   f002cc90 openprom
	   f002cc24 chosen
	   f002cbb4 packages
     Usually, you can simply type in the name before the at (@)
     sign and OpenFirmware will	fill in	the rest.

	   ok ccdd ppccii@@11ff,,44000000
	   ok llss
	   f0081524 ide@2
	   f007be50 scsi@3
	   f0074688 network@1,1
	   f0060324 ebus@1
	   ok ccdd iiddee@@22
	   ok llss
	   0081fe4 cdrom
	   f0081938 disk
	   ok ccdd ddiisskk
	   ok llss
	   ok ppwwdd
	   /pci@1f,4000/ide@2/disk
     OK, now we	know the path to the IDE device	in this	example.
     Now, we need to determine if it's capable of booting.  If it
     is, it will have the wwoorrdd `open'.

	   ok wwoorrddss
	   close	 load	       write	     read	   seek
	   open		 write-blocks  read-blocks   max-transfer
	   block-size	 dma-free      dma-alloc     spin-down	   spin-up
     Great!  Also, in case you're interested in	further	details
     about your	hardware, you can use the ..pprrooppeerrttiieess command.

     So, when it's time	to type	in a boot command, use the short-
     ened version of the ppwwdd command.  You need	to be more spe-
     cific if there are	two devices with the same name (in this
     case, two /pci entries).  In this example,	you'd type:

	   ok bboooott //ppccii@@11ff,,44000000//iiddee//ddiisskk@@00,,00
     You can also store	this device path across	reboots	using the
     nnvvaalliiaass command.

	   ok nnvvaalliiaass wwdd00 //ppccii@@11ff,,44000000//iiddee//ddiisskk@@00,,00::aa

     And when the kernel is done booting, it may not automati-
     cally use your card as the	root device -- you may need to
     type in the NetBSD/sparc64	name for that device:

	   root	on sd0a	dumps on sd0b
	   no file system for sd0 (dev 0x700)
	   cannot mount	root, error = 79
	   root	device (default	sd0a): ?
	   use one of: hme0 sd0[a-h] wd0[a-h] halt
	   root	device (default	sd0a): wwdd00aa
	   dump	device:	wwdd00aa
	   file	system (default	generic): ffffss
	   root	on wd0a

     The root device can also be specified in your kernel config
     file.

     _C_o_n_f_i_g_u_r_a_t_i_o_n _o_f _n_e_t_w_o_r_k _i_n_t_e_r_f_a_c_e_s

     Some network devices (i.e., certain SBus cards) allow a
     choice between operating on a UTP or a AUI	port.  The le
     driver supports automatic detection of the	port which is
     actually connected	to the wire.  If automatic detection is
     not available or not working properly in your environment,
     you may have to specify the type connection using the _m_e_d_i_a
     parameter of ifconfig(8).	During installation, you'll get
     the opportunity to	specify	the appropriate	medium.	 Use
     10base5/AUI to select the AUI connector, or 10baseT/UTP to
     select the	UTP connector.

   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
     Installing	NetBSD is a relatively complex process,	but if
     you have this document in hand it shouldn't be too	much
     trouble.

     There are several ways to install NetBSD onto a disk.  The
     easiest way in terms of preliminary setup is to install from
     CD-ROM.  If you don't have	access to a CD-ROM or CD-ROM
     burner, you can use a miniroot image that can be booted off
     your local	disk's swap partition.	Alternatively, if your
     UltraSPARC	is hooked up in	a network you can find a server
     and arrange for a diskless	setup which is a convenient way
     to	install	on a machine whose disk	does not currently hold	a
     usable operating system (see the section _I_n_s_t_a_l_l_i_n_g _N_e_t_B_S_D
     _b_y	_u_s_i_n_g _a	_d_i_s_k_l_e_s_s _s_e_t_u_p below).

     If	you have problems with these or	you are	installing NetBSD
     onto the same disk	as Solaris, see	the section below on
     _M_a_n_u_a_l _I_n_s_t_a_l_l_a_t_i_o_n _o_f _N_e_t_B_S_D _u_s_i_n_g _S_o_l_a_r_i_s

     _I_n_s_t_a_l_l_i_n_g	_N_e_t_B_S_D _f_r_o_m _C_D_-_R_O_M

     Installing	from CD-ROM is the least painful way to	install
     NetBSD.  Simply insert the	CD-ROM in the drive, power up the
     computer, and type:

	   ok bboooott ccddrroomm

     This Open Firmware	boot command will cause	the NetBSD kernel
     contained in the CD-ROM to	be booted.  After the initial
     probe messages you'll be asked to start the install or
     upgrade procedure.	 Proceed to the	section	_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 below.

     _I_n_s_t_a_l_l_i_n_g	_N_e_t_B_S_D _b_y _u_s_i_n_g	_t_h_e _N_e_t_B_S_D _m_i_n_i_r_o_o_t

     The miniroot is a self-contained NetBSD file system holding
     all utilities necessary to	install	NetBSD on a local disk.
     It	is distributed as a plain file designed	to be transferred
     to	a raw disk partition from which	it can be booted using
     the appropriate OpenFirmware command.  Usually, the miniroot
     will be loaded into the swap partition of a disk.	If
     needed, you can use any other unused partition, but remember
     that the partition	will then not available	during the
     installation process.

     Loading the miniroot onto your raw	partition is simple using
     the dd(1) command.	 Just remember to first	uncompress the
     miniroot image and	boot your OS with the -s flag so that it
     runs ``single-user'' and does not attempt to start	swapping.

	   ok bboooott --ss

     On	Solaris	you use	a command like:

	   # gguunnzziipp mmiinniirroooott..ffss..ggzz
	   # dddd	iiff==mmiinniirroooott..ffss ooff==//ddeevv//rrddsskk//cc00tt00dd00ss11 bbss==44kk
     On	NetBSD the command is:

	   # gguunnzziipp mmiinniirroooott..ffss..ggzz
	   # dddd	iiff==mmiinniirroooott..ffss ooff==//ddeevv//rrssdd00bb bbss==44kk
     Replace /dev/rdsk/c0t0d0s1	or /dev/rsd0b with your	swap par-
     tition.

     After transferring	the miniroot to	disk, bring the	system
     down by:

	   # hhaalltt
     Then boot the miniroot by typing the appropriate command at
     the OpenFirmware prompt:

	   ok bboooott ddiisskk::bb nneettbbssdd
     If	you've loaded the miniroot onto	some other disk	than sd0
     use the correct _d_e_v_a_l_i_a_s, such as

	   ok bboooott ddiisskk11::bb nneettbbssdd
     This Open Firmware	boot command will cause	the NetBSD kernel
     contained in the miniroot image to	be booted.  After the
     initial probe messages you'll be asked to start the install
     or	upgrade	procedure.  Proceed to the section _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 below.

     _I_n_s_t_a_l_l_i_n_g	_N_e_t_B_S_D _b_y _u_s_i_n_g	_a _N_e_t_B_S_D _k_e_r_n_e_l	_o_n _a _S_o_l_a_r_i_s
     _p_a_r_t_i_t_i_o_n

     This procedure is very straightforward.  You will be putting
     the NetBSD	installation kernel (kernel with a RAM disk
     installer)	on your	Solaris	partition and telling Open
     Firmware to boot the NetBSD kernel.

     CAVEAT: this method is a bit fragile.  Depending on physical
     partition layout, partition size, and parameters used to
     create the	filesystem of your Solaris root	partition, bugs
     in	the bootloader might be	triggered and cause this method
     to	fail.

     First, copy the _n_e_t_b_s_d_-_I_N_S_T_A_L_L_._g_z kernel and bootloader to
     the root level of your hard drive and halt	your system

	   # ccpp	bbiinnaarryy//kkeerrnneell//nneettbbssdd--IINNSSTTAALLLL..ggzz	//
	   # ccpp	iinnssttaallllaattiioonn//mmiisscc//ooffwwbboooott //
	   # hhaalltt
     At	the Open Firmware prompt, boot NetBSD.

	   ok bboooott ddiisskk::aa //ooffwwbboooott --aa
     The -a flag is needed so that the bootloader will ask you to
     find your installation kernel.

	   Rebooting with command: boot	disk:a /ofwboot	-a
	   Boot	device:	/pci@1f,4000/scsi@3/disk@0,0:a	File and args: /ofwboot	-a
	   Enter filename [/ofwboot]: <<rreettuurrnn>>
	   >> NetBSD/sparc64 OpenFirmware Boot,	Revision 1.7
	   >> (autobuild@tgm.netbsd.org, Thu May 20 16:29:20 UTC 2004)
	   Boot: nneettbbssdd--IINNSSTTAALLLL..ggzz
     After the initial probe messages you'll be	asked to start
     the install or upgrade procedure.	Proceed	to the section
     _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 below.

     _I_n_s_t_a_l_l_i_n_g	_N_e_t_B_S_D _b_y _u_s_i_n_g	_a _n_e_t_b_o_o_t _s_e_t_u_p

     1.	  Introduction

	  To netboot a sparc64,	you must configure one or more
	  servers to provide information and files to your
	  sparc64 (the `client').  If you are using NetBSD (any
	  architecture)	on your	netboot	server(s), the informa-
	  tion provided	here should be sufficient to configure
	  everything.  Additionally, you may wish to look at the
	  diskless(8) manual page and the manual pages for each
	  daemon you'll	be configuring.	 If the	server(s) are
	  another operating system, you	should consult the NetBSD
	  Diskless HOW-TO, which will walk you through the steps
	  necessary to configure the netboot services on a vari-
	  ety of platforms:
		hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ddooccss//nneettwwoorrkk//nneettbboooott//

	  You may either netboot the installer so you can install
	  onto a locally attached disk,	or you may run your sys-
	  tem entirely over the	network.

	  Briefly, the netboot process involves	discovery, boot-
	  strap, kernel	and file system	stages.	 In the	first
	  stage, the client discovers information about	where to
	  find the bootstrap program.  Next, it	downloads and
	  executes the bootstrap program.  The bootstrap program
	  goes through another discovery phase to determine where
	  the kernel is	located.  The bootstrap	program	tries to
	  mount	the NFS	share containing the kernel.  Once the
	  kernel is loaded, it starts executing.  For RAM disk
	  kernels, it mounts the RAM disk file system and begins
	  executing the	installer from the RAM disk.  For normal
	  (non-RAM disk) kernels, the kernel tries to mount the
	  NFS share that had the kernel	and starts executing the
	  installation tools or	init(8).  All sparc64 systems use
	  a combination	of RARP	and DHCP for the discovery stage.
	  TFTP is used in the bootstrap	phase to download the
	  bootstrap program, _o_f_w_b_o_o_t_._n_e_t, which	has been linked
	  to a file name appropriate to	the client's IP	address
	  as described in the TFTP section below.  NFS is used in
	  both the kernel and file system stages to download the
	  kernel, and to access	files on the file server.

	  We will use `CC:CC:CC:CC:CC:CC' as the MAC address
	  (ethernet hardware address) of your netboot client
	  machine.  You	should have determined this address in an
	  earlier stage.  In this example, we will use
	  `192.168.1.10' as the	IP address of your client and
	  `client.test.net' as its name.  We will assume you're
	  providing all	of your	netboot	services on one	machine
	  called `server.test.net' with	the client's files
	  exported from	the directory _/_e_x_p_o_r_t_/_c_l_i_e_n_t_/_r_o_o_t.  You
	  should, of course, replace all of these with the names,
	  addresses, and paths appropriate to your environment.

	  You should set up each netboot stage in order	(i.e.,
	  discovery, bootstrap,	kernel,	and then file system) so
	  that you can test them as you	proceed.

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

	  Put the following lines in your _/_e_t_c_/_d_h_c_p_d_._c_o_n_f (see
	  dhcpd.conf(5)	and dhcp-options(5) for	more informa-
	  tion):

		ddns-update-style none;
				# Do not use any dynamic DNS features
				#
		allow bootp;	# Allow	bootp requests,	thus the dhcp server
				# will act as a	bootp server.
				#
		authoritative;	# master DHCP server for this subnet
				#
		subnet 192.168.1.0 netmask 255.255.255.0 {
				# Which	network	interface to listen on.
				# The zeros indicate the range of addresses
				# that are allowed to connect.
		}
		group {
				# Set of parameters common to all clients
				# in this "group".
				#
			option broadcast-address	192.168.1.255;
			option domain-name		"test.net";
			option domain-name-servers	dns.test.net;
			option routers			router.test.net;
			option subnet-mask		255.255.255.0;
				#
				# An individual	client.
				#
			host client.test.net {
				hardware ethernet	CC:CC:CC:CC:CC:CC;
				fixed-address		192.168.1.10;
				#
				# Name of the host (if the fixed address
				# doesn't resolve to a simple name).
				#
				option host-name	"client";
				#
				# Name of the bootloader or kernel
				# to download via tftp.

				#
				# The path on the NFS server.
				#
				option root-path "/export/client/root";

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

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

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

	  You will need	to start the ddhhccppdd.  If	it's already run-
	  ning,	you will need to restart it to force it	to re-
	  read its configuration file.	If the server is running
	  NetBSD, you can achieve this with:

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

     3.	  rarpd(8)

	  Create an _/_e_t_c_/_e_t_h_e_r_s	file with the following	line:

		CC:CC:CC:CC:CC:CC     client

	  Add your client to the server's _/_e_t_c_/_h_o_s_t_s file:

		192.168.1.10 client

	  You will need	to start the rraarrppdd.  If	it's already run-
	  ning,	you will need to restart it to force it	to re-
	  read its configuration file.	If the server is running
	  NetBSD, you can achieve this with:

		# //eettcc//rrcc..dd//rraarrppdd rreessttaarrtt

     4.	  tftpd(8)

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

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

	  Next,	edit _/_e_t_c_/_i_n_e_t_d_._c_o_n_f and uncomment the line with
	  the TFTP daemon:

		tftp  dgram  udp  wait	root  /usr/libexec/tftpd tftpd -l -s /tftpboot

	  Now, restart inetd(8).  If the server	is running
	  NetBSD, you can achieve this with:

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

	  Now, you need	to copy	the bootloader for your	sparc64
	  machine to _/_t_f_t_p_b_o_o_t.	 Get _o_f_w_b_o_o_t_._n_e_t from the
	  _i_n_s_t_a_l_l_a_t_i_o_n_/_n_e_t_b_o_o_t directory of the	distribution.

		# ccpp ooffwwbboooott..nneett //ttffttppbboooott

	  Now, you need	to link	_o_f_w_b_o_o_t_._n_e_t to the filename that
	  your sparc64 will look for.  It will look for	a file-
	  name composed	of the machine's IP address (in	hexadeci-
	  mal).	 For example, a	machine	which has been assigned
	  IP address 192.168.1.10, will	make a TFTP request for
	  _C_0_A_8_0_1_0_A.

	  You can use bc(1) to help calculate the filename:

		# bbcc
		oobbaassee==1166
		119922
		C0
		116688
		A8
		11
		1
		1100
		A
		qquuiitt
		# ccdd //ttffttppbboooott
		# llnn --ss	ooffwwbboooott..nneett CC00AA88001100AA

	  Just to be sure, let's make everything readable.

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

	  Sometimes, the arp(8)	table gets messed up, and the
	  TFTP server can't communicate	with the client.  In this
	  case,	it will	write a	log message (via syslogd(8)) to
	  _/_v_a_r_/_l_o_g_/_m_e_s_s_a_g_e_s saying: `tftpd: write: Host	is down'.
	  If this is the case, you may need to force the server
	  to map your client's ethernet	address	to its IP
	  address:

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

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

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

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

	  Put the following line in _/_e_t_c_/_e_x_p_o_r_t_s to enable NFS
	  sharing:

		/export/client/root -maproot=root client.test.net

	  If your server is currently running an NFS server, you
	  only need to restart mountd(8).  Otherwise, you need to
	  start	rpcbind(8) and nfsd(8).	 If the	server is running
	  NetBSD, you can achieve this with:

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

     6.	  NetBSD kernel	and installation tools

	  Now, if you place a kernel named _n_e_t_b_s_d in
	  _/_e_x_p_o_r_t_/_c_l_i_e_n_t_/_r_o_o_t your client should boot the kernel.
	  Use _b_i_n_a_r_y_/_k_e_r_n_e_l_/_n_e_t_b_s_d_-_G_E_N_E_R_I_C_._g_z.

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

	  If you are netbooting	the installer, copy the	distribu-
	  tion files to	the client's root directory and	extract
	  the tools from _i_n_s_t_a_l_l_a_t_i_o_n_/_m_i_s_c_/_i_n_s_t_f_s_._t_g_z.

		# ccpp **..ttggzz //eexxppoorrtt//cclliieenntt//rroooott
		# ccdd //eexxppoorrtt//cclliieenntt//rroooott
		# ttaarr --xxppzzff iinnssttffss..ttggzz

     7.	  Client file system

	  You can skip this step if you	do not plan to run your
	  client diskless after	installation.  Otherwise, you
	  need to extract and set up the client's installation of
	  NetBSD.  The Diskless	HOW-TO describes how to	provide
	  better security and save space on the	NFS server over
	  the procedure	listed here.  See _f_o_r _d_e_t_a_i_l_s_:
		hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ddooccss//nneettwwoorrkk//nneettbboooott//nnffss..hhttmmll.
	  ++oo   Extracting distribution sets

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

	      Continue with the	other non-essential distribution
	      sets if desired.

	  ++oo   Set up swap

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

	  ++oo   Create device nodes

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

	      This procedure only works	on NetBSD hosts.

	  ++oo   Set up the client's fstab(5)

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

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

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

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

		    rc_configured=YES
		    hostname="client"
		    defaultroute="192.168.1.1"
		    nfs_client=YES
		    auto_ifconfig=NO
		    net_interfaces=""

	      Make sure	rc does	not reconfigure	the network
	      device since it will lose	its connection to the NFS
	      server with your root file system.

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

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

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

     8.	  Setting up the server	daemons

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

		dhcpd=YES	 dhcpd_flags="-q"
		rarpd=YES	 rarpd_flags="-a"
		nfs_server=YES	       # enable	server daemons
		mountd=YES
		rpcbind=YES	 rpcbind_flags="-l"   #	-l logs	libwrap

	  Also,	you'll need to make sure the _t_f_t_p_d line	in
	  _/_e_t_c_/_i_n_e_t_d_._c_o_n_f remains uncommented.

     Now, netboot your system from the server by entering the
     appropriate bboooott command at the Open Firmware prompt.

	   ok bboooott nneett nneettbbssdd
     After the initial probe messages you'll be	asked to start
     the install or upgrade procedure.	Proceed	to the section
     _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 below.

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

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

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

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

	  The following	is a walk-through of the steps you will
	  take while installing	NetBSD on your hard disk.
	  ssyyssiinnsstt is a menu-driven program that	guides you
	  through the installation process.  Sometimes questions
	  will be asked, and in	many cases the default answer
	  will be displayed in brackets	(``[ ]'') after	the ques-
	  tion.	 If you	wish to	stop the installation, you may
	  press	CONTROL-C at any time, but if you do, you'll have
	  to begin the installation process again from scratch by
	  running the _/_s_y_s_i_n_s_t program from the	command	prompt.
	  It is	not necessary to reboot.

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

	  First, let's describe	a quick	install.  The other sec-
	  tions	of this	document go into the installation proce-
	  dure in more detail, but you may find	that you do not
	  need this.  If you want detailed instructions, skip to
	  the next section.  This section describes a basic
	  installation,	using a	CD / DVD as the	install	medium.

	  ++oo   What you need.

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

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

	      --	  An optical drive.

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

	  ++oo   The Quick	Installation

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

			  .***********************************************.
			  * NetBSD-11.99.6 Install System		  *
			  *						  *
			  *>a: Install NetBSD to hard disk		  *
			  * b: Upgrade NetBSD on a hard	disk		  *
			  * c: Re-install sets or install additional sets *
			  * d: Reboot the computer			  *
			  * e: Utility menu				  *
			  * 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.

		  WARNING: If you are installing onto a	disk
		  which	you want to use	with Solaris, stop here.
		  You will need	to perform a manual installation
		  as ssyyssiinnsstt overwrites	the Solaris partition ta-
		  ble.	See the	section	on _M_a_n_u_a_l _I_n_s_t_a_l_l_a_t_i_o_n _o_f
		  _N_e_t_B_S_D _u_s_i_n_g _S_o_l_a_r_i_s

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

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

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

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

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

	  You may want to read the boot	messages, to notice your
	  disk's name and capacity.  Its name will be something
	  like sd0 or wd0 and the geometry will	be printed on a
	  line that begins with	its name.  As mentioned	above,
	  you may need your disk's geometry when creating
	  NetBSD's partitions.	You will also need to know the
	  name,	to tell	ssyyssiinnsstt	which disk to use.  The	most
	  important thing to know is that wd0 is NetBSD's name
	  for your first IDE disk, wd1 the second, etc.	 sd0 is
	  your first SCSI disk,	sd1 the	second,	etc.

	  Once NetBSD has booted and printed all the boot mes-
	  sages, you will be presented with a welcome message and
	  a main menu.	It will	also include instructions for
	  using	the menus.

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

	  If you do not	intend to use networking during	the
	  installation,	but you	do want	your machine to	be con-
	  figured for networking once the system is installed,
	  you should first go to the UUttiilliittyy mmeennuu and select the
	  CCoonnffiigguurree nneettwwoorrkk option.  If	you only want to tempo-
	  rarily use networking	during the installation, you can
	  specify these	parameters later.  If you are not using
	  the Domain Name System (DNS),	you can	give an	empty
	  response when	asked to provide a server.

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

	  To start the installation, select IInnssttaallll NNeettBBSSDD ttoo
	  hhaarrdd ddiisskk from the main menu.

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

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

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

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

	  ++oo   Choosing which portion of	the disk to use.

	      You will be asked	if you want to use the entire
	      disk or only part	of the disk.  If you decide to
	      use the entire disk for NetBSD, ssyyssiinnsstt will check
	      for the presence of other	operating systems and you
	      will be asked to confirm that you	want to	overwrite
	      these.

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

	  The partition	table of the NetBSD part of a disk is
	  called a _d_i_s_k_l_a_b_e_l.  If your disk already has	a diskla-
	  bel written to it, you can choose UUssee	eexxiissttiinngg
	  ppaarrttiittiioonn ssiizzeess.  Otherwise, select SSeett ssiizzeess	ooff NNeettBBSSDD
	  ppaarrttiittiioonnss.

	  After	you have chosen	your partitions	and their sizes
	  (or if you opted to use the existing partitions), you
	  will be presented with the layout of the NetBSD diskla-
	  bel and given	one more chance	to change it.  For each
	  partition, you can set the type, offset and size, block
	  and fragment size, and the mount point.  The type that
	  NetBSD uses for normal file storage is called	44..22BBSSDD.
	  A swap partition has a special type called sswwaapp.  Some
	  partitions in	the disklabel have a fixed purpose.

		a	Root partition (_/)

		b	Swap partition.

		c	The entire disk.

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

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

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

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

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

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

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

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

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

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

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

     19.  _E_n_s_u_r_e _y_o_u _h_a_v_e _t_h_e _c_o_r_r_e_c_t _k_e_r_n_e_l _i_n_s_t_a_l_l_e_d

	  If you are installing	from the 32-bit	sparc distribu-
	  tion set, make sure that you installed the correct ker-
	  nel.	The sparc64 installation tools do not by default
	  copy the correct 32-bit kernel.  Unless you prepared
	  ahead	of time	by renaming the	_k_e_r_n_-_G_E_N_E_R_I_C___S_U_N_4_U_._t_g_z to
	  _k_e_r_n_-_G_E_N_E_R_I_C_._t_g_z then	you will need to follow	the next
	  few instructions.

	  Go to	the main installation menu, and	select UUttiilliittyy
	  mmeennuu and then	select the RRuunn //bbiinn//sshh option, which will
	  give you a shell prompt.  You	may need to type one of
	  the following	commands to get	your delete key	to work
	  properly, depending on your keyboard:
		# ssttttyy eerraassee ''^^hh''
		# ssttttyy eerraassee ''^^??''

	  Type the following command (replacing	_w_d_0_a with the
	  partition name of your destination root partition):
		# mmoouunntt	//ddeevv//wwdd00aa //mmnntt
		# ccdd //mmnntt
	  Now you need to mount	the location of	your distribution
	  sets:
		# mmoouunntt	//ddeevv//ccdd00aa //mmnntt22
		# ttaarr xxppzzvvff //mmnntt22//ssppaarrcc//bbiinnaarryy//kkeerrnneell//kkeerrnn--
		GGEENNEERRIICC__SSUUNN44UU..ttggzz
		# uummoouunntt //mmnntt
		# uummoouunntt //mmnntt22
		# eexxiitt

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

	  Congratulations, you have successfully installed NetBSD
	  11.99.6.  You	can now	reboot the machine and boot
	  NetBSD from hard disk.

     Skip down to the section on _B_o_o_t_i_n_g _N_e_t_B_S_D	_f_o_r _t_h_e	_f_i_r_s_t
     _t_i_m_e

     _M_a_n_u_a_l _I_n_s_t_a_l_l_a_t_i_o_n _o_f _N_e_t_B_S_D _u_s_i_n_g _S_o_l_a_r_i_s

     (Adapted from Murray Stokely's <murray@osd.bsdi.com>
     instructions)

     You can use Solaris to prepare the	NetBSD user-friendly
     installer or to perform a full manual installation	of
     NetBSD.  If you want to use the user-friendly miniroot
     installer or RAM disk installation	kernel,	follow the sec-
     tions _I_n_s_t_a_l_l_i_n_g _N_e_t_B_S_D _b_y	_u_s_i_n_g _t_h_e _N_e_t_B_S_D _m_i_n_i_r_o_o_t or
     _I_n_s_t_a_l_l_i_n_g	_N_e_t_B_S_D _b_y _u_s_i_n_g	_a _N_e_t_B_S_D _k_e_r_n_e_l	_o_n _a _S_o_l_a_r_i_s
     _p_a_r_t_i_t_i_o_n.

     Manual installation from Solaris 10 is not	possible because
     NetBSD cannot use the resulting UFS file system.  It is pos-
     sible to install Solaris 10 and NetBSD on the same	disk.  To
     do	so, partition the disk with the	Solaris	format command,
     then boot NetBSD and perform a manual installation.  Be
     careful not to write a NetBSD disklabel.  Use the disklabel
     command to	read the partition size, as constructed	from the
     Solaris disklabel.	 By default the	NetBSD newfs command
     writes a NetBSD disklabel.	 Avoid this by using the -F and
     -s	arguments to newfs.

     ++oo	 _P_r_e_p_a_r_i_n_g _t_h_e _d_i_s_k _i_n _S_o_l_a_r_i_s

	 The first step	is to format and label the disk	that you
	 would like to use with	NetBSD.	 This can be accomplished
	 with the format(1M) command in	Solaris, which allows you
	 to partition a	disk and write a disklabel.  It	also is
	 used to perform a low-level format on SCSI drives.  You
	 will want to create a root partition and a swap parti-
	 tion.	Depending on your preferences, you may also wish
	 to create separate _/_u_s_r or _/_v_a_r partitions.

	       # //uussrr//ssbbiinn//ffoorrmmaatt
	       Searching for disks...
	       Mode sense page(3) reports nsect	value as 280, adjusting	it to 218
	       done

	       c0t1d0: configured with capacity	of 16.95GB

	       AVAILABLE DISK SELECTIONS:
		      0. c0t0d0	<SUN4.2G cyl 3880 alt 2	hd 16 sec 135>
			 /pci@1f,4000/scsi@3/sd@0,0
		      1. c0t1d0	<IBM-DXHS18Y-0430 cyl 8152 alt 2 hd 20 sec 218>
			 /pci@1f,4000/scsi@3/sd@1,0
	       Specify disk (enter its number):	11
	       selecting c0t1d0
	       [disk formatted]
	       Disk not	labeled.  Label	it now?	yy

	       format> ffoorrmmaatt
	       Ready to	format.	 Formatting cannot be interrupted
	       and takes 114 minutes (estimated). Continue? y
	       Beginning format. The current time is Sat May 29	22:15:13 2004

	       Formatting...
	       done
	       Verifying media...
		       pass 0 -	pattern	= 0xc6dec6de
		  8151/19/208
		       pass 1 -	pattern	= 0x6db6db6d
		  8151/19/208

	       Total of	0 defective blocks repaired.
	       format> ppaarrttiittiioonn
	       partition> pprriinntt
	       Current partition table (original):
	       Total disk cylinders available: 8152 + 2	(reserved cylinders)

	       Part	 Tag	Flag	 Cylinders	  Size		  Blocks
		 0	 root	 wm	  0 -	60	129.86MB    (61/0/0)	 265960
		 1	 swap	 wu	 61 -  121	129.86MB    (61/0/0)	 265960
		 2     backup	 wu	  0 - 8151	 16.95GB    (8152/0/0) 35542720
		 3 unassigned	 wm	  0		  0	    (0/0/0)	      0
		 4 unassigned	 wm	  0		  0	    (0/0/0)	      0
		 5 unassigned	 wm	  0		  0	    (0/0/0)	      0
		 6	  usr	 wm	122 - 8151	 16.69GB    (8030/0/0) 35010800
		 7 unassigned	 wm	  0		  0	    (0/0/0)	      0

	       partition> llaabbeell
	       Ready to	label disk, continue? yy
	       partition> qquuiitt
	       format> qquuiitt

	 After your disk has been labeled you need to create file
	 systems on your slices.  The Solaris newfs(1M)	command
	 will create ffs file systems that can be used by NetBSD.

	       # //uussrr//ssbbiinn//nneewwffss //ddeevv//ddsskk//cc00tt11dd00ss00
	       # //uussrr//ssbbiinn//nneewwffss //ddeevv//ddsskk//cc00tt11dd00ss66

     ++oo	 _I_n_s_t_a_l_l_i_n_g _N_e_t_B_S_D _S_o_f_t_w_a_r_e _f_r_o_m _S_o_l_a_r_i_s

	 You should now	mount your NetBSD root and _/_u_s_r	parti-
	 tions under Solaris so	that you can populate the file
	 systems with NetBSD binaries.

	       # //uussrr//ssbbiinn//mmoouunntt //ddeevv//ddsskk//cc00tt11dd00ss00 //mmnntt
	       # mmkkddiirr //mmnntt//uussrr
	       # //uussrr//ssbbiinn//mmoouunntt //ddeevv//ddsskk//cc00tt11dd00ss66 //mmnntt//uussrr

	 Now extract the distribution file sets

	       # ccdd ~~//nneettbbssdd//bbiinnaarryy//sseettss
	       # gguunnzziipp	**..ttaarr..ggzz
	       # eecchhoo ~~//nneettbbssdd//bbiinnaarryy//sseettss//**..ttaarr || ((ccdd //mmnntt;; xxaarrggss --nn11 ppaaxx --rrppee	--ff ))

	 Now you should	copy the NetBSD	second stage bootloader
	 into your new root partition and install the bootblocks
	 using Solaris's installboot(1M) command.

	       # ccpp ~~//nneettbbssdd//iinnssttaallllaattiioonn//mmiisscc//ooffwwbboooott //mmnntt
	       # //uussrr//ssbbiinn//iinnssttaallllbboooott ~~//nneettbbssdd//iinnssttaallllaattiioonn//mmiisscc//bboooottbbllkk //ddeevv//rrddsskk//cc00tt11dd00ss00

     ++oo	 _C_r_e_a_t_i_n_g _N_e_t_B_S_D _D_e_v_i_c_e	_N_o_d_e_s _u_n_d_e_r _S_o_l_a_r_i_s

	 This is not a necessary step.	If your	_/_d_e_v directory is
	 empty,	init(8)	will create a RAM disk with all	of the
	 essential device nodes	each time the system boots.  If
	 you want to create the	device nodes on	disk, you will
	 need to use the Solaris mknod(1M) command.  Look in
	 _/_d_e_v_/_M_A_K_E_D_E_V for the correct names, major and minor num-
	 bers, ownership, and permissions.

     ++oo	 _C_o_n_f_i_g_u_r_i_n_g _t_h_e _N_e_t_B_S_D	_s_y_s_t_e_m _f_r_o_m _S_o_l_a_r_i_s

	 To save effort, you may want to use your favorite
	 Solaris editor	to configure some of the files in _/_e_t_c
	 before	booting	into NetBSD the	first time.  In	particu-
	 lar, you should look at _/_e_t_c_/_f_s_t_a_b, _/_e_t_c_/_r_c_._c_o_n_f,
	 _/_e_t_c_/_r_e_s_o_l_v_._c_o_n_f, and _/_e_t_c_/_h_o_s_t_s.  See	the section below
	 on _P_o_s_t _i_n_s_t_a_l_l_a_t_i_o_n _s_t_e_p_s before _B_o_o_t_i_n_g _N_e_t_B_S_D _f_o_r _t_h_e
	 _f_i_r_s_t _t_i_m_e.

   BBoooottiinngg NNeettBBSSDD ffoorr tthhee ffiirrsstt	ttiimmee
     Now it is time to boot NetBSD for the first time.	You will
     boot from your disk using similar syntax as described above
     in	_S_e_t_t_i_n_g	_u_p _O_p_e_n	_F_i_r_m_w_a_r_e and _D_e_t_e_r_m_i_n_i_n_g _h_o_w _t_o	_b_o_o_t _f_r_o_m
     _a_n	_S_B_U_S _o_r	_P_C_I _c_a_r_d.  To boot from	your first disk, type:

	   ok bboooott ddiisskk

   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 ssuunn for a local
	  console, or whatever is appropriate for your serial
	  console (some	systems	display	garbage	with a ssuunn termi-
	  nal type, you	may need to use	ssuunn--ssss55) 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, along the lines of

		ifconfig_hme0="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_hme0="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.	  Select the proper terminal devices

	  If you are using a serial console, you will have to
	  edit the _/_e_t_c_/_t_t_y_s file and change sun-ss5 to	the
	  appropriate terminal type, such as vt220.

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

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

     6.	  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:

     7.	  Installing third-party packages

	  If you wish to install any of	the software freely
	  available for	UNIX-like systems you are strongly
	  advised to first check the NetBSD package system,
	  pkgsrc.  pkgsrc automatically	handles	any changes nec-
	  essary to make the software run on NetBSD.  This
	  includes the retrieval and installation of any other
	  packages the software	may depend upon.

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

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

	  ++oo   Precompiled binaries can be found	at
		    hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//ppkkggssrrcc//ppaacckkaaggeess//NNeettBBSSDD//
	      usually in the _s_p_a_r_c_6_4_/_1_1_._9_9_._6_/_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 bbaasshh	ppeerrll aappaacchhee xxffccee44 ffiirreeffooxx
	      ...

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

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

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

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

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

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

     8.	  Misc

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

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

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

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

	      is likely	to give	you more information on	these
	      files.

   UUppggrraaddiinngg aa pprreevviioouussllyy--iinnssttaalllleedd NNeettBBSSDD SSyysstteemm
     The easiest way to	upgrade	to NetBSD 11.99.6 is with bina-
     ries, 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 11.99.6 system.  However, that
     doesn't mean that you're finished with the	upgrade	process.
     You will probably want to update the set of device	nodes you
     have in _/_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 11.99.6.

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

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

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

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

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

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

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

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

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

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

     The _m_a_n command is	used to	view the documentation on a
     topic, and	is started by entering mmaann [_s_e_c_t_i_o_n] _t_o_p_i_c.  The
     brackets [] around	the section should not be entered, but
     rather indicate that the section is optional.  If you don't
     ask for a particular section, the topic with the lowest num-
     bered section name	will be	displayed.  For	instance, after
     logging in, enter

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

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

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

     instead.

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

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

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

   AAddmmiinniissttrriivviiaa
     If	you've got something to	say, do	so!  We'd like your
     input.  There are various mailing lists available via the
     mailing list server at _m_a_j_o_r_d_o_m_o_@_N_e_t_B_S_D_._o_r_g.  See
	   hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//mmaaiilliinngglliissttss//
     for details.

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

     To	report bugs, use the send-pr(1)	command	shipped	with
     NetBSD, and fill in as much information about the problem as
     you can.  Good bug	reports	include	lots of	details.

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

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

     If	you're interested in doing a serious amount of work on a
     specific port, you	probably should	contact	the `owner' of
     that port (listed below).

     If	you'd like to help with	NetBSD,	and have an idea as to
     how you could be useful, send us mail or subscribe	to:
     _n_e_t_b_s_d_-_u_s_e_r_s_@_N_e_t_B_S_D_._o_r_g.

     As	a favor, please	avoid mailing huge documents or	files to
     these mailing lists.  Instead, put	the material you would
     have sent up for FTP or WWW somewhere, then mail the appro-
     priate list about it.  If you'd rather not	do that, mail the
     list saying you'll	send the data to those who want	it.

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

	       Keith Bostic
	       Ralph Campbell
	       Mike Karels
	       Marshall	Kirk McKusick

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

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

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

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

     ++oo	 The many organizations	that provide NetBSD mirror sites.

     ++oo	 Without CVS, this project would be impossible to manage,
	 so our	hats go	off to Brian Berliner, Jeff Polk, and the
	 various other people who've had a hand	in making CVS a
	 useful	tool.

     ++oo	 We list the individuals and organizations that	have made
	 donations or loans of hardware	and/or money, to support
	 NetBSD	development, and deserve credit	for it at
	       hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ddoonnaattiioonnss//
	 (If you're not	on that	list and should	be, tell us!  We
	 probably were not able	to get in touch	with you, to ver-
	 ify that you wanted to	be listed.)

     ++oo	 Finally, we thank all of the people who've put	sweat and
	 tears into developing NetBSD since its	inception in Jan-
	 uary, 1993.  (Obviously, there	are a lot more people who
	 deserve thanks	here.  If you're one of	them, and would
	 like to be mentioned, tell us!)

   LLeeggaall MMuummbboo--JJuummbboo
     All product names mentioned herein	are trademarks or regis-
     tered trademarks of their respective owners.

     The following notices are required	to satisfy the license
     terms of the software that	we have	mentioned in this docu-
     ment:

     NetBSD is a registered trademark of The NetBSD Foundation,
     Inc.
     This product includes software developed by the University
     of	California, Berkeley and its contributors.
     This product includes software developed by the NetBSD Foun-
     dation.
     This product includes software developed by The NetBSD Foun-
     dation, Inc. and its contributors.
     This product includes software developed for the NetBSD
     Project.  See https://www.NetBSD.org/ for information about
     NetBSD.
     This product includes cryptographic software written by Eric
     Young (eay@cryptsoft.com)
     This product includes cryptographic software written by Eric
     Young (eay@mincom.oz.au)
     This product includes software designed by	William	Allen
     Simpson.
     This product includes software developed at Ludd, University
     of	Luleoa.
     This product includes software developed at Ludd, University
     of	Luleoa, Sweden and its contributors.
     This product includes software developed at the Information
     Technology	Division, US Naval Research Laboratory.
     This product includes software developed by Aaron Brown and
     Harvard University.
     This product includes software developed by Adam Ciarcinski
     for the NetBSD project.
     This product includes software developed by Adam Glass.
     This product includes software developed by Adam Glass and
     Charles M.	 Hannum.
     This product includes software developed by Alex Zepeda.
     This product includes software developed by Alex Zepeda, and
     Colin Wood	for the	NetBSD Project.
     This product includes software developed by Allen Briggs.
     This product includes software developed by Amancio Hasty
     and Roger Hardiman
     This product includes software developed by Berkeley Soft-
     ware Design, Inc.
     This product includes software developed by Bill Paul.
     This product includes software developed by Bodo Moeller.
     This product includes software developed by 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 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 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 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 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 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 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, 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 Pedro Roque Mar-
     ques <pedro_m@yahoo.com>
     This product includes software developed by Per Fogelstrom.
     This product includes software developed by Peter Galbavy.
     This product includes software developed by Phase One, Inc.
     This product includes software developed by Philip	A. Nel-
     son.
     This product includes software developed by QUALCOMM Incor-
     porated.
     This product includes software developed by Ravikanth.
     This product includes software developed by RiscBSD.
     This product includes software developed by Roar Thronaes.
     This product includes software developed by 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 Takashi Hamada.
     This product includes software developed by Takumi	Nakamura.
     This product includes software developed by Tatoku	Ogaito
     for the NetBSD Project.
     This product includes software developed by Tommi Komulainen
     <Tommi.Komulainen@iki.fi>.
     This product includes software developed by TooLs GmbH.
     This product includes software developed by Trimble Naviga-
     tion, Ltd.
     This product includes software developed by Waldi Ravens.
     This product includes software developed by WIDE Project and
     its contributors.
     This product includes software developed by Winning Strate-
     gies, Inc.
     This product includes software developed by Yen Yen Lim and
     North Dakota State	University
     This product includes software developed by Zembu Labs, Inc.
     This product includes software developed by the Alice Group.
     This product includes software developed by the Computer
     Systems Engineering Group at Lawrence Berkeley Laboratory.
     This product includes software developed by the Computer
     Systems Laboratory	at the University of Utah.
     This product includes software developed by the Harvard Uni-
     versity and its contributors.
     This product includes software developed by the Kungliga
     Tekniska Hoegskolan and its contributors.
     This product includes software developed by the Network
     Research Group at Lawrence	Berkeley Laboratory.
     This product includes software developed by the OpenSSL
     Project for use in	the OpenSSL Toolkit.
     (http://www.OpenSSL.org/)
     This product includes software developed by the PocketBSD
     project and its contributors.
     This product includes software developed by the RiscBSD ker-
     nel team
     This product includes software developed by the RiscBSD
     team.
     This product includes software developed by the SMCC Tech-
     nology Development	Group at Sun Microsystems, Inc.
     This product includes software developed by the University
     of	California, Lawrence Berkeley Laboratories.
     This product includes software developed by the University
     of	California, Lawrence Berkeley Laboratory.
     This product includes software developed by the University
     of	California, Lawrence Berkeley Laboratory and its contrib-
     utors.
     This product includes software developed by the University
     of	Vermont	and State Agricultural College and Garrett A.
     Wollman.
     This product includes software developed by the University
     of	Vermont	and State Agricultural College and Garrett A.
     Wollman, by William F.  Jolitz, and by the	University of
     California, Berkeley, Lawrence Berkeley Laboratory, and its
     contributors.
     This product includes software developed by the Urbana-Cham-
     paign Independent Media Center.
     This product includes software developed for the FreeBSD
     project
     This product includes software developed for the NetBSD
     Project by	Allegro	Networks, Inc.,	and Wasabi Systems, Inc.
     This product includes software developed for the NetBSD
     Project by	Bernd Ernesti.
     This product includes software developed for the NetBSD
     Project by	Christopher G. Demetriou.
     This product includes software developed for the NetBSD
     Project by	Eiji Kawauchi.
     This product includes software developed for the NetBSD
     Project by	Genetec	Corporation.
     This product includes software developed for the NetBSD
     Project by	Jason R. Thorpe.
     This product includes software developed for the NetBSD
     Project by	John M.	Vinopal.
     This product includes software developed for the NetBSD
     Project by	Jonathan Stone.
     This product includes software developed for the NetBSD
     Project by	Kyma Systems LLC.
     This product includes software developed for the NetBSD
     Project by	Matthias Drochner.
     This product includes software developed for the NetBSD
     Project by	Perry E. Metzger.
     This product includes software developed for the NetBSD
     Project by	Piermont Information Systems Inc.
     This product includes software developed for the NetBSD
     Project by	Shigeyuki Fukushima.
     This product includes software developed for the NetBSD
     Project by	SUNET, Swedish University Computer Network.
     This product includes software developed for the NetBSD
     Project by	Wasabi Systems,	Inc.
     This product includes software developed or owned by Caldera
     International, Inc.
     This product includes software developed under OpenBSD by
     Per Fogelstrom.
     This product includes software developed under OpenBSD by
     Per Fogelstrom Opsycon AB for RTMX	Inc, North Carolina, USA.
     This software was developed by Holger Veit	and Brian Moore
     for use with "386BSD" and similar operating systems.  "Simi-
     lar operating systems" includes mainly non-profit oriented
     systems for research and education, including but not
     restricted	to "NetBSD", "FreeBSD",	"Mach" (by CMU).
     The Institute of Electrical and Electronics Engineers and
     The Open Group, have given	us permission to reprint portions
     of	their documentation.

     In	the following statement, the phrase ``this text'' refers
     to	portions of the	system documentation.

     Portions of this text are reprinted and reproduced	in
     electronic	form in	NetBSD,	from IEEE Std 1003.1, 2004
     Edition, Standard for Information Technology -- Portable
     Operating System Interface	(POSIX), The Open Group	Base
     Specifications Issue 6, Copyright (C) 2001-2004 by	the
     Institute of Electrical and Electronics Engineers,	Inc and
     The Open Group.  In the event of any discrepancy between
     these versions and	the original IEEE and The Open Group
     Standard, the original IEEE and The Open Group Standard is
     the referee document.

     The original Standard can be obtained online at
     http://www.opengroup.org/unix/online.html.

     This notice shall appear on any product containing	this
     material.

     In	the following statement, "This software" refers	to the
     parallel port driver:
	   This	software is a component	of "386BSD" developed by
	   William F. Jolitz, TeleMuse.

     Some files	have the following copyright:
	   Mach	Operating System
	   Copyright (c) 1991,1990,1989	Carnegie Mellon	Univer-
	   sity
	   All Rights Reserved.

	   Permission to use, copy, modify and distribute this
	   software and	its documentation is hereby granted, pro-
	   vided that both the copyright notice	and this permis-
	   sion	notice appear in all copies of the software, de-
	   rivative works or modified versions,	and any	portions
	   thereof, and	that both notices appear in supporting
	   documentation.

	   CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN
	   ITS CONDITION.  CARNEGIE MELLON DISCLAIMS ANY LIABIL-
	   ITY OF ANY KIND FOR ANY DAMAGES WHATSOEVER RESULTING
	   FROM	THE USE	OF THIS	SOFTWARE.

	   Carnegie Mellon requests users of this software to
	   return to
	   Software Distribution Coordinator  or  Software.Dis-
	   tribution@CS.CMU.EDU
	   School of Computer Science
	   Carnegie Mellon University
	   Pittsburgh PA 15213-3890

	   any improvements or extensions that they make and
	   grant Carnegie the rights to	redistribute these
	   changes.

     Some files	have the following copyright:
	   Copyright (c) 1994, 1995 Carnegie-Mellon University.
	   All rights reserved.

	   Author: Chris G. Demetriou

	   Permission to use, copy, modify and distribute this
	   software and	its documentation is hereby granted, pro-
	   vided that both the copyright notice	and this permis-
	   sion	notice appear in all copies of the software, de-
	   rivative works or modified versions,	and any	portions
	   thereof, and	that both notices appear in supporting
	   documentation.
	   CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN
	   ITS "AS IS" CONDITION.  CARNEGIE MELLON DISCLAIMS ANY
	   LIABILITY OF	ANY KIND FOR ANY DAMAGES WHATSOEVER
	   RESULTING FROM THE USE OF THIS SOFTWARE.

	   Carnegie Mellon requests users of this software to
	   return to
	   Software Distribution Coordinator  or  Software.Dis-
	   tribution@CS.CMU.EDU
	   School of Computer Science
	   Carnegie Mellon University
	   Pittsburgh PA 15213-3890

	   any improvements or extensions that they make and
	   grant Carnegie the rights to	redistribute these
	   changes.

     Some files	have the following copyright:
	   Copyright 1996 The Board of Trustees	of The Leland
	   Stanford Junior University. All Rights Reserved.

	   Permission to use, copy, modify, and	distribute this
	   software and	its documentation for any purpose and
	   without fee is hereby granted, provided that	the above
	   copyright notice appear in all copies.  Stanford Uni-
	   versity makes no representations about the suitability
	   of this software for	any purpose.  It is provided "as
	   is" without express or implied warranty.

   TThhee EEnndd
NetBSD/sparc64 11.99.6		 Jun 07, 2026		NetBSD/sparc64 11.99.6
