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

CCOONNTTEENNTTSS
     About this	Document
     What is NetBSD?
     Changes Between The NetBSD	8 and 9	Releases
	Installation and Partitioning Changes
     Features to be removed in a later release
     The NetBSD	Foundation
     Sources of	NetBSD
     NetBSD 9.4_STABLE Release Contents
	NetBSD/evbarm subdirectory structure
	Binary distribution sets
     NetBSD/evbarm System Requirements and Supported Devices
	32-bit SoCs supported by GENERIC kernels (ARMv7-A)
	64-bit SoCs supported by GENERIC64 kernels
     Getting the NetBSD	System on to Useful Media
     Preparing your System for NetBSD installation
     Installing	the NetBSD System
	Installation for ARMv7 and AArch64 devices with	U-Boot
	Installing NetBSD/evbarm to a SATA hard	disk
     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 9.4_STABLE on the _e_v_b_a_r_m platform.	It is available
     in	four different formats titled _I_N_S_T_A_L_L_._e_x_t, where _._e_x_t is
     one of _._p_s, _._h_t_m_l,	_._m_o_r_e, or _._t_x_t:

	   _._p_s	   PostScript.

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

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

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

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

   WWhhaatt	iiss NNeettBBSSDD??
     The NetBSD	Operating System is a fully functional Open
     Source UNIX-like operating	system derived from the	Univer-
     sity of California, Berkeley Networking Release 2 (Net/2),
     4.4BSD-Lite, and 4.4BSD-Lite2 sources.  NetBSD runs on many
     different different system	architectures (ports) across a
     variety of	distinct CPU families, and is being ported to
     more.  The	NetBSD 9.4_STABLE release contains complete
     binary releases for most of these system architectures, with
     preliminary support for the others	included in source form.
     Please see	the NetBSD _w_e_b_s_i_t_e_: hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg// for
     information on them.

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

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

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

     It	is impossible to completely summarize the massive devel-
     opment that went into the NetBSD 9.4_STABLE 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//nneettbbssdd--99//llaatteesstt//CCHHAANNGGEESS
     _C_H_A_N_G_E_S_-_9_._1_:
	   hhttttppss::////nnyyccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD--ddaaiillyy//nneettbbssdd--99//llaatteesstt//CCHHAANNGGEESS--99..11
     _C_H_A_N_G_E_S_-_9_._2_:
	   hhttttppss::////nnyyccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD--ddaaiillyy//nneettbbssdd--99//llaatteesstt//CCHHAANNGGEESS--99..22
     _C_H_A_N_G_E_S_-_9_._3_:
	   hhttttppss::////nnyyccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD--ddaaiillyy//nneettbbssdd--99//llaatteesstt//CCHHAANNGGEESS--99..33
     _C_H_A_N_G_E_S_-_9_._4_:
	   hhttttppss::////nnyyccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD--ddaaiillyy//nneettbbssdd--99//llaatteesstt//CCHHAANNGGEESS--99..44
     _C_H_A_N_G_E_S_-_9_._5_:
	   hhttttppss::////nnyyccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD--ddaaiillyy//nneettbbssdd--99//llaatteesstt//CCHHAANNGGEESS--99..55
     files in the top level directory of the NetBSD 9.4	release
     tree.

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

     The sysinst installation program has been reworked	for this
     release.

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

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

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

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

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

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

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

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

     CHANGES	   Changes between the 8.0 and 9.0 releases.

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

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

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

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

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

     CHANGES-9.5   Changes after the release of	9.4.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

     The evbarm-specific portion of the	NetBSD 9.4_STABLE release
     is	found in the _e_v_b_a_r_m subdirectory of the	distribution:
     _._._._/_N_e_t_B_S_D_-_9_._4___S_T_A_B_L_E_/_e_v_b_a_r_m_/.  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_/
		   _g_z_i_m_g_/
			    _a_r_m_v_7_._i_m_g_._g_z  A gzipped writable
					  image	containing the
					  complete NetBSD operat-
					  ing system for a range
					  of 32-bit devices
					  (includes a GENERIC
					  kernel).
			    _a_r_m_6_4_._i_m_g_._g_z  A gzipped writable
					  image	containing the
					  complete NetBSD operat-
					  ing system for a range
					  of 64-bit devices
					  (includes a GENERIC64
					  kernel).
			    _r_p_i_._i_m_g_._g_z	  A gzipped writable
					  image	containing the
					  complete 32-bit NetBSD
					  operating system for
					  Raspberry Pi variants
					  only (includes RPI ker-
					  nels).
		   _k_e_r_n_e_l_/
			    _n_e_t_b_s_d_-_G_E_N_E_R_I_C_._g_z
				       A gzipped ARMv7 kernel
				       which supports a	range of
				       32-bit devices that do not
				       need board-specific ker-
				       nels.
			    _n_e_t_b_s_d_-_G_E_N_E_R_I_C_6_4_._g_z
				       A gzipped AArch64 kernel
				       which supports a	range of
				       64-bit devices that do not
				       need board-specific ker-
				       nels.
			    _n_e_t_b_s_d_-_R_P_I_._g_z
				       A gzipped ARMv6 kernel
				       which supports the Rasp-
				       berry Pi	1 only.
			    _n_e_t_b_s_d_-_R_P_I_2_._g_z
				       A gzipped ARMv6 kernel
				       which supports the Rasp-
				       berry Pi	2 only.
			    _*_._d_t_b_._g_z   Gzipped board-specific
				       device trees.
		   _s_e_t_s_/    evbarm 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_/  evbarm kernel modules providing
			      memory disk root file systems for
			      expert usage.
		   _m_i_s_c_/
			      _b_o_o_t_a_a_6_4_._e_f_i
					    AArch64 EFI	boot-
					    loader

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

