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

CCOONNTTEENNTTSS
     About this	Document
     What is NetBSD?
     Changes Between The NetBSD	10 and 11 Releases
     Features to be removed in a later release
     The NetBSD	Foundation
     Sources of	NetBSD
     NetBSD 11.0_RC2 Release Contents
	NetBSD/hp300 subdirectory structure
	Binary distribution sets
     NetBSD/hp300 System Requirements and Supported Devices
	Supported hardware
	Unsupported hardware
     Getting the NetBSD	System on to Useful Media
     Preparing your System for NetBSD installation
	Formatting your	hard drives
	Designing your disk's partition	table
	Installing the bootstrap program locally
	Installing the miniroot	file system locally
	Configuring the	netboot	server
	Put Series 400 systems in HP-UX	Compatible Boot	Mode
	Searching for a	bootable system
	Selecting ethernet port	on Series 400
	Running	SYS_INST
	Choosing a kernel location
     Installing	the NetBSD System
     Post installation steps
     Upgrading a previously-installed NetBSD System
	Upgrading using	the miniroot
	Manual upgrade
     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.0_RC2 on	the _h_p_3_0_0 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 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.0_RC2 release contains complete binary releases
     for most of these system architectures, with preliminary
     support for the others included in	source form.  For more
     information please	visit hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//.

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

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

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

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

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

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

     If	you are	upgrading from a version of NetBSD-current please
     also check	the _C_o_m_p_a_t_i_b_i_l_i_t_y _I_s_s_u_e_s _W_i_t_h _P_r_e_v_i_o_u_s _N_e_t_B_S_D
     _R_e_l_e_a_s_e_s.	It is impossible to completely summarize the mas-
     sive development that went	into the NetBSD	11.0_RC2 release.
     The complete list of changes can be found in
     _C_H_A_N_G_E_S_:
	   hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD//NNeettBBSSDD--1111..00__RRCC22//CCHHAANNGGEESS
     _C_H_A_N_G_E_S_-_1_1_._0_:
	   hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD//NNeettBBSSDD--1111..00__RRCC22//CCHHAANNGGEESS--1111..00
     which are also present in the top level directory of the
     NetBSD 11.0 release tree.

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

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

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

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

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

   NNeettBBSSDD 1111..00__RRCC22 RReelleeaassee CCoonntteennttss
     The root directory	of the NetBSD 11.0_RC2 release is orga-
     nized as follows:

     _._._._/_N_e_t_B_S_D_-_1_1_._0___R_C_2_/

     CHANGES	   Changes between the 10.0 and	11.0 releases.

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

     CHANGES.prev  Changes in previous NetBSD releases.

     LAST_MINUTE   Last	minute changes and notes about the
		   release.

     README.files  README describing the distribution's	contents.

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

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

     In	addition to the	files and directories listed above, there
     is	one directory per architecture,	for each of the	architec-
     tures for which NetBSD 11.0_RC2 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.0_RC2
	       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.0_RC2	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_/_h_p_3_0_0 _s_u_b_d_i_r_e_c_t_o_r_y _s_t_r_u_c_t_u_r_e

     The hp300-specific	portion	of the NetBSD 11.0_RC2 release is
     found in the _h_p_3_0_0	subdirectory of	the distribution:
     _._._._/_N_e_t_B_S_D_-_1_1_._0___R_C_2_/_h_p_3_0_0_/.  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-
				       thing supported in this
				       release.
			    _n_e_t_b_s_d_-_R_A_M_D_I_S_K_._g_z
				       A gzipped NetBSD	kernel
				       containing code for all of
				       the hardware supported in
				       this release with an
				       embedded	ramdisk-based
				       installer.  This	is the
				       same kernel that	is
				       present on the miniroot
				       filesystem, but uses a
				       newer more user-friendly
				       installation program.
			    _n_e_t_b_s_d_-_R_A_M_D_I_S_K_._s_y_m_b_o_l_s_._g_z
				       Symbols for
				       _n_e_t_b_s_d_-_R_A_M_D_I_S_K_._g_z.
		   _s_e_t_s_/    hp300 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_/  hp300 miniroot file system image;
			      see below.
		   _m_i_s_c_/      Miscellaneous hp300 installation
			      utilities; see installation section
			      below.

			      _H_P_-_I_B_._g_e_o_m_e_t_r_y  A	file containing
					      geometry for some
					      HB-IB disk drives.

			      _S_Y_S___I_N_S_T_._g_z     A	gzipped	copy of
					      the SYS_INST mini-
					      root installation
					      program.	This is
					      only necessary if
					      you can't	use the
					      RAMDISK based
					      installer.

			      _S_Y_S___U_B_O_O_T_._g_z    A	gzipped	copy of
					      the universal boot
					      block.  Supports
					      Network, tape and
					      disk booting.  This
					      is useful	if you
					      are installing a
					      diskless
					      NetBSD/hp300 sys-
					      tem.

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

     The NetBSD	hp300 binary distribution sets contain the bina-
     ries which	comprise the NetBSD 11.0_RC2 release for hp300.
     The binary	distribution sets can be found in the
     _h_p_3_0_0_/_b_i_n_a_r_y_/_s_e_t_s subdirectory of the NetBSD 11.0_RC2 dis-
     tribution tree, and are as	follows:

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

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

     ddeebbuugg    This distribution	set contains debug information
	      for all base system utilities.  It is useful when
	      reporting	issues with binaries or	during 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/hp300 11.0_RC2	GENERIC
	      kernel, named _/_n_e_t_b_s_d.  You _m_u_s_t install this dis-
	      tribution	set.

     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.

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

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

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

   NNeettBBSSDD//hhpp330000	SSyysstteemm RReeqquuiirreemmeennttss aanndd	SSuuppppoorrtteedd DDeevviicceess
     NetBSD/hp300 11.0_RC2 will	run on most HP 9000/300- and
     400-series	machines.  The smallest	amount of RAM that has
     been tested is 4 MB.  If you wish to run X, more RAM is rec-
     ommended.

     _S_u_p_p_o_r_t_e_d _h_a_r_d_w_a_r_e

	   ++oo   CPUs
	       --   318 (16 MHz 68020, with built-in monochrome
		   framebuffer,	no expansion)
	       --   319 (16 MHz 68020, with built-in 6 bit color
		   framebuffer,	no expansion)
	       --   320 (16 MHz 68020, 16 KB L2 cache, up to 7.5
		   MB RAM)
		   _R_e_q_u_i_r_e_s _H_u_m_a_n _I_n_t_e_r_f_a_c_e _b_o_a_r_d
	       --   330 (16 MHz 68020, 4	MB on motherboard, up to
		   8 MB	RAM)
		   _R_e_q_u_i_r_e_s _H_u_m_a_n _I_n_t_e_r_f_a_c_e _b_o_a_r_d
	       --   332 (16 MHz 68030, optional 68882, up to 8 MB
		   RAM)
	       --   340 (16 MHz 68030, up to 16 MB RAM)
	       --   345 (50 MHz 68030 with 32 KB	L2 cache, up to
		   128 MB RAM, built-in	SCSI)
	       --   350 (25 MHz 68020, 32 KB L2 cache, up to 48 MB
		   RAM)
		   _R_e_q_u_i_r_e_s _H_u_m_a_n _I_n_t_e_r_f_a_c_e _b_o_a_r_d
	       --   360 (25 MHz 68030, with 4 MB	RAM built-in, up
		   to 16 MB RAM)
		   _R_e_q_u_i_r_e_s _S_y_s_t_e_m _I_n_t_e_r_f_a_c_e _b_o_a_r_d
	       --   362 (25 MHz 68030, up to 16 MB RAM, built-in
		   SCSI)
	       --   370 (33 MHz 68030, 64 KB L2 cache, up to 48 MB
		   RAM)
		   _R_e_q_u_i_r_e_s _S_y_s_t_e_m _I_n_t_e_r_f_a_c_e _b_o_a_r_d
	       --   375 (50 MHz 68030 with 32 KB	L2 cache, up to
		   128 MB RAM, built-in	SCSI)
	       --   380 (25 MHz 68040, up to 128	MB RAM,	built-in
		   SCSI)
	       --   382 (25 MHz 68040, up to 32 MB RAM, built-in
		   SCSI)
	       --   385 (33 MHz 68040, up to 128	MB RAM,	built-in
		   SCSI)
	       --   400s, 400t, 400dl (50 MHz 68030 with	32 KB L2
		   cache, built-in SCSI, up to 128 MB RAM)
	       --   425s, 425t, 425dl (25 MHz 68040 with	built-in
		   SCSI, up to 128 MB RAM)
	       --   425e	(25 MHz	68040, built-in	SCSI)
		   _T_h_e _B_o_o_t_R_O_M _d_o_e_s _n_o_t	_s_u_p_p_o_r_t	_s_e_r_i_a_l _c_o_n_s_o_l_e_.
		   _T_h_e NetBSD/hp300 _b_o_o_t_l_o_a_d_e_r _a_n_d _k_e_r_n_e_l _w_i_l_l
		   _u_s_e _t_h_e _s_e_r_i_a_l _p_o_r_t _f_o_r _c_o_n_s_o_l_e _i_f
		   `SERVICE/NORMAL' _s_w_i_t_c_h _o_n _t_h_e _b_a_c_k _p_a_n_e_l _i_s
		   _t_u_r_n_e_d _t_o `SERVICE' _p_o_s_i_t_i_o_n_.
	       --   433s, 433t, 433dl (33 MHz 68040 with	built-in
		   SCSI, up to 128 MB RAM)

	   ++oo   HP-IB devices
	       --   _r_d; CS80 disks: 2200, 2202, 2203, 7908, 7911,
		   7912, 7914, 7933, 7936, 7937, 7941, 7945,
		   7946, 7957, 7958, and 7959
		   _E_m_u_l_a_t_e_d _C_S_8_0 _d_i_s_k_s _b_y _H_P_D_i_s_k_:
			 hhttttpp::////wwwwww..ddaallttoonn..aaxx//hhppddiisskk//
		   _a_n_d _H_P_D_r_i_v_e_:
			 hhttttppss::////wwwwww..hhpp99884455..nneett//99884455//pprroojjeeccttss//hhppddrriivvee//
		   _a_l_s_o	_w_o_r_k_.
	       --   _r_d; CS80 floppy disks: 9122,	9134 (possibly
		   others)
		   _R_e_q_u_i_r_e_s _u_s_e	_o_f _H_P_-_U_X _L_I_F _u_t_i_l_i_t_i_e_s _v_i_a _H_P_-_U_X
		   _e_m_u_l_a_t_i_o_n
	       --   _c_t; CS80 Low-density	16 track cartridge (67
		   MB):	7912, 7914, 7946, and 9144
		   _C_a_n_n_o_t _r_e_a_d _o_r _w_r_i_t_e	_t_o _3_2 _t_r_a_c_k _t_a_p_e_s
	       --   _c_t; CS80 High-density 32 track cartridge (134
		   MB):	9145
		   _C_a_n_n_o_t _w_r_i_t_e	_t_o _1_6 _t_r_a_c_k _t_a_p_e_s _(_r_e_a_d	_o_n_l_y_)
	       --   _m_t; CS80 Half-inch tape: 7974A, 7978A/B,
		   7979A, 7980A, and 7980XC.

		   _N_o_t_e_:  You should connect HP-IB tape	drives
			  and printers to the slow HP-IB inter-
			  face and hard	drives to the fast HP-IB
			  interface (if	present).

	   ++oo   SCSI devices
	       --   _s_d; SCSI hard drives
	       --   _c_d; SCSI CD-ROM drives
	       --   _s_d; SCSI Magneto-optical drives
	       --   _s_t; SCSI tape drives: HP 35450A (DDS-1 DAT),
		   Exabyte EXB-8200 (8mm), Archive (QIC-24), Ar-
		   chive Viper (QIC-60), Archive Viper (QIC-150),
		   Archive Python 25501	(DAT), and Archive Python
		   28849 (DAT)
	       --   _c_h; SCSI autochangers

	   ++oo   Serial interfaces
	       --   _c_o_m;	Built-in single	serial port on System
		   Interface board and Human Interface board
	       --   _c_o_m;	Built-in Apollo	4-port on Series 400
		   workstations
	       --   _d_c_m;	98638 8-port (DIO-II board, appears to
		   kernel as two 98642 devices)
	       --   _d_c_m;	98642 4-port (DIO-I board)
	       --   _c_o_m;	98626, 98644 built-in or add-on	(DIO-I
		   board) single serial	port

	       _N_o_t_e_:  See the FAQ for more detailed specs and
		      information on configuring:
			    hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//hhpp330000//ffaaqq..hhttmmll##sseerriiaalliinnffoo

	   ++oo   Network interfaces
	       --   _l_e; 98643 built-in and add-on (DIO-I	board)
		   ethernet cards.

	   ++oo   Graphics	Devices
	       --   98542 monochrome Topcat (512x400, 1 bit, DIO-
		   II)
	       --   98543 color Topcat (512x400,	4 bits,	DIO-II)
	       --   98544 monochrome Topcat (1024x768, 1	bit, DIO-
		   II)
	       --   98545A color	Topcat (1024x768, 4 bits, DIO-II)
	       --   98547 color Topcat (1024x768, 6 bits)
	       --   98548A monochrome Catseye (1024x768,	1 bit)
	       --   98549A color	Catseye	(1024x768, 6 bits)
	       --   98550A Catseye Hi-Res Color (a.k.a. CH)
		   (1280x1024 @	60 Hz, 8 bits, DIO-II)
	       --   98700 and 98710 Gatorbox (1280x1024 @ 60 Hz,	4
		   or 8	bits)
		   _R_e_q_u_i_r_e_s _9_8_2_8_7 _(_D_I_O_-_I _b_o_a_r_d_)	_t_o _c_o_n_n_e_c_t _t_o
		   _w_o_r_k_s_t_a_t_i_o_n
	       --   98720 and 98721 color Renaissance SRX
		   (1280x1024 @	60 Hz, 8, 12 or	24 bits)
		   _R_e_q_u_i_r_e_s _9_8_7_2_4 _(_D_I_O_-_I _b_o_a_r_d_)	_o_r _9_8_7_2_5 _(_D_I_O_-_I_I
		   _b_o_a_r_d_) _t_o _c_o_n_n_e_c_t _t_o	_w_o_r_k_s_t_a_t_i_o_n
	       --   98730 and 98731 DaVinci TurboSRX (1280x1024 @
		   60 Hz, 8, 16, or 24 bits)
		   _R_e_q_u_i_r_e_s _9_8_7_2_6_A _(_D_I_O_-_I_I _b_o_a_r_d_) _t_o _c_o_n_n_e_c_t _t_o
		   _w_o_r_k_s_t_a_t_i_o_n
	       --   A1096A monochrome Hyperion (1280x1024, 1 bit)
	       --   A1416A Kathmandu (a.k.a. Color VRX) (1280x1024
		   @ 60	hz, 8 bits, DIO-II)
	       --   A1659A CRX (1280x1024 @ 72 hz, 8 bits, SGC)
	       --   98705 Tigershark PersonalVRX	DIO-II graphics
		   device
		   _U_n_t_e_s_t_e_d
	       --   362 and 382 built-in	EVRX framebuffer
	       --   425e	built-in EVRX framebuffer

	   ++oo   HP-HIL devices
	       --   Keyboards
	       --   Two and three button	mice
	       --   Three button	trackballs (M1309A)
	       --   46094 Quadrature Port (supports normal serial
		   mice)
	       --   Graphics tablets
	       --   Dial	boxes
	       --   ID modules

	   ++oo   Miscellaneous boards/interfaces
	       --   98265A/98652	SCSI interface (DIO-I board,
		   daughtercard	for 98562, or built-in)
	       --   98561 Human Interface board (DIO-I board with
		   serial port,	HP-HIL,	and HP-IB)
	       --   98562 System	Interface board	(DIO-II	board
		   with	serial port, HP-HIL, HP-IB, DMA, and eth-
		   ernet, has optional fast HP-IB or SCSI daugh-
		   terboard)
	       --   98620 DMA card (DIO-I board,	for use	with
		   98561)
	       --   98624 HP-IB interface (DIO-I	board or built-
		   in)
	       --   98625A and 98625B 'fast' HP-IB interface (DIO-
		   I board or daughtercard for 98562)
	       --   Apollo Domain keyboard and mouse on Series 400
		   workstations
	       --   ``ARCOFI'' audio device on 425e

     Each serial interface has its own quirks, and some	of them
     use non-standard pins.  The FAQ describes how to configure
     and connect serial	consoles to hp300 systems.
	   hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//hhpp330000//ffaaqq..hhttmmll##sseerriiaallccoonnssoollee

     When you try booting from a system	with a framebuffer that
     is	not supported by NetBSD/hp300, the screen will turn
     black, and	it will	try using the serial port for the con-
     sole.

     _U_n_s_u_p_p_o_r_t_e_d _h_a_r_d_w_a_r_e

	   ++oo   CPUs
	       --   310 (10 MHz 68010, with built-in monochrome
		   framebuffer,	rs232 (25 pin),	hil, and slow
		   hpib)

	   ++oo   Graphics	Devices
	       --   98702 TurboVRX DIO-II graphics device

	   ++oo   Miscellaneous boards/interfaces
	       --   parallel port, on 345, 362, 375, 380, 382,
		   385,	and Series 400 workstations
	       --   EISA	support, on Series 400 workstations
	       --   Token Ring cards (a.k.a. ATR)
	       --   VME bus adapter, on Series 300 workstations
	       --   98628A single port dcl (DIO-I board)
	       --   98625C fast HP-IB option on models 345 and 375

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

     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.

     _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
			       _h_p_3_0_0_/_b_i_n_a_r_y_/_s_e_t_s.  (You	only need
			       to know this if you are mixing
			       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..00__RRCC22
				     # ccdd hhpp330000//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
     There are two installation	tools available.  The traditional
     miniroot installer	is script-based	and may	be netbooted or
     may be dumped to a	disk and run locally.  The ramdisk kernel
     with the ssyyssiinnsstt installation utility is more flexible, but
     can only be netbooted and has not been extensively	tested.

     There are several possible	installation configurations
     described in this document.  Other	configurations are possi-
     ble, but less common.  If you are unable to install based on
     the information in	this document, post a message to
     _p_o_r_t_-_h_p_3_0_0_@_N_e_t_B_S_D_._o_r_g asking for help.  The configurations
     described in this document	are as follows:

     ++oo	 hp300 netboots	SYS_UBOOT from a NetBSD	server running
	 rbootd(8), or other server platforms (Linux, FreeBSD,
	 SunOS,	Solaris, HP-UX etc.) with YAMAMORI Takenori's
	 sun-rbootd package and	then runs the miniroot installa-
	 tion tools or a purely	diskless installation from a
	 server	on the same subnet (you	must have root access).
	 For more information, refer to	the NetBSD Diskless HOW-
	 TO 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//nneettwwoorrkk//nneettbboooott//
	 and
	       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//rrbboooottdd//

     ++oo	 hp300 loads SYS_UBOOT from a local disk, tape,	or floppy
	 and then runs the miniroot installation tools or a
	 purely	diskless installation from a server as described
	 above.	 You will need HP-UX on	your hp300 if it does not
	 have a	SCSI interface or a floppy drive.

     ++oo	 hp300 loads SYS_INST from a local disk.  You partition
	 the drive and then run	the miniroot installation tools
	 from that drive.  You will need HP-UX on your hp300 if
	 it does not have a SCSI interface.
     The preferred method is to	use another NetBSD server to net-
     boot the hp300 client.  This procedure will not work on the
     handful of	models which are incapable of netbooting.  In
     particular, the 320, 350, 330, 318, and 319 might not have	a
     recent enough BootROM.  The BootROM revision is printed when
     your workstation is first powered on (or rebooted).  Revi-
     sion B or later will definitely work.  BootROMs with numeric
     revisions such as 1.1 (on a 400s) will netboot without any
     problems.	You can	netboot	from any built-in or add-on eth-
     ernet board on a model with a supported BootROM.

     If	you have access	to a NetBSD/hp300 system, it is	_m_u_c_h eas-
     ier to simply upgrade than	to install from	scratch.  Skip
     down to the section on _U_p_g_r_a_d_i_n_g _a	_p_r_e_v_i_o_u_s_l_y_-_i_n_s_t_a_l_l_e_d
     _N_e_t_B_S_D _S_y_s_t_e_m

     _F_o_r_m_a_t_t_i_n_g	_y_o_u_r _h_a_r_d _d_r_i_v_e_s

     NetBSD/hp300 does not have	the capability to perform a low-
     level format of hard drives.  SCSI	disks can be formatted on
     any platform with SCSI support and	then used on
     NetBSD/hp300.  HP-IB disks	can only be formatted by the
     HP-UX mediainit(1)	command.  You may need to first	create
     the device	nodes for your disk, as	HP-UX was never	very good
     about populating _/_d_e_v_/_r_d_s_k	properly.

	   # mmkknnoodd //ddeevv//ddsskk//IIDDss00 bb 00 00xxSSCCIIDD0000
	   # mmkknnoodd //ddeevv//rrddsskk//IIDDss00 cc 44 00xxSSCCIIDD0000
	   # mmeeddiiaaiinniitt --vv //ddeevv//rrddsskk//IIDDss00

     _I_D	is the HP-IB address (a.k.a. slave) of the disk	in hexa-
     decimal.  This is usually between 00 and 07, but possibly up
     to	1F (31 decimal)	.

     _S_C	is the Select Code of the disk controller.  This is usu-
     ally 07 for slow (i.e. built-in) HP-IB or 0E (14 decimal)
     for SCSI or fast HP-IB.

     _D_e_s_i_g_n_i_n_g _y_o_u_r _d_i_s_k_'_s _p_a_r_t_i_t_i_o_n _t_a_b_l_e

     This step can sometimes be	a real pain, especially	when
     using _S_Y_S___I_N_S_T.  It's best	to calculate it	ahead of time.

     If	you are	installing to an HP-IB disk, you will need infor-
     mation about your disk's geometry,	based on 512-byte sec-
     tors.  The	file _i_n_s_t_a_l_l_a_t_i_o_n_/_m_i_s_c_/_H_P_-_I_B_._g_e_o_m_e_t_r_y in the dis-
     tribution has geometry information	for several HP-IB disks,
     but may be	incomplete.  Geometry may be calculated	from an
     HP-UX _/_e_t_c_/_d_i_s_k_t_a_b	entry, but note	that HP-UX geometry is
     based on 1024 byte	sectors, while NetBSD's	is based on 512
     byte sectors.  You	should have all	partitions start on
     cylinder boundaries.

     If	you are	installing to a	SCSI disk, you don't need to
     worry about the details of	the geometry.  Just create a
     disklabel based on	the total number of sectors available on
     the disk.

     _A _q_u_i_c_k _n_o_t_e _a_b_o_u_t	_p_a_r_t_i_t_i_o_n_s_: Since the target disk will
     become the	boot disk for your new NetBSD/hp300 installation,
     you will need to treat the	`a' and	`c' partitions in a spe-
     cial manner.  Due to the size of the NetBSD/hp300 boot pro-
     gram (it spills into the area after the disklabel), it is
     necessary to offset the beginning of the `a' partition.  For
     HP-IB disks, it is	best to	offset it by one cylinder from
     the beginning of the disk.	 For SCSI disks, just offset it
     by	100 KB (200 sectors).  Later, the `c' partition	will be
     marked with the type `boot' and may not be	used for a file
     system.  (For those unfamiliar with historic BSD partition
     conventions, the `c' partition is defined as the `entire
     disk', or the `raw	partition'.)

     _N_o_t_e_:  You	will need at least a 6 MB swap partition
	    (although 2-3*RAM is recommended) if you are unable
	    to netboot the installer, as the miniroot is tempo-
	    rarily placed in this partition.

     Here is an	example	disklabel from a 7959B HP-IB hard drive:

	   # /dev/rrd0a:
	   type: HP-IB
	   disk: rd7959B
	   label:
	   flags:
	   bytes/sector: 512
	   sectors/track: 42
	   tracks/cylinder: 9
	   sectors/cylinder: 378
	   cylinders: 1572
	   total sectors: 594216
	   rpm:	3600
	   interleave: 1
	   trackskew: 0
	   cylinderskew: 0
	   headswitch: 0	   # milliseconds
	   track-to-track seek:	0  # milliseconds
	   drivedata: 0

	   8 partitions:
	   #	    size   offset    fstype   [fsize bsize   cpg]
	     a:	   37800      378    4.2BSD	1024  8192    16   #
	     b:	   66150    38178      swap	1024  8192    16   #
	     c:	  594216	0      boot			   # (Cyl.    0	- 1571)
	     d:	  489888   104328    4.2BSD	1024  8192    16   #

     _I_n_s_t_a_l_l_i_n_g	_t_h_e _b_o_o_t_s_t_r_a_p _p_r_o_g_r_a_m _l_o_c_a_l_l_y

     For earlier models	incapable of netbooting, you need to
     install the bootstrap program on a	bootable local device,
     such as a hard disk, floppy disk, or tape drive.  If you
     will be booting the miniroot over the network, then you will
     be	installing _i_n_s_t_a_l_l_a_t_i_o_n_/_m_i_s_c_/_S_Y_S___U_B_O_O_T.

     If	you do not have	access to a netboot server to serve the
     miniroot installer, you can use a primitive bootstrap pro-
     gram _i_n_s_t_a_l_l_a_t_i_o_n_/_m_i_s_c_/_S_Y_S___I_N_S_T to	load the miniroot from a
     locally attached device (such as a	disk, tape or CD-R).
     This is not recommended, as _S_Y_S___I_N_S_T is difficult to use,
     buggy, and	provides no error checking when	partitioning your
     disk.

     If	your system has	SCSI, this is easy.  Just take a scratch
     SCSI disk (hard disk, zip disk, or	CD-R) and use any com-
     puter to dump the bootstrap program to it.	 For example, to
     dump it to	the sd1	disk on	a non-i386 platform:

	   # dddd	iiff==SSYYSS__UUBBOOOOTT ooff==//ddeevv//ssdd11cc

     If	your system has	a floppy drive,	you can	write the boot-
     strap program to it using any computer with a floppy drive.
     You will need to dump it using a utility like rraawwrriittee or
     dd(1).  Make sure to read back from the floppy to verify
     that the file has been written correctly.

     If	your system does not have SCSI or a floppy drive, you
     will need a bootable operating system on your hp300 so you
     can write files to	the HP-IB device.  You should probably
     write the bootstrap program to the	disk you will be
     installing	NetBSD onto.

     Using HP-UX to write to an	HP-IB disk:

	   # dddd	iiff==SSYYSS__UUBBOOOOTT ooff==//ddeevv//rrddsskk//IIDDss00

     _I_D	is the HP-IB address (a.k.a. slave) of the disk	in hexa-
     decimal.  This is usually between 00 and 07, but possibly up
     to	1F (31 decimal)	.

     Using HP-UX to write to an	HP-IB tape:

	   # dddd	iiff==SSYYSS__UUBBOOOOTT ooff==//ddeevv//rrmmtt//00mmnnbb oobbss==2200bb ccoonnvv==oossyynncc

     _I_n_s_t_a_l_l_i_n_g	_t_h_e _m_i_n_i_r_o_o_t _f_i_l_e _s_y_s_t_e_m _l_o_c_a_l_l_y

     This step is only necessary if you	are not	loading	the mini-
     root installer from a netboot server.  Follow the same pro-
     cedure for	the bootstrap program, except use the uncom-
     pressed miniroot file system
     (_i_n_s_t_a_l_l_a_t_i_o_n_/_m_i_n_i_r_o_o_t_/_m_i_n_i_r_o_o_t_._f_s_._g_z ) instead of	the boot-
     strap program.  The only quirk is that you	should place it
     at	the offset of the swap partition you calculated	above in
     the disklabel.  In	the example disklabel above, the offset
     is	38178 sectors of 512 bytes.  Therefore,	the dd(1) command
     would be something	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//IIDDss00 sseeeekk==3388117788bb
     Note the `b' after	the offset, which specifies blocks of 512
     bytes.

     By	dumping	the miniroot to	disk where the swap partition
     will be, you're saving a step later where _S_Y_S___I_N_S_T	tries to
     download the miniroot over	NFS.  Just make	sure that when
     you enter the partition table into	_S_Y_S___I_N_S_T you use the same
     block offset for the swap partition as you	dumped the mini-
     root.

     _C_o_n_f_i_g_u_r_i_n_g _t_h_e _n_e_t_b_o_o_t _s_e_r_v_e_r

     This step will configure your netboot server to provide
     _S_Y_S___U_B_O_O_T and the miniroot	installer to your hp300.

     1.	  Introduction

	  To netboot a hp300, you must configure one or	more
	  servers to provide information and files to your hp300
	  (the `client').  If you are using NetBSD (any	architec-
	  ture)	on your	netboot	server(s), the information pro-
	  vided	here should be sufficient to configure every-
	  thing.  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 supported	hp300
	  systems use HP's proprietary RMP (the	rbootd(8) daemon)
	  for the first	discovery stage	and bootstrap download
	  stages.  The bootstrap program uses DHCP for its dis-
	  covery stage.	 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.	  rbootd(8)

	  Get _S_Y_S___U_B_O_O_T	from the _i_n_s_t_a_l_l_a_t_i_o_n_/_m_i_s_c directory of
	  the distribution.

		# mmkkddiirr	--pp //uussrr//mmddeecc//rrbboooottdd
		# ccpp SSYYSS__UUBBOOOOTT //uussrr//mmddeecc//rrbboooottdd
		# cchhmmoodd	--RR aa++rrXX	//uussrr//mmddeecc//rrbboooottdd

	  Create _/_e_t_c_/_r_b_o_o_t_d_._c_o_n_f with the following line:

		CC:CC:CC:CC:CC:CC SYS_UBOOT

	  You will need	to start the rrbboooottdd.  If it's already
	  running, you will need to restart it to force	it to re-
	  read its configuration file.	If the server is running
	  NetBSD, you can achieve this with:

		# //eettcc//rrcc..dd//rrbboooottdd rreessttaarrtt

	  If your netboot server is not	running	NetBSD but other
	  OSs (like Linux, Solaris etc.), you have to use
	  YAMAMORI Takenori's sun-rbootd package instead of
	  native rbootd(8).  Please refer the "Setting up the
	  rbootd server" section in the	_N_e_t_B_S_D _D_i_s_k_l_e_s_s	_H_O_W_-_T_O_:
		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//rrbboooottdd//
	  for details.

     3.	  dhcpd(8)

	  The bootstrap	program	uses DHCP to discover the loca-
	  tion of the kernel.  Put the following lines in your
	  _/_e_t_c_/_d_h_c_p_d_._c_o_n_f (see dhcpd.conf(5) and dhcp-options(5)
	  for more information):

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

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

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

     5.	  NetBSD kernel	and installation tools

	  Now, if you place a kernel named _n_e_t_b_s_d in
	  _/_e_x_p_o_r_t_/_c_l_i_e_n_t_/_r_o_o_t your client should boot the kernel.
	  If you are netbooting	the installer, you can use either
	  the traditional miniroot-based installer
	  _i_n_s_t_a_l_l_a_t_i_o_n_/_m_i_n_i_r_o_o_t_/_m_i_n_i_r_o_o_t_._f_s_._g_z or the experimen-
	  tal RAM disk-based installer
	  _b_i_n_a_r_y_/_k_e_r_n_e_l_/_n_e_t_b_s_d_-_R_A_M_D_I_S_K_._g_z.

	  To use the miniroot-based installer, mount the miniroot
	  file system on your netboot server.  This procedure
	  does _n_o_t work	on any operating system	other than
	  NetBSD.  You'll also need to either set up a new NFS
	  share	point or an FTP	server for the distribution
	  files, as they won't fit inside the miniroot file sys-
	  tem.

		# gguunnzziipp mmiinniirroooott..ffss..ggzz
		# vvnnccoonnffiigg --cc //ddeevv//vvnndd00cc //ppaatthh//ttoo//mmiinniirroooott..ffss
		# mmoouunntt	--oo rroo //ddeevv//vvnndd00cc //eexxppoorrtt//cclliieenntt//rroooott
		# llss //eexxppoorrtt//cclliieenntt//rroooott
		 .profile     dist/	   install.md	mnt/	     sbin/	  usr/
		 bin/	      etc/	   install.sub	mnt2/	     tmp/	  var/
		 dev/	      install*	   kern/	netbsd*	     upgrade*

	  If there are no files	present	in your	exported direc-
	  tory,	then something is wrong.

	  To use the RAM disk-based installer, uncompress and
	  rename the kernel.  Also, copy the distribution files
	  to the client's root directory.

		# ccpp **..ttggzz //eexxppoorrtt//cclliieenntt//rroooott
		# gguunnzziipp nneettbbssdd--RRAAMMDDIISSKK..ggzz
		# mmvv nneettbbssdd--RRAAMMDDIISSKK //eexxppoorrtt//cclliieenntt//rroooott//nneettbbssdd

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

     6.	  Client file system

	  You can skip this step if you	do not plan to run your
	  client diskless after	installation.  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

     7.	  Setting up the server	daemons

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

		rbootd=YES	 rbootd_flags=""
		dhcpd=YES	 dhcpd_flags="-q"
		nfs_server=YES	       # enable	server daemons
		mountd=YES
		rpcbind=YES	 rpcbind_flags="-l"   #	-l logs	libwrap

     _P_u_t _S_e_r_i_e_s	_4_0_0 _s_y_s_t_e_m_s _i_n _H_P_-_U_X _C_o_m_p_a_t_i_b_l_e	_B_o_o_t _M_o_d_e

     Series 400	systems	can be configured to boot either HP-UX or
     DomainOS.	To boot	NetBSD/hp300 you must have your	system
     configured	in `HP-UX Compatible Boot Mode'.  If, when you
     power on your machine, it does _n_o_t	present	a menu like the
     following,	then you need to change	your configuration.

	   Copyright 1990,
	   Hewlett-Packard Company.
	   All Rights Reserved.

	   BOOTROM  Series 400	Rev. 1.1
	   MD12	REV 1.2	1990/08/07.14:27:08
	   [...]

     1.	  Attach a Domain keyboard or an HIL keyboard.
	  The BootROM knows how	to use either, even if NetBSD
	  doesn't yet.

     2.	  Put your system into `service	mode'.
	  For a	4XXs, there's a	toggle switch on the back of the
	  machine (near	the top).  For a 4XXt or 4XXdl,	press the
	  green	button on the front, behind the	silly door.  For
	  a 425e, there's a toggle switch on the back of the
	  machine (in the middle).  The	second green LED should
	  light	up.

     3.	  Reset	the machine.
	  Press	the reset button.  For a 4XXs, there's a small
	  plunger on the back of the machine (near the top).  For
	  a 4XXt or 4XXdl, there's a white button on the front,
	  behind the silly door.  For a	425e, there's a	button on
	  the back of the machine.

     4.	  Press	RETURN to get the Domain boot prompt (>	).
	  You can type H to get	a list of available commands.

     5.	  Type the following sequence of commands to convert to
	  `HP-UX Compatible Boot Mode'.

		> CCFF
		Type [key] RETURN ? 22
		Type [key] RETURN ? 22
		Type T or P  RETURN ? PP
		Type [key] RETURN ? EE

     6.	  Be sure to turn `service mode' _o_f_f when you're done.
	  It may prevent you from selecting which device to boot
	  from.
     See the FAQ for additional	help.
	   hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//hhpp330000//ffaaqq..hhttmmll##ddoommaaiinn

     _S_e_a_r_c_h_i_n_g _f_o_r _a _b_o_o_t_a_b_l_e _s_y_s_t_e_m

     All the early hp300 Boot ROMs are very primitive and only
     allow a few simple	operations.  You can only interact with
     it	after it is first powered on.  If you reboot the machine,
     it	will ignore anything you type and start	loading	the same
     OS	you previously booted.

     At	any time after it recognizes the keyboard, while it is
     doing its self test or searching for a bootable system, you
     can hit reset to return it	to a cold-boot configuration.  On
     HIL keyboards, this is control-shift-break, where break is
     the key in	the upper left (where escape is	on sane	key-
     boards).  There is	no equivalent over serial terminal,
     you'll need to power-cycle	your machine.

     After it beeps (i.e. recognizes the HIL keyboard),	press
     RETURN twice to get the list of bootable devices.

	   SEARCHING FOR A SYSTEM (RETURN To Pause)

     The newer HP Boot ROM, present on Series 400 machines and
     some of the later 300s (345, 375, 380, 382, 385) is capable
     of	a little bit more.  To select which device to boot from,
     press RETURN once after it	beeps twice (i.e. recognizes the
     HIL keyboard) to get the list of bootable devices.

	   RESET To Power-Up, SPACE clears input   Select System, type RETURN	    ?

     The FAQ lists additional things you can do	with the BootROM
     and describes the order the BootROM looks for bootable
     devices.
	   hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//hhpp330000//ffaaqq..hhttmmll

     A normal power-on sequence	(from a	400s) looks something
     like this:

	   Copyright 1990,
	   Hewlett-Packard Company.
	   All Rights Reserved.

	   BOOTROM  Series 400	Rev. 1.1
	   MD12	REV 1.2	1990/08/07.14:27:08
	   MC68030 Processor
	   MC68882 Coprocessor
	   Configuration EEPROM
	   Utility Chip	at 41
	   HP-HIL.Keyboard
	    RESET To Power-Up
	    Loading Memory
	   Self-Test Mode
	    RESET To Power-Up, SPACE clears input
	   Select System, type RETURN
	   HP-IB
	   DMA-C0
	    Self-Test Mode
	   RAM 33554158	Bytes
	   HP98644 (RS-232) at 9
	   HP PARALLEL at 12
	   HP98265 (SCSI S 32) at 14
	   HP98643 (LAN) at 21,	AUI, 080009115DB3
	   Bit Mapped Video at 133 (Console)
	    System Search Mode
						   :RODIME RO3000T, 1406, 0
						      1Z SYS_UBOOT
						   :LAN080009115DB3, 2100, 0
						      2Z SYS_UBOOT
						   :HP7959, 702, 0, 0
						      1H SYSHPUX
						      1D SYSDEBUG
						      1B SYSBCKUP
						   :HP9122, 0700, 0, 0
						      3Z SYS_INST

     You should	see your bootstrap program somewhere in	this
     list.  If it's not	here, then your	hp300 can't boot it and
     there's a problem somewhere.  To boot from	a particular
     device, type in the two character name for	it and press
     RETURN.  In this example, you'd type 2Z to	boot from the
     network.

     _S_e_l_e_c_t_i_n_g _e_t_h_e_r_n_e_t	_p_o_r_t _o_n	_S_e_r_i_e_s _4_0_0

     Series 400	machines have two ethernet media types built into
     the motherboard.  You may only use	one at a time.	When your
     Series 400	workstation goes through the self-test when pow-
     ered on or	rebooted, it will say one of the following:

	   HP98643 (LAN) at 21,	AUI
	   HP98643 (LAN) at 21,	Thin

     If	the wrong type of network is selected, you will	need to
     change the	ethernet port.	You will need to open the case
     (4XXt, 4XXdl, 4XXe) or remove the motherboard (4XXs) to
     access the	jumper.	 Be sure to use	static-prevention mea-
     sures, as you could easily	fry your motherboard from care-
     lessness.	If you are uncomfortable with this, ask	a friend
     who is aware of these issues.  There is a block of	8 jumpers
     at	the rear of the	motherboard, labeled AUI/Thin.	You will
     need to put the jumpers in	the position necessary for your
     type of ethernet.

     _R_u_n_n_i_n_g _S_Y_S___I_N_S_T

     This step is necessary _o_n_l_y if you	cannot netboot.

     Chose SYS_INST from the list of bootable devices that the
     BootROM found.  SYS_INST will load	and prompt you for a com-
     mand.

     _A _q_u_i_c_k _n_o_t_e _a_b_o_u_t	_d_i_s_k _n_u_m_b_e_r_s_: While in the _S_Y_S___I_N_S_T pro-
     gram, you may use different unit numbers for the disks than
     when the NetBSD kernel is running.	 The unit number for a
     disk while	in _S_Y_S___I_N_S_T is calculated with the following for-
     mula:

	   unit	= (controller *	8) + slaveID

     Controllers are numbered 0, 1, ...	starting with the lowest
     select code.  SCSI	controllers and	HP-IB controllers are
     counted separately.  Therefore, if	you had	a system with an
     internal HP-IB interface at select	code 7,	a fast HP-IB
     interface at select code 14, and a	SCSI interface at select
     code 16, unit numbers might be something like the following:

	   LLooccaattiioonn		     UUnniitt
	   HP-IB at 7, slaveID 2     2	     (disk: rd2)
	   HP-IB at 14,	slaveID	5    13	     (disk: rd13)
	   SCSI	at 16, slaveID 0     0	     (disk: sd0)

     You will need to place a disklabel	on the disk.

	   sys_inst> ddiisskkllaabbeell

     _N_o_t_e_:  It may be worth selecting the zzaapp option initially to
	    ensure that	the disklabel area is clear.  This may be
	    especially important if an HP-UX boot block	had been
	    previously installed on the	disk.

     Select the	eeddiitt option, and answer	the questions about your
     disk.  There may be several questions which you may not be
     sure of the answers to.  Listed below are guidelines for
     SCSI and HP-IB disks:

	   Bad sectoring?	NO
	   Ecc?			NO
	   Interleave?		1
	   Trackskew?		0
	   Cylinderskew?	0
	   Headswitch?		0
	   Track-to-track?	0
	   Drivedata 0-4?	0 (for all Drivedata values)

     Next, you will be asked to	fill out the partition map.  You
     must provide responses for	all 8 partitions.  Remember, you
     must have the sector offset for the `b' partition match the
     location you dumped the miniroot file system image.  Set the
     size and offset of	any unused partition to	0.  Note that
     sizes and offsets are expressed in	`n sectors', assuming 512
     byte sectors.  Care should	be taken to ensure that	parti-
     tions begin and end on cylinder boundaries	(i.e. size and
     offset is an even multiple	of the number of sectors per
     cylinder).	 While this is not technically necessary, it is
     generally encouraged.

     _N_o_t_e_:  When setting the partition type of the `b' partition,
	    make sure to specify it as an ffs partition	so that
	    the	miniroot can be	mounted	(even if this will be a
	    swap partition).  You will be given	a chance to clean
	    this up later in the installation process.

     Once you have edited the label, select the	sshhooww option to
     verify that it is correct.	 If so,	select wwrriittee and ddoonnee.
     Otherwise,	you may	re-edit	the label.

     In	an earlier step, we already copied the miniroot	image to
     the target	disk.

     Boot from the miniroot file system.

	   sys_inst> bboooott

     Enter the disk from which to boot.	 The kernel in the mini-
     root file system will be booted into single-user mode.

     _C_h_o_o_s_i_n_g _a	_k_e_r_n_e_l _l_o_c_a_t_i_o_n

     Once the bootstrap	program	SYS_UBOOT has started, it will
     pause and let you chose a kernel location,	name, and
     options:

	   >> NetBSD/hp300 Primary Boot, Revision 1.13
	   >> (gregm@mcgarry, Mon Apr 15 08:46:32 NZST 2002)
	   >> HP 9000/425e SPU
	   >> Enter "reset" to reset system.
	   Boot: [[[le0a:]netbsd][-a][-c][-d][-s][-v][-q]] :-

     If	your kernel is on a different device than SYS_UBOOT then
     you will need to type in where to find it.	 This is the
     case, for example,	if your	model is incapable of netbooting
     and you started SYS_UBOOT from a floppy, and the miniroot
     installer is on a netboot server.	In this	case, you'd type
     in	`le0' at the prompt.

     If	you've installed the miniroot on your disk, you	can
     always boot from that by using partition `b' when prompted
     by	SYS_UBOOT.  For	example, to boot the miniroot from an HP-
     IB	disk on	controller 0 at	slave ID 2, you'd type:

	   Boot: [[[rd0a:]netbsd][-a][-c][-d][-s][-v][-q]] :-  rrdd22bb::nneettbbssdd

   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
     The miniroot's install program is very simple to use.  It
     will guide	you through the	entire process,	and is well auto-
     mated.  If	you need to restart the	installer, hit Control-C
     which will	return you to a	shell prompt.  From there, just
     start it over:

	   # ..//iinnssttaallll

     The experimental RAM disk-based installer is not described
     here, but is very self-explanatory.

     The miniroot's install program will:

     1.	  Allow	you to place disklabels	on additional disks.
	  Note that partition sizes and	offsets	are expressed in
	  sectors.  When you fill out the disklabel, you will
	  need to specify partition types and file system parame-
	  ters.	 If you're unsure what these values should be,
	  use the following:

		fstype:	4.2BSD
		fsize: 1024
		bsize: 4096
		cpg: 16

	  If the partition will	be a swap partition, use the fol-
	  lowing:

		fstype:	swap
		fsize: 0 (or blank)
		bsize: 0 (or blank)
		cpg: 0 (or blank)

	  You will also	need to	specify	the number of partitions.
	  The number of	partitions is determined by the	`index'
	  of the last partition	letter,	where a	= 1, b = 2, etc.
	  Therefore, if	the last filled	partition is partition
	  `g', there are 7 partitions.	Any partitions with size
	  of 0 may be removed from the list.

	  Anything after a `#' is a comment.

	  The following	is an example disklabel	partition map:

		7 partitions:
		#      size   offset	fstype	 [fsize	bsize	cpg]
		a:    30912	 448	4.2BSD	   1024	 8192	 16   #	(Cyl.	 1 - 69)
		b:   130816    31360	  swap			      #	(Cyl.	70 - 361)
		c:  1296512	   0	  boot			      #	(Cyl.	 0 - 2893)
		e:    81984   162176	4.2BSD	   1024	 8192	 16   #	(Cyl.  362 - 544)
		f:   102592   244160	4.2BSD	   1024	 4096	 16   #	(Cyl.  545 - 773)
		g:   949760   346752	4.2BSD	   1024	 8192	 16   #	(Cyl.  774 - 2893)

     2.	  Create file systems on target	partitions.

     3.	  Allow	you to set up your system's network configura-
	  tion.	 Remember to specify host names	without	the
	  domain name appended to the end.  For	example	use foo
	  instead of foo.bar.org.  If, during the process of con-
	  figuring the network interfaces, you make a mistake,
	  you will be able to re-configure that	interface by sim-
	  ply selecting	it for configuration again.

     4.	  Mount	target file systems.  You will be given	the
	  opportunity to manually edit the resulting _/_e_t_c_/_f_s_t_a_b.

     5.	  Extract binary sets from the media of	your choice.

     6.	  Copy configuration information gathered during the
	  installation process to your root file system	(_/).

     7.	  Make device nodes in your root file system under _/_d_e_v.

     8.	  Copy a new kernel onto your root partition (_/).

     9.	  Install a new	boot block.

     10.  Check	your file systems for integrity.

     First-time	installation on	a system through a method other
     than the installation program is possible,	but strongly dis-
     couraged.

   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 hhpp330000hh for a
	  local	console, or whatever is	appropriate for	your
	  serial console.  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 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_le0="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_le0="inet myname.my.dom netmask
		255.255.255.0"

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

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

     3.	  Logging in

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

     4.	  Adding accounts

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

     5.	  The X	Window System

	  If you installed the X Window	System,	you may	want to
	  read the chapter about X in the _N_e_t_B_S_D _G_u_i_d_e_:
		hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ddooccss//gguuiiddee//eenn//cchhaapp--xx..hhttmmll:
	  Also,	you may	want to	read through the NetBSD/hp300 _F_A_Q
	  _e_n_t_r_y	_o_n _X_1_1_:
		hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ppoorrttss//hhpp330000//ffaaqq..hhttmmll##xx1111.

     6.	  Installing third-party packages

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

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

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

	  ++oo   Precompiled binaries can be found	at
		    hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//ppkkggssrrcc//ppaacckkaaggeess//NNeettBBSSDD//
	      usually in the _h_p_3_0_0_/_1_1_._0___R_C_2_/_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.

     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
     It	is possible to easily upgrade your existing NetBSD/hp300
     system using the upgrade program in the miniroot or by manu-
     ally performing the same steps as the miniroot upgrade pro-
     gram.

     _U_p_g_r_a_d_i_n_g _u_s_i_n_g _t_h_e _m_i_n_i_r_o_o_t

     If	you wish to upgrade your system	by this	method,	simply
     select the	uuppggrraaddee	option once the	miniroot has booted.  The
     upgrade program with then guide you through the procedure.
     While you can boot	the miniroot using the same methods
     described above for a fresh install of NetBSD/hp300 there
     are easier	and less intrusive options since your disk is
     already labeled and bootable.  The	easiest	is to dump the
     miniroot to your swap partition and boot from that.

     1.	  Download the files you'll need to upgrade

	  In particular, make sure you have on your locally
	  mounted file systems _b_a_s_e_._t_g_z	and _m_i_n_i_r_o_o_t_._f_s_._g_z

     2.	  Boot your hp300 into `single-user mode':

	  Follow the instructions in the section above on
	  _C_h_o_o_s_i_n_g _a _k_e_r_n_e_l _l_o_c_a_t_i_o_n and type -s at the	prompt.

     3.	  Extract and install a	new boot block:

	  Make sure you	install	the bootstrap program distributed
	  with this version of NetBSD/hp300.

		# ttaarr --xxppvvzzff bbaassee..ttggzz ..//uussrr//mmddeecc
		# ddiisskkllaabbeell --BB --bb ..//uussrr//mmddeecc//uubboooott..lliiff	_r_o_o_t_-_d_i_s_k
	  E.g.:	_r_o_o_t_-_d_i_s_k could	be sd0 or rd0.	We'll assume rd0
	  for now.

     4.	  Install the miniroot file system:

	  First	make sure that your `b'	partition has enough room
	  for the uncompressed miniroot	(otherwise it might over-
	  write	another	partition or the end of	the disk).

		# 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d00bb

     5.	  Boot the miniroot:

	  Follow the instructions in the section above on
	  _C_h_o_o_s_i_n_g _a _k_e_r_n_e_l _l_o_c_a_t_i_o_n and type rd0b:netbsd at the
	  prompt.

     The upgrade program will:

     1.	  Enable the network based on your system's current net-
	  work configuration.

     2.	  Mount	your existing file systems.

     3.	  Extract binary sets from the media of	your choice.

     4.	  Fixup	your system's existing _/_e_t_c_/_f_s_t_a_b, changing the
	  occurrences of uuffss to	ffffss and	let you	edit the result-
	  ing file.

     5.	  Make new device nodes	in your	root file system under
	  _/_d_e_v.

     6.	  Don't	forget to extract the kkeerrnn set from the	distribu-
	  tion.

	  _N_o_t_e_:	 The existing kernel _w_i_l_l _n_o_t be backed	up; doing
		 so would be pointless,	since older kernels may
		 not be	capable	of running NetBSD 11.0_RC2
		 executables.

     7.	  Install a new	boot block.

     8.	  Check	your file systems for integrity.

     9.	  You'll have to reboot	your system manually

     _M_a_n_u_a_l _u_p_g_r_a_d_e

     While using the miniroot's	upgrade	program	is the preferred
     method of upgrading your system, it is possible to	upgrade
     your system manually.  To do this,	follow the following pro-
     cedure:

     1.	  Place	_a_t _l_e_a_s_t the bbaassee binary set in	a file system
	  accessible to	the target machine.  A local file system
	  is preferred,	since the NFS subsystem	in the
	  NetBSD 11.0_RC2 kernel may be	incompatible with your
	  old binaries.

     2.	  Back up your pre-existing kernel and copy the	11.0_RC2
	  kernel into your root	partition (_/).

     3.	  Extract and install a	new boot block:

	  Make sure you	install	the bootstrap program distributed
	  with this version of NetBSD/hp300.

		# ttaarr --xxppvvzzff bbaassee..ttggzz ..//uussrr//mmddeecc
		# ddiisskkllaabbeell --BB --bb ..//uussrr//mmddeecc//uubboooott..lliiff	_r_o_o_t_-_d_i_s_k
	  E.g.:	_r_o_o_t_-_d_i_s_k could	be sd0 or rd0.

     4.	  Reboot with the 11.0_RC2 kernel into single-user mode.

     5.	  Check	all file systems:

		# //ssbbiinn//ffsscckk --ppff

     6.	  Mount	all local file systems:

		# //ssbbiinn//mmoouunntt --aa --tt nnoonnffss

     7.	  If you keep _/_u_s_r or _/_u_s_r_/_s_h_a_r_e on an NFS server, you
	  will want to mount those file	systems	as well.  To do
	  this,	you will need to enable	the network:

		# sshh //eettcc//rrcc..dd//nneettwwoorrkk ssttaarrtt

     8.	  Make sure you	are in the root	file system (_/)	and
	  extract the bbaassee binary set:

		# ccdd //
		# ppaaxx --zzrrvvppee --ff	_/_p_a_t_h_/_t_o_/bbaassee..ttggzz

     9.	  Sync the file	systems:

		# ssyynncc

     10.  At this point	you may	extract	any other binary sets you
	  may have placed on local file	systems, or you	may wish
	  to extract additional	sets at	a later	time.  To extract
	  these	sets, use the following	commands:

		# ccdd //
		# ppaaxx --zzrrvvppee --ff	_p_a_t_h___t_o___s_e_t

     _N_o_t_e_:  You	_s_h_o_u_l_d _n_o_t extract the eettcc set if upgrading.
	    Instead, you should	extract	that set into another
	    area and carefully merge the changes by hand.

   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.0_RC2.

     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.0_RC2 release.	See the	``Components removed from
     NetBSD'' section near the beginning of this document for a
     list.

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

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

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

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

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

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

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

     instead.

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

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

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

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

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

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

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

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

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

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

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

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

	       Keith Bostic
	       Ralph Campbell
	       Mike Karels
	       Marshall	Kirk McKusick

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

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

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

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

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

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

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

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

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

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

     NetBSD is a registered trademark of The NetBSD Foundation,
     Inc.
     This product includes software developed by the University
     of	California, Berkeley and its contributors.
     This product includes software developed by the NetBSD Foun-
     dation.
     This product includes software developed by The NetBSD Foun-
     dation, Inc. and its contributors.
     This product includes software developed for the NetBSD
     Project.  See https://www.NetBSD.org/ for information about
     NetBSD.
     This product includes cryptographic software written by Eric
     Young (eay@cryptsoft.com)
     This product includes cryptographic software written by Eric
     Young (eay@mincom.oz.au)
     This product includes software designed by	William	Allen
     Simpson.
     This product includes software developed at Ludd, University
     of	Luleoa.
     This product includes software developed at Ludd, University
     of	Luleoa, Sweden and its contributors.
     This product includes software developed at the Information
     Technology	Division, US Naval Research Laboratory.
     This product includes software developed by Aaron Brown and
     Harvard University.
     This product includes software developed by Adam Ciarcinski
     for the NetBSD project.
     This product includes software developed by Adam Glass.
     This product includes software developed by Adam Glass and
     Charles M.	 Hannum.
     This product includes software developed by Alex Zepeda.
     This product includes software developed by Alex Zepeda, and
     Colin Wood	for the	NetBSD Project.
     This product includes software developed by Allen Briggs.
     This product includes software developed by Amancio Hasty
     and Roger Hardiman
     This product includes software developed by Ben Gray.
     This product includes software developed by Berkeley Soft-
     ware Design, Inc.
     This product includes software developed by Bill Paul.
     This product includes software developed by Bodo Moeller.
     This product includes software developed by Boris Popov.
     This product includes software developed by Brini.
     This product includes software developed by Bruce M. Simp-
     son.
     This product includes software developed by Causality Lim-
     ited.
     This product includes software developed by Charles Hannum.
     This product includes software developed by Charles M. Han-
     num.
     This product includes software developed by Charles M. Han-
     num, by the University of Vermont and State Agricultural
     College and Garrett A.  Wollman, by William F. Jolitz, and
     by	the University of California, Berkeley,	Lawrence Berkeley
     Laboratory, and its contributors.
     This product includes software developed by Christian E.
     Hopps.
     This product includes software developed by Christian E.
     Hopps, Ezra Story,	Kari Mettinen, Markus Wild, Lutz Vieweg
     and Michael Teske.
     This product includes software developed by Christopher G.
     Demetriou.
     This product includes software developed by Christopher G.
     Demetriou for the NetBSD Project.
     This product includes software developed by Chuck Silvers.
     This product includes software developed by Cisco Systems,
     Inc.
     This product includes software developed by Colin Wood.
     This product includes software developed by Colin Wood for
     the NetBSD	Project.
     This product includes software developed by Computing Ser-
     vices at Carnegie Mellon University (http://www.cmu.edu/com-
     puting/).
     This product includes software developed by Daan Vreeken.
     This product includes software developed by Daishi	Kato
     This product includes software developed by Daniel	Widenfalk
     and Michael L. Hitch.
     This product includes software developed by Daniel	Widenfalk
     for the NetBSD Project.
     This product includes software developed by David Jones and
     Gordon Ross
     This product includes software developed by David Miller.
     This product includes software developed by Dean Huxley.
     This product includes software developed by Emmanuel Dreyfus
     This product includes software developed by Eric S. Hvozda.
     This product includes software developed by Eric S. Raymond
     This product includes software developed by Eric Young
     (eay@cryptsoft.com)
     This product includes software developed by Eric Young
     (eay@mincom.oz.au)
     This product includes software developed by Ezra Story.
     This product includes software developed by Ezra Story and
     by	Kari Mettinen.
     This product includes software developed by Ezra Story, by
     Kari Mettinen and by Bernd	Ernesti.
     This product includes software developed by Ezra Story, by
     Kari Mettinen, and	Michael	Teske.
     This product includes software developed by Ezra Story, by
     Kari Mettinen, Michael Teske and by Bernd Ernesti.
     This product includes software developed by Frank van der
     Linden for	the NetBSD Project.
     This product includes software developed by Gardner
     Buchanan.
     This product includes software developed by Garrett D'Amore.
     This product includes software developed by Gary Thomas.
     This product includes software developed by Gordon	Ross
     This product includes software developed by Harvard Univer-
     sity.
     This product includes software developed by Harvard Univer-
     sity and its contributors.
     This product includes software developed by Hellmuth
     Michaelis and Joerg Wunsch
     This product includes software developed by Henrik	Vester-
     gaard Draboel.
     This product includes software developed by Herb Peyerl.
     This product includes software developed by Hidetoshi
     Shimokawa.
     This product includes software developed by Hubert	Feyrer
     for the NetBSD Project.
     This product includes software developed by Ian W.	Dall.
     This product includes software developed by Intel Corpora-
     tion and its contributors.
     This product includes software developed by Internet Initia-
     tive Japan	Inc.
     This product includes software developed by Internet
     Research Institute, Inc.
     This product includes software developed by James R. Maynard
     III.
     This product includes software developed by Jared D.
     McNeill.
     This product includes software developed by Jason L. Wright
     This product includes software developed by Jason R. Thorpe
     for And Communications, http://www.and.com/
     This product includes software developed by Joachim Koenig-
     Baltes.
     This product includes software developed by Jochen	Pohl for
     The NetBSD	Project.
     This product includes software developed by Joerg Wunsch
     This product includes software developed by John Birrell.
     This product includes software developed by John P. Wit-
     tkoski.
     This product includes software developed by John Polstra.
     This product includes software developed by Jonathan R.
     Stone for the NetBSD Project.
     This product includes software developed by Jonathan Stone.
     This product includes software developed by Jonathan Stone
     and Jason R. Thorpe for the NetBSD	Project.
     This product includes software developed by Jonathan Stone
     for the NetBSD Project.
     This product includes software developed by Julian	High-
     field.
     This product includes software developed by K. Kobayashi
     This product includes software developed by K. Kobayashi and
     H.	Shimokawa
     This product includes software developed by Kazuhisa
     Shimizu.
     This product includes software developed by Kazuki	Sakamoto.
     This product includes software developed by Kenneth Stailey.
     This product includes software developed by Kiyoshi Ikehara.
     This product includes software developed by Klaus Burkert,by
     Bernd Ernesti, by Michael van Elst, and by	the University of
     California, Berkeley and its contributors.
     This product includes software developed by Kyma Systems.
     This product includes software developed by Leo Weppelman
     and Waldi Ravens.
     This product includes software developed by Lloyd Parkes.
     This product includes software developed by Lutz Vieweg.
     This product includes software developed by Marc Horowitz.
     This product includes software developed by Marcus	Comstedt.
     This product includes software developed by Mark Brinicombe.
     This product includes software developed by Mark Brinicombe
     for the NetBSD Project.
     This product includes software developed by Mark Tinguely
     and Jim Lowe
     This product includes software developed by Markus	Wild.
     This product includes software developed by Marshall M. Mid-
     den.
     This product includes software developed by Masanobu Saitoh.
     This product includes software developed by Masaru	Oki.
     This product includes software developed by Matt DeBergalis
     This product includes software developed by Matthew Fre-
     dette.
     This product includes software developed by Michael Smith.
     This product includes software developed by Microsoft
     This product includes software developed by Mika Kortelainen
     This product includes software developed by Mike Pritchard.
     This product includes software developed by Mike Pritchard
     and contributors.
     This product includes software developed by Minoura Makoto.
     This product includes software developed by MINOURA Makoto,
     Takuya Harakawa.
     This product includes software developed by Niels Provos.
     This product includes software developed by Niklas	Hal-
     lqvist.
     This product includes software developed by Niklas	Hal-
     lqvist, Brandon Creighton and Job de Haas.
     This product includes software developed by Paolo Abeni.
     This product includes software developed by Paul Kranenburg.
     This product includes software developed by Paul Mackerras.
     This product includes software developed by Paul Mackerras
     <paulus@samba.org>.
     This product includes software developed by Pedro Roque Mar-
     ques <pedro_m@yahoo.com>
     This product includes software developed by Per Fogelstrom.
     This product includes software developed by Peter Galbavy.
     This product includes software developed by Phase One, Inc.
     This product includes software developed by Philip	A. Nel-
     son.
     This product includes software developed by QUALCOMM Incor-
     porated.
     This product includes software developed by Ravikanth.
     This product includes software developed by RiscBSD.
     This product includes software developed by Roar Thronaes.
     This product includes software developed by Rodney	W.
     Grimes.
     This product includes software developed by Roger Hardiman
     This product includes software developed by Rolf Grossmann.
     This product includes software developed by Ross Harvey.
     This product includes software developed by Ross Harvey for
     the NetBSD	Project.
     This product includes software developed by Scott Bartram.
     This product includes software developed by Scott Stevens.
     This product includes software developed by Shingo	WATANABE.
     This product includes software developed by Softweyr LLC,
     the University of California, Berkeley, and its contribu-
     tors.
     This product includes software developed by Stephan Thesing.
     This product includes software developed by Steven	M.
     Bellovin
     This product includes software developed by Takashi Hamada.
     This product includes software developed by Takumi	Nakamura.
     This product includes software developed by Tatoku	Ogaito
     for the NetBSD Project.
     This product includes software developed by Tommi Komulainen
     <Tommi.Komulainen@iki.fi>.
     This product includes software developed by TooLs GmbH.
     This product includes software developed by Trimble Naviga-
     tion, Ltd.
     This product includes software developed by Waldi Ravens.
     This product includes software developed by WIDE Project and
     its contributors.
     This product includes software developed by Winning Strate-
     gies, Inc.
     This product includes software developed by Yen Yen Lim and
     North Dakota State	University
     This product includes software developed by Zembu Labs, Inc.
     This product includes software developed by the Alice Group.
     This product includes software developed by the Computer
     Systems Engineering Group at Lawrence Berkeley Laboratory.
     This product includes software developed by the Computer
     Systems Laboratory	at the University of Utah.
     This product includes software developed by the Harvard Uni-
     versity and its contributors.
     This product includes software developed by the Kungliga
     Tekniska Hoegskolan and its contributors.
     This product includes software developed by the Network
     Research Group at Lawrence	Berkeley Laboratory.
     This product includes software developed by the OpenSSL
     Project for use in	the OpenSSL Toolkit.
     (http://www.OpenSSL.org/)
     This product includes software developed by the PocketBSD
     project and its contributors.
     This product includes software developed by the RiscBSD ker-
     nel team
     This product includes software developed by the RiscBSD
     team.
     This product includes software developed by the SMCC Tech-
     nology Development	Group at Sun Microsystems, Inc.
     This product includes software developed by the University
     of	California, Lawrence Berkeley Laboratories.
     This product includes software developed by the University
     of	California, Lawrence Berkeley Laboratory.
     This product includes software developed by the University
     of	California, Lawrence Berkeley Laboratory and its contrib-
     utors.
     This product includes software developed by the University
     of	Vermont	and State Agricultural College and Garrett A.
     Wollman.
     This product includes software developed by the University
     of	Vermont	and State Agricultural College and Garrett A.
     Wollman, by William F.  Jolitz, and by the	University of
     California, Berkeley, Lawrence Berkeley Laboratory, and its
     contributors.
     This product includes software developed by the Urbana-Cham-
     paign Independent Media Center.
     This product includes software developed for the FreeBSD
     project
     This product includes software developed for the NetBSD
     Project by	Allegro	Networks, Inc.,	and Wasabi Systems, Inc.
     This product includes software developed for the NetBSD
     Project by	Bernd Ernesti.
     This product includes software developed for the NetBSD
     Project by	Christopher G. Demetriou.
     This product includes software developed for the NetBSD
     Project by	Eiji Kawauchi.
     This product includes software developed for the NetBSD
     Project by	Frank van der Linden
     This product includes software developed for the NetBSD
     Project by	Genetec	Corporation.
     This product includes software developed for the NetBSD
     Project by	Jason R. Thorpe.
     This product includes software developed for the NetBSD
     Project by	John M.	Vinopal.
     This product includes software developed for the NetBSD
     Project by	Jonathan Stone.
     This product includes software developed for the NetBSD
     Project by	Kyma Systems LLC.
     This product includes software developed for the NetBSD
     Project by	Matthias Drochner.
     This product includes software developed for the NetBSD
     Project by	Perry E. Metzger.
     This product includes software developed for the NetBSD
     Project by	Piermont Information Systems Inc.
     This product includes software developed for the NetBSD
     Project by	Shigeyuki Fukushima.
     This product includes software developed for the NetBSD
     Project by	SUNET, Swedish University Computer Network.
     This product includes software developed for the NetBSD
     Project by	Wasabi Systems,	Inc.
     This product includes software developed or owned by Caldera
     International, Inc.
     This product includes software developed under OpenBSD by
     Per Fogelstrom.
     This product includes software developed under OpenBSD by
     Per Fogelstrom Opsycon AB for RTMX	Inc, North Carolina, USA.
     This software was developed by Holger Veit	and Brian Moore
     for use with "386BSD" and similar operating systems.  "Simi-
     lar operating systems" includes mainly non-profit oriented
     systems for research and education, including but not
     restricted	to "NetBSD", "FreeBSD",	"Mach" (by CMU).
     The Institute of Electrical and Electronics Engineers and
     The Open Group, have given	us permission to reprint portions
     of	their documentation.

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

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

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

     This notice shall appear on any product containing	this
     material.

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

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

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

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

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

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

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

	   Author: Chris G. Demetriou

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

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

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

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

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

   TThhee EEnndd
NetBSD/hp300 11.0_RC2		 Mar 04, 2026		 NetBSD/hp300 11.0_RC2