The NetBSD 9.4_STABLE release for evbarm is comprised of the fol-
lowing binary sets, which can be found in the _e_v_b_a_r_m_/_b_i_n_a_r_y_/_s_e_t_s
subdirectory of	the NetBSD 9.4_STABLE distribution tree:

bbaassee	 The NetBSD 9.4_STABLE evbarm bbaassee binary distribution.
	 You _m_u_s_t install this distribution set.  It contains the
	 base NetBSD utilities that are	necessary for the system
	 to run	and be minimally functional.

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

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

eettcc	 This distribution set contains	the system configuration
	 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/evbarm 9.4_STABLE GENERIC
	 kernel, named _/_n_e_t_b_s_d.	 You _m_u_s_t install this distribu-
	 tion set.

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

mmiisscc	 This set includes the system dictionaries, the	typeset-
	 table 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 functionality to
	 a running system.

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

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

NetBSD maintains its own set of	sources	for the	X Window System
in order to assure tight integration and compatibility.	 These
sources	are based on 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	environ-
	 ment.	This does not include the X servers.

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

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

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

xxeettcc	 Configuration files for X which could be locally modi-
	 fied.

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

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

The instructions given for extracting the source sets work
equally	well for the binary sets, but it is worth noting that if
you use	that method, the filenames stored in the sets are rela-
tive 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 evbarm binary distribution	also has
       its own checksum	files, just as the source distribution
       does.

NNeettBBSSDD//eevvbbaarrmm 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
_3_2_-_b_i_t _S_o_C_s _s_u_p_p_o_r_t_e_d _b_y _G_E_N_E_R_I_C _k_e_r_n_e_l_s _(_A_R_M_v_7_-_A_)

_Q_E_M_U_:
      hhttttppss::////wwiikkii..nneettbbssdd..oorrgg//ppoorrttss//eevvbbaarrmm//qqeemmuu__aarrmm//
is also	supported.
      ++oo	  Allwinner A10, A13, A20, A32,	A80, A83T, H3 (e.g.
	  Cubieboard, OLinuXino, LeMaker Banana	Pi...)
      ++oo	  Amlogic S805 (e.g. ODROID-C1)
      ++oo	  Broadcom BCM2836 (e.g. Raspberry Pi 2)
      ++oo	  Samsung Exynos 5422 (e.g. ODROID-XU3/XU-4)
      ++oo	  Texas	Instruments AM335x and OMAP3 (e.g. BeagleBoard,
	  BeagleBone Black...)
      ++oo	  Xilinx Zynq (e.g. Zedboard, Parallella...)
      ++oo	  NVIDIA Tegra K1

_6_4_-_b_i_t _S_o_C_s _s_u_p_p_o_r_t_e_d _b_y _G_E_N_E_R_I_C_6_4 _k_e_r_n_e_l_s

Devices	conforming to the Server Base System Architecture speci-
fication, and _Q_E_M_U_:
      hhttttppss::////wwiikkii..nneettbbssdd..oorrgg//ppoorrttss//eevvbbaarrmm//qqeemmuu__aarrmm//
are also supported.
      ++oo	  Allwinner H5,	H6, A64	(e.g. PINE64, Pinebook,	NanoPi
	  A64, OLinuXino...)
      ++oo	  Amlogic S905,	S805X, S905D, S905W, S905X (e.g. ODROID-
	  C2, Le Potato, NanoPi	K2...)
      ++oo	  Broadcom BCM2837 (e.g. Raspberry Pi 3)
      ++oo	  Marvell ThunderX
      ++oo	  Rockchip RK3328, RK3328 (e.g.	Pinebook Pro, RockPro64,
	  Firefly...)
      ++oo	  NVIDIA Tegra X1

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
Generally, NetBSD is installed on ARM devices by writing a live
image (armv7.img, or arm64.img for 64-bit devices) to a	SD card
or USB device.	For ARMv6 Raspberry Pi 1s, this	image is
rpi.img.gz.  The storage device	should be at least 2GB.

If you're on Windows rather than a Unix	variant, you can use
_r_a_w_r_i_t_e_3_2_:
      hhttttppss::////wwwwww..nneettbbssdd..oorrgg//~~mmaarrttiinn//rraawwrriittee3322//iinnddeexx..hhttmmll
instead	of dd(1) to write images, and _7_-_Z_i_p_:
hhttttppss::////wwwwww..77--zziipp..oorrgg// to decompress .gz files.

ARM devices generally also ship	with a vendor-specific U-Boot
bootloader, which may be replaced with a board-specific	"main-
line" U-Boot image from	pkgsrc for an optimal NetBSD experience.
The images available from _a_r_m_b_s_d_._o_r_g_:
      hhttttpp::////wwwwww..aarrmmbbssdd..oorrgg//aarrmm//
come pre-prepared with a board-specific	U-Boot image if	one is
available, and otherwise a generic image can be	used.

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
After writing an SD card image,	there are generally no specific
preparation steps needed for ARM.

Once the system	is booted, the init system will	resize the root
partition to take up the entire	disk.  Afterwards, the system can
be configured to your liking.

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
_I_n_s_t_a_l_l_a_t_i_o_n _f_o_r _A_R_M_v_7 _a_n_d _A_A_r_c_h_6_4 _d_e_v_i_c_e_s _w_i_t_h	_U_-_B_o_o_t

      ++oo	  Download or build armv7.img.gz (32-bit) or arm64.img.gz
	  (64-bit).
      ++oo	  Decompress the .gz image, using gunzip(1) on Unix.
      ++oo	  Write	the image to disk:

	  # dd if=armv7.img of=/dev/rld0d bs=1m	conv=sync
      ++oo	  If you are using Microsoft Windows, you can use
	  _r_a_w_r_i_t_e_3_2_:
		hhttttppss::////wwwwww..nneettbbssdd..oorrgg//~~mmaarrttiinn//rraawwrriittee3322//
	  to write SD card images, which can handle decompression
	  too.
      ++oo	  To replace the vendor	U-Boot bootloader with a "main-
	  line"	U-Boot,	obtain a board-specific	image. Bootload-
	  ers are provided by the _s_y_s_u_t_i_l_s_/_u_-_b_o_o_t_-_* packages in
	  _p_k_g_s_r_c_: hhttttppss::////wwwwww..ppkkggssrrcc..oorrgg//.

	  If you're using pkgsrc on an UNIX-like operating system
	  that isn't NetBSD, you must bootstrap	first (see the
	  _R_E_A_D_M_E file in the root directory of pkgsrc).

	  You can also extract the U-Boot image	from u-boot-*.tgz
	  archive in an	existing _N_e_t_B_S_D	_b_i_n_a_r_y _p_a_c_k_a_g_e _s_e_t_:
		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//aaaarrcchh6644//99..00//AAllll//.

	  Install the board-specific U-Boot to the SD card, e.g.
	  for Allwiner devices (PINE H64 in this case):

	  # dd if=/usr/pkg/share/u-boot/pine-h64/u-boot-sunxi-with-spl.bin of=/dev/rld0d bs=1k seek=8 conv=sync

	  Or a Rockchip	device (e.g. RockPro64):

	  # dd if=/usr/pkg/share/u-boot/rockpro64/rksd_loader.img of=/dev/rld0d	seek=64	conv=sync

If you do not want to prepare a	SD card	image manually,	NetBSD
developer Jared	McNeill	provides pre-prepared images on	his web-
site _a_r_m_b_s_d_._o_r_g_:
      hhttttpp::////wwwwww..aarrmmbbssdd..oorrgg//aarrmm//.

_I_n_s_t_a_l_l_i_n_g _N_e_t_B_S_D_/_e_v_b_a_r_m _t_o _a _S_A_T_A _h_a_r_d	_d_i_s_k

Some ARM boards	offer a	SATA interface,	and you	might want to
install	NetBSD to a hard disk after you've got it running from an
SD card.  You can do this using	sysinst(8) from	within NetBSD.

There are instructions for using _s_y_s_i_n_s_t _o_n _A_R_M_:
      hhttttppss::////wwiikkii..nneettbbssdd..oorrgg//ppoorrttss//eevvbbaarrmm//iinnssttaallll__uussiinngg__ssyyssiinnsstt//
on the NetBSD wiki.  The main difference from installing on other
ports is that a	FAT32 partition	is required for	/boot.

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 prop-
erly 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 config-
     uration of	_/_e_t_c_/_r_c_._c_o_n_f (ssyyssiinnsstt normally will), the system
     will drop you into	single user mode on first reboot with the
     message

	   /etc/rc.conf	is not configured. Multiuser boot
	   aborted.

     and with the root file system (_/) mounted read-only.  When
     the system	asks you to choose a shell, simply press RETURN
     to	get to a _/_b_i_n_/_s_h prompt.  If you are asked for a terminal
     type, respond with	vvtt222200 (or whatever is appropriate for
     your terminal type) and press RETURN.  You	may need to type
     one of the	following commands to get your delete key to work
     properly, depending on your keyboard:
	   # 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 proceed.	 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 documentation 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 continue 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_fxp0="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_fxp0="inet myname.my.dom netmask
	   255.255.255.0"

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

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

3.   Logging in

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

4.   Adding accounts

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

5.   The X Window System

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

6.   Installing	third party packages

     If	you wish to install any	of the software	freely available
     for UNIX-like systems you are strongly advised to first
     check the NetBSD package system, pkgsrc.  pkgsrc automati-
     cally handles any changes necessary 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	_e_v_b_a_r_m_/_9_._4___S_T_A_B_L_E_/_A_l_l subdir.  If you
	 installed pkgin(1) in the ssyyssiinnsstt post-installation con-
	 figuration 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 correctly con-
	 figured, you can install them with the	following com-
	 mands:

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

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

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

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

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

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

7.   Misc

     ++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 evbarm 9.4_STABLE is by
using the sysutils/sysupgrade package from pkgsrc.

First, edit _/_u_s_r_/_p_k_g_/_e_t_c_/_s_y_s_u_p_g_r_a_d_e_._c_o_n_f.  Make	sure RELEASEDIR
and ARCHIVE_EXTENSION are correct:

# Replace evbarm-aarch64 with evbarm-earmv7hf on a 32-bit system, evbarm-earmv6hf on the original RPI
RELEASEDIR="https://cdn.netbsd.org/pub/NetBSD/NetBSD-9.4_STABLE/evbarm-aarch64/"
ARCHIVE_EXTENSION=tar.xz

Make sure _/_b_o_o_t	is mounted, and	copy the new board-specific _*_._d_t_s
device tree file into place.  Note that	the device tree	files are
sorted into SoC-type subdirectories in _/_b_o_o_t_/_d_t_b, e.g. allwinner,
amlogic, broadcom, freescale, nvidia, rockchip.

For example, for the Allwinner-based PINE A64 LTS:

$ ftp https://cdn.netbsd.org/pub/NetBSD/NetBSD-9.4_STABLE/evbarm-aarch64/binary/kernel/sun50i-a64-pine64-lts.dtb.gz
$ gunzip sun50i-a64-pine64-lts.dtb.gz
# cp sun50i-a64-pine64-lts.dtb /boot/dtb/allwinner/
Also copy _b_o_o_t_a_a_6_4_._e_f_i if applicable:

$ ftp https://cdn.netbsd.org/pub/NetBSD/NetBSD-9.4_STABLE/evbarm-aarch64/installation/misc/bootaa64.efi
# cp bootaa64.efi /boot/EFI/BOOT/bootaa64.efi

Finally:

# sysupgrade fetch
# sysupgrade kernel
# sysupgrade modules
# reboot
# sysupgrade sets
# sysupgrade etcupdate
# sysupgrade postinstall
# reboot

This is	the most careful possible path with sysupgrade that makes
sure the kernel	and userland are always	fully compatible, by mak-
ing sure the kernel and	boot files are newer than the userland.
It is also possible to:

# sysupgrade auto
# reboot

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

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

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

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

UUssiinngg oonnlliinnee NNeettBBSSDD ddooccuummeennttaattiioonn
Documentation is available if you installed the	manual distribu-
tion set.  Traditionally, the ``man pages'' (documentation) 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 categories, but
three are of primary interest: user commands are in section 1,
file formats are in section 5, and administrative information is
in section 8.

The _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 numbered 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 documenta-
tion 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	possibly
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 interface 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 spe-
cific 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	appropriate 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	encouragement.

++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 host-
    ing	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 prob-
    ably were not able to get in touch with you, to verify 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	January,
    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 registered
trademarks of their respective owners.

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

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 Founda-
tion.
This product includes software developed by The	NetBSD Founda-
tion, 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 Tech-
nology Division, US Naval Research Laboratory.
This product includes software developed by Aaron Brown	and Har-
vard University.
This product includes software developed by Adam Ciarcinski for
the NetBSD project.
This product includes software developed by Adam Glass.
This product includes software developed by Adam Glass and
Charles	M.  Hannum.
This product includes software developed by Alex Zepeda.
This product includes software developed by Alex Zepeda, and
Colin Wood for the NetBSD Projet.
This product includes software developed by Allen Briggs.
This product includes software developed by Amancio Hasty and
Roger Hardiman
This product includes software developed by Ben	Gray.
This product includes software developed by Berkeley Software
Design,	Inc.
This product includes software developed by Bill Paul.
This product includes software developed by Boris Popov.
This product includes software developed by Brini.
This product includes software developed by Bruce M. Simpson.
This product includes software developed by Causality Limited.
This product includes software developed by Charles Hannum.
This product includes software developed by Charles M. Hannum.
This product includes software developed by Charles M. Hannum, by
the University of Vermont and State Agricultural College and Gar-
rett A.	 Wollman, by William F.	Jolitz,	and by the University of
California, Berkeley, Lawrence Berkeley	Laboratory, and	its con-
tributors.
This product includes software developed by Christian E. Hopps.
This product includes software developed by Christian E. Hopps,
Ezra Story, Kari Mettinen, Markus Wild,	Lutz Vieweg and	Michael
Teske.
This product includes software developed by Christopher	G.
Demetriou.
This product includes software developed by Christopher	G.
Demetriou for the NetBSD Project.
This product includes software developed by Chuck Silvers.
This product includes software developed by Cisco Systems, Inc.
This product includes software developed by Colin Wood.
This product includes software developed by Colin Wood for the
NetBSD Project.
This product includes software developed by Computing Services at
Carnegie Mellon	University (http://www.cmu.edu/computing/).
This product includes software developed by Daan Vreeken.
This product includes software developed by Daishi Kato
This product includes software developed by Daniel Widenfalk and
Michael	L. Hitch.
This product includes software developed by Daniel Widenfalk for
the NetBSD Project.
This product includes software developed by David Jones	and Gor-
don 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@min-
com.oz.au)
This product includes software developed by Ezra Story.
This product includes software developed by Ezra Story and by
Kari Mettinen.
This product includes software developed by Ezra Story,	by Kari
Mettinen and by	Bernd Ernesti.
This product includes software developed by Ezra Story,	by Kari
Mettinen, and Michael Teske.
This product includes software developed by Ezra Story,	by Kari
Mettinen, Michael Teske	and by Bernd Ernesti.
This product includes software developed by Frank van der Linden
for the	NetBSD Project.
This product includes software developed by Gardner Buchanan.
This product includes software developed by Garrett D'Amore.
This product includes software developed by Gary Thomas.
This product includes software developed by Gordon Ross
This product includes software developed by Harvard University.
This product includes software developed by Harvard University
and its	contributors.
This product includes software developed by Hellmuth Michaelis
and Joerg Wunsch
This product includes software developed by Henrik Vestergaard
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 Corporation and
its contributors.
This product includes software developed by Internet Initiative
Japan Inc.
This product includes software developed by Internet Research
Institute, Inc.
This product includes software developed by James R. Maynard III.
This product includes software developed by Jared D. McNeill.
This product includes software developed by Jason L. Wright
This product includes software developed by Jason R. Thorpe for
And Communications, http://www.and.com/
This product includes software developed by Joachim Koenig-
Baltes.
This product includes software developed by Jochen Pohl	for The
NetBSD Project.
This product includes software developed by Joerg Wunsch
This product includes software developed by John Birrell.
This product includes software developed by John P. Wittkoski.
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 Highfield.
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 Cal-
ifornia, Berkeley and its contributors.
This product includes software developed by Kyma Systems.
This product includes software developed by Leo	Weppelman and
Waldi Ravens.
This product includes software developed by Lloyd Parkes.
This product includes software developed by Lutz Vieweg.
This product includes software developed by Marc Horowitz.
This product includes software developed by Marcus Comstedt.
This product includes software developed by Mark Brinicombe.
This product includes software developed by Mark Brinicombe for
the NetBSD Project.
This product includes software developed by Mark Tinguely and Jim
Lowe
This product includes software developed by Markus Wild.
This product includes software developed by Marshall M.	Midden.
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 Fredette.
This product includes software developed by Michael Smith.
This product includes software developed by Microsoft
This product includes software developed by Mika Kortelainen
This product includes software developed by Mike Pritchard.
This product includes software developed by Mike Pritchard and
contributors.
This product includes software developed by Minoura Makoto.
This product includes software developed by MINOURA Makoto,
Takuya Harakawa.
This product includes software developed by Niels Provos.
This product includes software developed by Niklas Hallqvist.
This product includes software developed by Niklas Hallqvist,
Brandon	Creighton and Job de Haas.
This product includes software developed by Paolo Abeni.
This product includes software developed by Paul Kranenburg.
This product includes software developed by Paul Mackerras.
This product includes software developed by Paul Mackerras
<paulus@samba.org>.
This product includes software developed by Pedro Roque	Marques
<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. Nelson.
This product includes software developed by QUALCOMM Incorpo-
rated.
This product includes software developed by RiscBSD.
This product includes software developed by Roar Thronaes.
This product includes software developed by Rodney W. Grimes.
This product includes software developed by Roger Hardiman
This product includes software developed by Rolf Grossmann.
This product includes software developed by Ross Harvey.
This product includes software developed by Ross Harvey	for the
NetBSD Project.
This product includes software developed by Scott Bartram.
This product includes software developed by Scott Stevens.
This product includes software developed by Shingo WATANABE.
This product includes software developed by Softweyr LLC, the
University of California, Berkeley, and	its contributors.
This product includes software developed by Stephan Thesing.
This product includes software developed by Steven M. Bellovin
This product includes software developed by Takashi Hamada.
This product includes software developed by Takumi Nakamura.
This product includes software developed by Tatoku Ogaito for the
NetBSD Project.
This product includes software developed by Tommi Komulainen
<Tommi.Komulainen@iki.fi>.
This product includes software developed by TooLs GmbH.
This product includes software developed by Trimble Navigation,
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 Strategies,
Inc.
This product includes software developed by Yasushi Yamasaki
This product includes software developed by Yen	Yen Lim	and North
Dakota State University
This product includes software developed by Zembu Labs,	Inc.
This product includes software developed by the	Alice Group.
This product includes software developed by the	Computer Systems
Engineering Group at Lawrence Berkeley Laboratory.
This product includes software developed by the	Computer Systems
Laboratory at the University of	Utah.
This product includes software developed by the	Harvard	Univer-
sity 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	kernel
team
This product includes software developed by the	RiscBSD	team.
This product includes software developed by the	SMCC Technology
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 contributors.
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, Berke-
ley, Lawrence Berkeley Laboratory, and its contributors.
This product includes software developed by the	Urbana-Champaign
Independent Media Center.
This product includes software developed for the FreeBSD project
This product includes software developed for the NetBSD	Project
by Allegro Networks, Inc., and Wasabi Systems, Inc.
This product includes software developed for the NetBSD	Project
by Bernd Ernesti.
This product includes software developed for the NetBSD	Project
by Christopher G. Demetriou.
This product includes software developed for the NetBSD	Project
by Eiji	Kawauchi.
This product includes software developed for the NetBSD	Project
by Frank van der Linden
This product includes software developed for the NetBSD	Project
by Genetec Corporation.
This product includes software developed for the NetBSD	Project
by Jason R. Thorpe.
This product includes software developed for the NetBSD	Project
by John	M. Vinopal.
This product includes software developed for the NetBSD	Project
by Jonathan Stone.
This product includes software developed for the NetBSD	Project
by Kyma	Systems	LLC.
This product includes software developed for the NetBSD	Project
by Matthias Drochner.
This product includes software developed for the NetBSD	Project
by Perry E. Metzger.
This product includes software developed for the NetBSD	Project
by Piermont Information	Systems	Inc.
This product includes software developed for the NetBSD	Project
by Shigeyuki Fukushima.
This product includes software developed for the NetBSD	Project
by SUNET, Swedish University Computer Network.
This product includes software developed for the NetBSD	Project
by Wasabi Systems, Inc.
This product includes software developed or owned by Caldera
International, Inc.
This product includes software developed under OpenBSD by Per
Fogelstrom.
This product includes software developed under OpenBSD by Per
Fogelstrom Opsycon AB for RTMX Inc, North Carolina, USA.
This software was developed by Holger Veit and Brian Moore for
use with "386BSD" and similar operating	systems.  "Similar oper-
ating 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 University
      All Rights Reserved.

      Permission to use, copy, modify and distribute this soft-
      ware and its documentation is hereby granted, provided that
      both the copyright notice	and this permission notice appear
      in all copies of the software, derivative	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	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.Distribu-
      tion@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 soft-
      ware and its documentation is hereby granted, provided that
      both the copyright notice	and this permission notice appear
      in all copies of the software, derivative	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.Distribu-
      tion@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 soft-
      ware and its documentation for any purpose and without fee
      is hereby	granted, provided that the above copyright notice
      appear in	all copies.  Stanford University makes no repre-
      sentations 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/evbarm 9.4_STABLE	Feb 18,	202604	      NetBSD/evbarm 9.4_STABLE
