INSTALLATION NOTES for OpenBSD/sparc64 5.2


What is OpenBSD?
----------------

OpenBSD is a fully functional, multi-platform UN*X-like Operating
System based on Berkeley Networking Release 2 (Net/2) and 4.4BSD-Lite.
There are several operating systems in this family, but OpenBSD
differentiates itself by putting security and correctness first.  The
OpenBSD team strives to achieve what is called a 'secure by default'
status.  This means that an OpenBSD user should feel safe that their
newly installed machine will not be compromised.  This 'secure by
default' goal is achieved by taking a proactive stance on security.

Since security flaws are essentially mistakes in design or implement-
ation, the OpenBSD team puts as much importance on finding and fixing
existing design flaws and implementation bugs as it does writing new
code.  This means that an OpenBSD system will not only be more secure,
but it will be more stable.  The source code for all critical system
components has been checked for remote-access, local-access, denial-
of-service, data destruction, and information-gathering problems.

In addition to bug fixing, OpenBSD has integrated strong cryptography
into the base system.  A fully functional IPsec implementation is
provided as well as support for common protocols such as SSL and SSH.
Network filtering and monitoring tools such as packet filtering, NAT,
and bridging are also standard, as well as several routing services,
such as BGP and OSPF.  For high performance demands, support for
hardware cryptography has also been added to the base system.  Because
security is often seen as a tradeoff with usability, OpenBSD provides
as many security options as possible to allow the user to enjoy secure
computing without feeling burdened by it.

Because OpenBSD is from Canada, the export of Cryptography pieces
(such as OpenSSH, IPsec, and Kerberos) to the world is not restricted.

(NOTE: OpenBSD can not be re-exported from the US once it has entered
the US.  Because of this, take care NOT to get the distribution from
an FTP server in the US if you are outside of Canada and the US.)

A comprehensive list of the improvements brought by the 5.2 release
is available on the web at http://www.OpenBSD.org/52.html.

OpenBSD/sparc64 runs on 64-bit UltraSPARC-based machines, including most of
Sun Microsystems workstations and their clones.


Sources of OpenBSD:
-------------------

This is a list of currently known FTP and HTTP servers at the time
of the 5.2 release.  For a more recent list, please refer to

	http://www.OpenBSD.org/ftp.html


Argentina:
    http://openbsd.org.ar/pub/OpenBSD (Buenos Aires)
    ftp://ftp.openbsd.org.ar/pub/OpenBSD (Buenos Aires)

Australia:
    http://mirror.internode.on.net/pub/OpenBSD (Adelaide)
    ftp://mirror.internode.on.net/pub/OpenBSD (Adelaide)
    http://mirror.aarnet.edu.au/pub/OpenBSD (Brisbane)
    ftp://mirror.aarnet.edu.au/pub/OpenBSD (Brisbane)
    http://ftp.iinet.net.au/pub/OpenBSD (Perth)
    ftp://ftp.iinet.net.au/pub/OpenBSD (Perth)
    http://mirror.as24220.net/pub/OpenBSD (Melbourne)
    ftp://mirror.as24220.net/pub/OpenBSD (Melbourne)

Austria:
    http://ftp5.eu.openbsd.org/ftp/pub/OpenBSD (Vienna)
    ftp://ftp5.eu.openbsd.org/pub/OpenBSD (Vienna)
    http://ftp2.eu.openbsd.org/pub/OpenBSD (Vienna)
    ftp://ftp2.eu.openbsd.org/pub/OpenBSD (Vienna)

Brazil:
    http://openbsd.locaweb.com.br/pub/OpenBSD (Sao Paulo)
    ftp://openbsd.locaweb.com.br/pub/OpenBSD (Sao Paulo)

Bulgaria:
    http://mirror.telepoint.bg/OpenBSD (Sofia)

Canada:
    http://ftp.OpenBSD.org/pub/OpenBSD (Alberta)
    ftp://ftp.OpenBSD.org/pub/OpenBSD (Alberta)

Costa Rica:
    http://mirrors.ucr.ac.cr/OpenBSD
    ftp://mirrors.ucr.ac.cr/OpenBSD

Denmark:
    http://ftp.openbsd.dk/pub/OpenBSD (Aalborg)
    ftp://ftp.openbsd.dk/pub/OpenBSD (Aalborg)

Estonia:
    http://ftp.aso.ee/pub/OpenBSD (Tallinn)
    ftp://ftp.aso.ee/pub/OpenBSD (Tallinn)

France:
    http://ftp.fr.openbsd.org/pub/OpenBSD (Paris)
    ftp://ftp.fr.openbsd.org/pub/OpenBSD (Paris)
    http://ftp.arcane-networks.fr/pub/OpenBSD (Paris)
    ftp://ftp.arcane-networks.fr/pub/OpenBSD (Paris)
    http://ftp2.fr.openbsd.org/pub/OpenBSD (Paris)
    ftp://ftp2.fr.openbsd.org/pub/OpenBSD (Paris)

Germany:
    http://openbsd.cs.fau.de/pub/OpenBSD (Erlangen)
    ftp://openbsd.cs.fau.de/pub/OpenBSD (Erlangen)
    http://ftp.spline.de/pub/OpenBSD (Berlin)
    ftp://ftp.spline.de/pub/OpenBSD (Berlin)
    ftp://ftp-stud.fht-esslingen.de/pub/OpenBSD (Esslingen)
    http://ftp.bytemine.net/pub/OpenBSD (Oldenburg)
    ftp://ftp.bytemine.net/pub/OpenBSD (Oldenburg)
    http://ftp.halifax.rwth-aachen.de/openbsd (Aachen)
    ftp://ftp.halifax.rwth-aachen.de/pub/OpenBSD (Aachen)
    http://artfiles.org/openbsd (Hamburg)

Greece:
    http://ftp.cc.uoc.gr/mirrors/OpenBSD (Heraklion)
    ftp://ftp.cc.uoc.gr/mirrors/OpenBSD (Heraklion)

Hungary:
    http://ftp.fsn.hu/pub/OpenBSD (Budapest)
    ftp://ftp.fsn.hu/pub/OpenBSD (Budapest)

Ireland:
    http://ftp.heanet.ie/pub/OpenBSD (Dublin)
    ftp://ftp.heanet.ie/pub/OpenBSD (Dublin)

Japan:
    http://ftp.jaist.ac.jp/pub/OpenBSD (Ishikawa)
    ftp://ftp.jaist.ac.jp/pub/OpenBSD (Ishikawa)
    http://www.ftp.ne.jp/OpenBSD (Saitama)
    ftp://ftp.kddilabs.jp/OpenBSD (Saitama)

Korea:
    http://mirror.yongbok.net/OpenBSD (Seoul)
    ftp://mirror.yongbok.net/pub/OpenBSD (Seoul)

The Netherlands:
    http://ftp.nluug.nl/pub/OpenBSD (Utrecht)
    ftp://ftp.nluug.nl/pub/OpenBSD (Utrecht)
    http://ftp.bit.nl/pub/OpenBSD (Ede)
    ftp://ftp.bit.nl/pub/OpenBSD (Ede)

Norway:
    http://baksmell.netrunner.nu/pub/OpenBSD (Trondheim)
    ftp://baksmell.netrunner.nu/pub/OpenBSD (Trondheim)

Pakistan:
    http://stingray.cyber.net.pk/pub/OpenBSD (Karachi)
    ftp://stingray.cyber.net.pk/OpenBSD (Karachi)

Poland:
    http://piotrkosoft.net/pub/OpenBSD (Oswiecim)
    ftp://ftp.piotrkosoft.net/pub/OpenBSD (Oswiecim)
    http://ftp.icm.edu.pl/pub/OpenBSD (Warszawa)
    ftp://ftp.icm.edu.pl/pub/OpenBSD (Warszawa)

Russia:
    http://mirror.corbina.net/pub/OpenBSD (Moscow)
    ftp://mirror.corbina.net/pub/OpenBSD (Moscow)

Saudi Arabia:
    http://mirrors.isu.net.sa/pub/ftp.openbsd.org (Riyadh)
    ftp://mirrors.isu.net.sa/pub/ftp.openbsd.org (Riyadh)

Slovenia:
    http://www.obsd.si/pub/OpenBSD (Ljubljana)
    ftp://ftp.obsd.si/pub/OpenBSD (Ljubljana)

South Africa:
    http://mirror.is.co.za/mirror/ftp.openbsd.org (Johannesburg)
    ftp://ftp.is.co.za/mirror/ftp.openbsd.org (Johannesburg)

Spain:
    http://mirror.cdmon.com/pub/OpenBSD (Barcelona)
    ftp://mirror.cdmon.com/pub/OpenBSD (Barcelona)

Sweden:
    http://ftp.eu.openbsd.org/pub/OpenBSD (Stockholm)
    ftp://ftp.eu.openbsd.org/pub/OpenBSD (Stockholm)
    http://ftp.netbsd.se/OpenBSD (Stockholm)

Switzerland:
    http://mirror.switch.ch/ftp/pub/OpenBSD (Zurich)
    ftp://mirror.switch.ch/pub/OpenBSD (Zurich)
    http://ftp.ch.openbsd.org/pub/OpenBSD (Zurich)
    ftp://ftp.ch.openbsd.org/pub/OpenBSD (Zurich)

Turkey:
    ftp://ftp.ulak.net.tr/OpenBSD

United Kingdom:
    http://www.mirrorservice.org/pub/OpenBSD (Kent)
    ftp://ftp.mirrorservice.org/pub/OpenBSD (Kent)
    http://mirror.bytemark.co.uk/OpenBSD (Manchester)
    ftp://mirror.bytemark.co.uk/OpenBSD (Manchester)

USA:
    http://ftp5.usa.openbsd.org/pub/OpenBSD (Redwood City, CA)
    ftp://ftp5.usa.openbsd.org/pub/OpenBSD (Redwood City, CA)
    http://ftp3.usa.openbsd.org/pub/OpenBSD (Boulder, CO)
    ftp://ftp3.usa.openbsd.org/pub/OpenBSD (Boulder, CO)
    http://mirror.team-cymru.org/pub/OpenBSD (Chicago, IL)
    ftp://mirror.team-cymru.org/pub/OpenBSD (Chicago, IL)
    http://mirror.planetunix.net/pub/OpenBSD (Chicago, IL)
    ftp://mirror.planetunix.net/pub/OpenBSD (Chicago, IL)
    http://filedump.se.rit.edu/pub/OpenBSD (Rochester, NY)
    ftp://filedump.se.rit.edu/pub/OpenBSD (Rochester, NY)
    http://openbsd.mirror.frontiernet.net/pub/OpenBSD (Rochester, NY)
    ftp://openbsd.mirror.frontiernet.net/pub/OpenBSD (Rochester, NY)
    http://ftp.lambdaserver.com/pub/OpenBSD (Chicago, Illinois)
    ftp://ftp.lambdaserver.com/pub/OpenBSD (Chicago, Illinois)
    http://openbsd.mirrors.hoobly.com (Pittsburgh, PA)
    http://mirror.ece.vt.edu/pub/OpenBSD (Blacksburg, VA)
    http://mirror.servihoo.net/pub/OpenBSD (Kansas City, MO)
    ftp://mirror.servihoo.net/pub/OpenBSD (Kansas City, MO)
    http://openbsd.mirrors.pair.com (Pittsburgh, PA)
    ftp://openbsd.mirrors.pair.com (Pittsburgh, PA)
    http://mirrors.gigenet.com/pub/OpenBSD (Arlington Heights, IL)
    ftp://mirrors.gigenet.com/pub/OpenBSD (Arlington Heights, IL)
    http://mirror.esc7.net/pub/OpenBSD (Dallas, TX)
    ftp://mirror.esc7.net/pub/OpenBSD (Dallas, TX)
    http://openbsd.mirrorcatalogs.com/pub/OpenBSD (Denver, CO)
    ftp://openbsd.mirrorcatalogs.com/pub/OpenBSD (Denver, CO)
    http://mirrors.nycbug.org/pub/OpenBSD (New York City, NY)
    ftp://mirrors.nycbug.org/pub/OpenBSD (New York City, NY)
    http://mirrors.syringanetworks.net/pub/OpenBSD (Boise, ID)
    ftp://mirrors.syringanetworks.net/pub/OpenBSD (Boise, ID)


Additionally, the file ftp://ftp.OpenBSD.org/pub/OpenBSD/ftplist
contains a list which is continually updated.  If you wish to become a
distribution site for OpenBSD, contact <www@OpenBSD.org>.


OpenBSD 5.2 Release Contents:
-----------------------------

The OpenBSD 5.2 release is organized in the following way.  In the
.../5.2 directory, for each of the architectures having an OpenBSD 5.2
binary distribution, there is a sub-directory.

The sparc64-specific portion of the OpenBSD 5.2 release is found in the
"sparc64" subdirectory of the distribution.  That subdirectory is laid
out as follows:

.../5.2/sparc64/

	INSTALL.sparc64	Installation notes; this file.

	SHA256		Output of the sum(1) program using the option
			-a sha256, usable for verification of the
			correctness of downloaded files.

	miniroot52.fs	A miniroot filesystem image to be used if you
			for some reason can't or don't want to use the
			ramdisk installation method.
			It can be copied to the swap partition of an existing
			OpenBSD, Solaris, NetBSD, or Linux installation to
			allow installing or upgrading to OpenBSD 5.2.

	floppy52.fs	The standard sparc64 boot and installation floppy;
			see below.
			This floppy image will boot on some SBus-based
			sparc64 models, such as:
			- Ultra 1/1E
			- Ultra 2

	floppyB52.fs	Another sparc64 boot and installation floppy;
			see below.
			This floppy image will boot on some PCI-based
			sparc64 models, such as:
			- SPARCengineUltra AX
			- SPARCengineUltra AXe
			- SPARCengineUltra AXi

	*.tgz		sparc64 binary distribution sets; see below.

	bsd		A stock GENERIC sparc64 kernel which will be
			installed on your system during the install.

	bsd.mp		A stock GENERIC.MP sparc64 kernel, with support for
			multiprocessor machines, which can be used instead
			of the GENERIC kernel after the install.

	bsd.rd		A compressed RAMDISK kernel; the embedded
			filesystem contains the installation tools.
			Used for simple installation from a pre-existing
			system.

	install52.iso	The sparc64 boot and installation CD-ROM image,
			which contains the base and X sets, so that install
			or upgrade can be done without network connectivity.

	cd52.iso	A miniroot filesystem image suitable to be used
			as a bootable CD-ROM image, but will require the base
			and X sets be found via another media or network;
			otherwise similar to the bsd.rd image above.

	installboot	The OpenBSD/sparc64 boot loader installation program.
	bootblk		The OpenBSD/sparc64 boot block.
	ofwboot		The OpenBSD/sparc64 secondary boot loader.
	ofwboot.net	The OpenBSD/sparc64 network boot loader.


Please note that there are multiple bootable images and kernels, intended
to allow installing OpenBSD/sparc64 in a variety of situations without
requiring a pre-existing working operating system.

The kernel and boot images are provided for net booting installations.

Bootable installation/upgrade floppy images:

	The two floppy images can be copied to a floppy using rawrite.exe,
	ntrw.exe, or `dd', as described later in this document.
	Each floppy image is a bootable install floppy which can be used
	both to install and to upgrade OpenBSD to the current version.
	It is also useful for maintenance and disaster recovery.

The OpenBSD/sparc64 binary distribution sets contain the binaries which
comprise the OpenBSD 5.2 release for sparc64 systems.  There are ten
binary distribution sets.  The binary distribution sets can be found in
the "sparc64" subdirectory of the OpenBSD 5.2 distribution tree,
and are as follows:

	base52	 The OpenBSD/sparc64 5.2 base binary distribution.  You MUST
		 install this distribution set.  It contains the base OpenBSD
		 utilities that are necessary for the system to run and be
		 minimally functional.
		 It includes shared library support, and excludes everything
		 described below.
		 [ 56.6 MB gzipped, 181.0 MB uncompressed ]

	comp52	 The OpenBSD/sparc64 Compiler tools.  All of the tools relating
		 to C, C++ and Objective-C are supported.  This set includes
		 the system include files (/usr/include), the linker, the
		 compiler tool chain, and the various system libraries
		 (except the shared libraries, which are included as part of
		 the base 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.
		 [ 63.5 MB gzipped, 236.5 MB uncompressed ]

	etc52	 This distribution set contains the system configuration
		 files that reside in /etc and in several other places.
		 This set MUST be installed if you are installing the
		 system from scratch, but should NOT be used if you are
		 upgrading.  (If you are upgrading, it's recommended that
		 you get a copy of this set and CAREFULLY upgrade your
		 configuration files by hand; see the section named 
		 Upgrading a previously-installed OpenBSD System" below.)
		 [ 512.8 KB gzipped, 1.5 MB uncompressed ]

	game52	 This set includes the games and their manual pages.
		 [ 2.6 MB gzipped, 6.1 MB uncompressed ]

	man52	 This set includes all of the manual pages for the binaries
		 and other software contained in the base set.
		 Note that it does not include any of the manual pages
		 that are included in the other sets.
		 [ 9.2 MB gzipped, 35.7 MB uncompressed ]

	xbase52  This set includes the base X distribution.  This includes
		 programs, headers and libraries.
		 [ 11.8 MB gzipped, 39.8 MB uncompressed ]

	xetc52	 This set includes the X window system configuration files
		 that reside in /etc.  It's the equivalent of etc52 for X.
		 [ 71.1 KB gzipped, 272.8 KB uncompressed ]

	xfont52  This set includes all of the X fonts.
		 [ 37.5 MB gzipped, 48.5 MB uncompressed ]

	xserv52  This set includes all of the X servers.
		 [ 6.2 MB gzipped, 17.1 MB uncompressed ]

	xshare52 This set includes all text files equivalent between all
		 architectures.
		 [ 3.2 MB gzipped, 17.5 MB uncompressed ]



OpenBSD System Requirements and Supported Devices:
--------------------------------------------------

OpenBSD/sparc64 5.2 runs on the following classes of machines:
	Ultra 1/1E 
	Ultra 2 
	Ultra 3 Mobile Workstation 
	Ultra 5/10 
	Ultra 25/45 
	Ultra 30/60/80 
	SPARCengineUltra AX 
	SPARCengineUltra AXe 
	SPARCengineUltra AXi 
	SPARCengineUltra AXdp 
	SPARCengineUltra AXmp 
	SPARCengine CP1500 
	Enterprise 150 
	Enterprise 220R 
	Enterprise 250 
	Enterprise 420R 
	Enterprise 450 
	Enterprise 3000/4000/5000/6000 
	Enterprise 3500/4500/5500/6500 
	Enterprise 10000 
	Sun Blade 100/150 
	Sun Blade 1000/2000 
	Sun Blade 1500/2500 
	Sun Blade T6300 
	Sun Blade T6320 
	Sun Blade T6340 
	Sun Fire V100/V120 
	Sun Fire V125 
	Sun Fire V210/V240/V440 
	Sun Fire V215/V245 
	Sun Fire V250 
	Sun Fire 280R 
	Sun Fire V480/V880 
	Sun Fire V490/V890 
	Sun Fire V1280 
	Sun Fire T1000/T2000 
	Sun SPARC Enterprise T1000/T2000 
	Sun SPARC Enterprise T5120/T5220 
	Sun SPARC Enterprise T5140/T5240 
	Sun SPARC Enterprise T5440 
	Sun SPARC Enterprise M4000/M5000/M8000/M9000 
	Sun SX1500 
	Sun SX2500 
	Sun SX3200 
	Netra AX1105 
	Netra AX2200 
	Netra X1 
	Netra 20/T4 
	Netra 120 
	Netra 210/240/440 
	Netra 1280 
	Netra 1290 
	Netra T1 100/105 
	Netra T1 AC200/DC200 
	Netra T 1100 
	Netra T 1120/1125 
	Netra T 1400/1405 
	Netra CP3060
	Netra CP3260
	Netra T2000
	Netra T5220 
	Netra T5440 
	Fujitsu PRIMEPOWER 250/450 
	Fujitsu PRIMEPOWER 650/850  (with SPARC64-V processors only)
	Fujitsu SPARC Enterprise T1000/T2000 
	Fujitsu SPARC Enterprise T5120/T5220 
	Fujitsu SPARC Enterprise T5140/T5240 
	Fujitsu SPARC Enterprise T5440 
	Fujitsu SPARC Enterprise M4000/M5000/M8000/M9000 
as well on faithful clones of the above Sun systems, including:
	Momentum Leopard-V 
	RDI/Tadpole UltraBook 170/200 
	Tadpole SPARCLE 550SX/650SX
	Tadpole Viper 

Even if your machine is not listed above, it is possible that OpenBSD/sparc64
will work on it.  OpenBSD/sparc64 does not work on machines with Fujitsu's
SPARC64-I, SPARC64-II, SPARC64-III and SPARC64-IV processors.

OpenBSD/sparc64 5.2 supports SMP (Symmetrical MultiProcessor)
systems.  To support SMP operation, a separate SMP kernel (bsd.mp) is
included with the installation file sets.

The minimal configuration requires 32MB of RAM and ~160MB of disk space.
To install the entire system requires much more disk space, and to run
X or compile the system, more RAM is recommended.

Supported devices include:
	SCSI Host Adapters:
		Adaptec AIC-7770, AIC-7850, AIC-7860, AIC-7870, AIC-7880,
		AIC-7890, AIC-7891, AIC-7892, AIC-7895, AIC-7896, AIC-7897
		and AIC-7899 based host adapters (ahc), including the
		Adaptec cards
			AHA-274X[W,T]
			AHA-284X
			AHA-2910, AHA-2915
			AHA-2920
			AHA-2930[C,U2]
			AHA-2940[J,N,U,AU,UW,UW Dual,UW Pro,U2W,U2B]
			AHA-2950[U2W,U2B]
			AHA-3940[U,AU,UW,AUW,U2W]
			AHA-3950U2
			AHA-3960
			AHA-3985
			AHA-4944UW
			AHA-19160B
			AHA-29160[B,N]
			AHA-39160
		SBus NCR53c9x adapters (esp)
		SBus 10/100Mbit SunSwift Ethernet+SCSI cards, aka HME + FAS366
		  cards (esp)
		SBus and PCI QLogic adapters (isp)
		PCI NCR53c8xx adapters (siop)
		AMD Am53c974 PCscsi-PCI host adapters including the Tekram
		  DC-390 (pcscp)
		LSI Logic Fusion-MPT(Symbios Logic/NCR) (mpi) 

	PCI IDE Controllers: (pciide)
		Acer Labs M5229
		Command Technologies PCI0646, PCI0680
		National Semiconductor PC87415
		Promise PDC20262, PDC20267, PDC20268
		Other PCI IDE controllers may work, but have not been tested

	CD-ROM and DVD-ROM Drives
		Most SCSI CD-ROM, CD-R, CD-RW, DVD and DVD-RW drives
		Most ATAPI CD-ROM, CD-R, CD-RW, DVD and DVD-RW drives

	Ethernet Adapters:
		onboard AMD Lance Ethernet (le)
		SBus AMD Lance Ethernet cards (le)
		SBus 10/100MBit Sun FastEthernet 1.0 cards (qec/be)
		SBus Quad 10MBit Sun QuadEthernet cards (qec/qe)
		onboard SBus/PCI HME Ethernet cards (hme)
		SBus 10/100Mbit Ethernet cards (hme)
		SBus 10/100Mbit SunSwift Ethernet+SCSI cards (hme)
		SBus Quad 10/100MBit Quad Fast Ethernet cards (hme, qfe)
		PCI Fast Ethernet (hme)
		PCI Quad Fast Ethernet (hme)
		PCI Gigabit Ethernet (gem)
		PCI GigaSwift Ethernet (cas)
		PCI Alteon Tigon I/II PCI Gigabit Ethernet boards (ti)
		PCI Digital DC21x4x-based PCI adapters (de)
		PCI Davicom DM9102 Ethernet (dc)
		PCI Intel 21145-based adapters (dc)
		PCI Intel i8255x-based (except the i82556) adapters (fxp)
		PCI 3Com 3c9xx EtherLink XL adapters (xl)
		PCI SMC 83C170 ("EtherPower II") (EPIC/100) (epic)
		AMD PCnet-based PCI adapters (pcn)
                    BOCALANcard/PCI
                    AT&T StarLAN 10, EN100, and StarLAN Fiber
		Intel i82540, i82541, i82542, i82543, i82544, i82545, i82546,
		i82547, i82571, i82572 and i82573 based adapters, including:
		    HP ProLiant NC310F PCI-X Gigabit NIC (SX Fiber)
		    HP ProLiant NC340T PCI-X Gigabit NIC
		    HP ProLiant NC360T PCI Express Dual Port Gigabit NIC
		    HP ProLiant NC6132 Upgrade Module (SX Fiber)
		    HP ProLiant NC6133 Upgrade Module (LX Fiber)
		    HP ProLiant NC6134 PCI Gigabit NIC (SX Fiber)
		    HP ProLiant NC6136 PCI Gigabit NIC (SX Fiber)
		    HP ProLiant NC6170 PCI-X Gigabit NIC (SX Fiber)
		    HP ProLiant NC7131 PCI Gigabit NIC
		    HP ProLiant NC7132 Upgrade Module
		    HP ProLiant NC7170 PCI-X Dual Port Gigabit NIC
		    HP ProLiant NC7170LP PCI-X Dual Port Gigabit NIC
		    Intel PRO/1000 Gigabit Server Adapter (SX Fiber)
		      (PWLA8490)
		    Intel PRO/1000F Gigabit Server Adapter (SX Fiber)
		      (PWLA8490SX)
		    Intel PRO/1000T Server Adapter (PWLA8490T)
		    Intel PRO/1000XT Server Adapter (PWLA8490XT)
		    Intel PRO/1000XS Server Adapter (SX Fiber) (PWLA8490XF)
		    Intel PRO/1000T Desktop Adapter (PWLA8390T)
		    Intel PRO/1000XTL Lo Profile PCI Server (PWLA8490XTL)
		    Intel PRO/1000MT Desktop Adapter (PWLA8390MT)
		    Intel PRO/1000MT Server Adapter (PWLA8490MT)
		    Intel PRO/1000MT Dual Port Server Adapter (PWLA8492MT)
		    Intel PRO/1000MF Server Adapter (SX Fiber) (PWLA8490MF)
		    Intel PRO/1000MF Dual Port Server Adapter (SX Fiber)
		      (PWLA8492MF)
		    Intel PRO/1000MF Server Adapter (LX Fiber) (PWLA8490LX)
		    Intel PRO/1000MT Quad PCI-X Adapter (PWLA8494MT)
		    Intel PRO/1000GT Quad PCI-X Adapter (PWLA8494GT)
		    Intel PRO/1000PT Desktop Adapter
		    Intel PRO/1000PT Server Adapter
		    Intel PRO/1000PT Dual Port Server Adapter
		    Intel PRO/1000PT Quad Port Server Adapter
		    Intel PRO/1000PF Server Adapter (SX Fiber)
		    Intel PRO/1000PF Dual Port Server Adapter (SX Fiber)
		Broadcom BCM570x (Tigon3) based PCI adapters 
		    3Com 3c996-T (10/100/1000baseT) 
		    3Com 3c996-SX (1000baseSX) 
		    3Com 3c996B-T (10/100/1000baseT) 
		    HP ProLiant NC370F PCI-X Gigabit NIC (1000baseSX) 
		    HP ProLiant NC370T PCI-X Gigabit NIC (10/100/1000baseT) 
		    HP ProLiant NC1020 PCI Gigabit NIC (10/100/1000baseT) 
		    HP ProLiant NC6770 PCI-X Gigabit NIC (1000baseSX) 
		    HP ProLiant NC7770 PCI-X Gigabit NIC (10/100/1000baseT) 
		    HP ProLiant NC7771 PCI-X Gigabit NIC (10/100/1000baseT) 
		    HP ProLiant NC7781 embedded PCI-X Gigabit NIC (10/100/1000baseT) 
		    Netgear GA302T (10/100/1000baseT) 
		    SysKonnect SK-9D21 (10/100/1000baseT) 
		    SysKonnect SK-9D41 (1000baseSX) 
		Sundance/Tamarack TC9021 based PCI adapters, including: 
		    Allied Telesis CentreCOM LA1000-PCI-T 
		    Antares Microsystems TC9021 
		    D-Link DGE-550T 
               PCI RealTek 8129, RealTek 8139 Ethernet adapters, including:
                    Accton MPX 5030/5038
                    Allied Telesyn AT2550
                    Corega FEther CB-TXD 10/100 Ethernet 
                    D-Link DFE530TX+, DFE538TX
                    Encore ENL832-TX-RENT 10/100 M PCI
                    Genius GF100TXR
                    KTX-9130TX 10/100 Fast Ethernet
                    Longshine LCS-8038TX-R
                    NDC NE100TX-E
                    Netgear FA311 v2
                    Netronix EA-1210 Net Ether 10/100
                    Nortel BayStack 21
                    OvisLink LEF-8129TX, LEF-8139TX
                    SMC EZ Card 10/100 PCI 1211-TX
                    TRENDnet TE100-PCBUSR CardBus 
                Realtek 8169/8169S/8110S based PCI adapters, including:
                    Buffalo LGY-PCI-GT (8169S)
                    Corega CG-LAPCIGT (8169S)
                    D-Link DGE-528T (8169S)
                    Gigabyte 7N400 Pro2 Integrated Gigabit Ethernet (8110S)
                    LevelOne GNC-0105T (8169S)
                    Linksys EG1032v3 (8169S)
		    Netgear GA311 (8169S)
                    Netgear GA511 PC Card (8169)
                    PLANEX COMMUNICATIONS Inc. GN-1200TC (8169S)
                    Surecom EP-320G-TX1 (8169S)
                    US Robotics USR997902 (8169S)
                    Xterasys XN-152 10/100/1000 NIC (8169)
		ADMtek AN986-based USB adapters, including:
		    3Com 3c460b
		    Abocom UFE1000
		    Abocom DSB650TX
		    Accton USB320-EC
		    Accton SpeedStream Ethernet
		    Admtek Pegasus, Pegasus II
		    Billionton Systems USB100, USB100EL, USB100LP, USBE100
		    Corega FEther USB-TX, USB-TXS
		    D-Link DSB-650, 650TX, 650TX-PNA
		    ELCON Systemtechnik Goldpfeil P-LAN
		    Elecom LD-USB, LD-USBL/TX
		    Elsa Microlink USB2Ethernet
		    GIGABYTE GN-BR402W 
		    Hawking UF100 
		    HP HN210E 
		    I/O Data USB ETTX
		    Kingston KNU101TX
		    Linksys USB100TX, USB100H1, USB10T, USB10TA, USB10TX 
		    Melco Inc. LUA-TX, LUA2-TX
		    Microsoft MN110 
		    Mobility EasiDock Ethernet 
		    Netgear FA101 
		    Omnidirectional Control Technology USB TO Ethernet 
		    Siemens SpeedStream USB
		    SmartBridges smartNIC 2
		    SMC 2202USB/ETH
		    SMC 2206USB/ETH
		    SOHOware NUB100, NUB110
		ASIX Electronics AX88172/AX88178/AX88772 USB Ethernet adapters,
		including:
		    ATEN UC210T
		    BAFO BF-320
		    Billionton Systems USB2AR
		    Buffalo(MELCO) LUA-U2-KTX
		    Corega FEther USB2-TX
		    D-Link DUB-E100
		    Good Way GWUSB2E
		    Hawking UF200
		    Intellinet USB 2.0 to Ethernet (rev A)
		    IO-Data ETG-US2
		    JVC MP-PRX1
		    Level One USB-0200
		    Linksys USB200M
		    Netgear FA120
		    Nintendo Wii USB Lan Ethernet Adapter RVL-015
		    OQO model 01+ Ethernet
		    Sitecom LN-029
		    SMC 2209USB/ETH
		    SnapPort USB 2.0 LAN Adapter
		    ST Lab USB 2.0 Fast Ethernet
		    Surecom EP-1427X-2
		    System TALKS SGC-X2UL
		    TRENDnet TU2-ET100
		    Z-TEK ZK-R01-2
		CATC USB-EL1210A-based USB adapters, including:
		    Belkin F5U111 
		    CATC Netmate and Netmate II 
		    SmartBridges SmartLink 
		Davicom DM9601 based USB adapters, including:
		    Corega FEther USB-TXC
		    HenTong WK-668
		    ShanTou ST268
		Kawasaki LSI KL5KUSB101B-based USB adapters, including:
		    3Com 3c19250
		    3Com 3c460 HomeConnect
		    AboCom Systems URE450 Ethernet
		    ADS Technologies USB-10T
		    Aox USB101
		    Asante USB to Ethernet
		    ATen DSB-650C
		    ATen UC10T
		    Corega USB-T
		    D-Link DSB-650C
		    Entegra NET-USB-E45
		    I/O Data USB-ET/T
		    Jaton USB XpressNet
		    Kawasaki USB101
		    Kingston Ethernet
		    Linksys USB10T
		    Mobility Ethernet
		    Netgear EA101
		    Peracom USB
		    Portgear Ethernet
		    Portsmith Express Ethernet
		    Psion Dacom Gold Port Ethernet
		    Shark Pocket Adapter
		    Silicom U2E
		    SMC 2102/2104USB
		RealTek RTL8150L based USB adapters, including:
		    Abocom RTL8151
		    BAFO BF-310
		    Billionton USBKR-100
		    Compex UE202-B
		    GreenHouse GH-USB100B
		    GreenHouse GH-USB100B with HomePNA
		    Hawking Technology HUF11
		    Linksys USB100M
		    Longshine LCS-8138TX
		    Melco Inc. LUA-KTX
		    Micronet SP128AR
		    NetComm NP1010
		    OQO model 01 (10/100) Ethernet
		    Repotec RP-USB100-A
		    SMC 2208USB/ETH
		    TRENDnet TU-ET100C
		    Zt USB10/100
		    ZyXEL Prestige
		    Z-TEK ZK-R02

	Wireless Ethernet Adapters
		Atheros IEEE 802.11a/b/g CardBus adapters
		Atheros IEEE 802.11a/b/g PCI adapters
		Atheros USB IEEE 802.11a/b/g USB adapters
		Atmel AT76C50x IEEE 802.11b USB adapters
		Conexant/Intersil Prism GT Full-MAC IEEE 802.11a/b/g PCI
		    adapters
		Marvell Libertas IEEE 802.11b/g Compact Flash adapters (will be
		    detected as PCMCIA adapters)
		Ralink Technology IEEE 802.11a/b/g CardBus adapters
		Ralink Technology IEEE 802.11a/b/g PCI adapters
		Ralink Technology IEEE 802.11b/g USB adapters
		Ralink Technology USB IEEE 802.11a/b/g USB adapters
		Ralink Technology USB IEEE 802.11a/b/g/Draft-N USB adapters
		TI ACX100/ACX111 IEEE 802.11a/b/g PCI adapters
		WaveLAN/IEEE, PRISM 2-3, and Spectrum24 IEEE 802.11b Compact
		    Flash adapters (will be detected as PCMCIA adapters)
		WaveLAN/IEEE, PRISM 2-3, and Spectrum24 IEEE 802.11b PCI
		    adapters
		WaveLAN/IEEE, PRISM 2-3, and Spectrum24 IEEE 802.11b PCMCIA
		    adapters
		WaveLAN/IEEE, PRISM 2-3, and Spectrum24 IEEE 802.11b USB
		    adapters

	WAN Adapters
		SBE (formerly Lan Media Corporation) SSI (T1)/HSSI/DS1/DS3

	Universal Serial Bus (USB) Devices
		USB Audio
		USB Diamond Multimedia Rio MP3 players
		USB Ethernet adapters, see above
		USB Generic Human Interface Devices (catch-all)
		USB Handspring Visor
		USB Hubs
		USB Keyboards
		USB Mass Storage devices, i.e., USB floppy drives and
		  USB memory stick controllers
		USB Mice
		USB Modems
		USB Printers
		USB Scanners
		USB-USB cables
		USB Y@p phone

	Serial ports
		onboard SBUS Zilog 8530 (zs)
		onboard EBUS Infineon (Siemens) 82532 (sab)
		onboard 16550 compatibles (com)
		SBus MAGMA cards including: 4Sp, 8Sp, 12Sp, 16Sp,
			LC2+1Sp, 2+1Sp, 4+1Sp, 8+2Sp, and 2+1HS Sp
		SBus Serial Parallel Interface (spif)
		Aurora SBus sio2 Serial Interface (asio)
		PCI `universal' communication cards, providing serial
		  and parallel ports, including:
		    AT&T/Lucent Venus Modem (found on IBM 33L4618
			card, Actiontec 56K, and others)
		    Avlab Low Profile PCI 4S Quartet (4 port serial)
		    Avlab PCI 2S (2 port serial)
		    Boca Research Turbo Serial 654 PCI (4 port serial)
		    Boca Research Turbo Serial 658 PCI (8 port serial)
		    Decision Computer Inc PCCOM PCI 2 Port (serial)
		    Decision Computer Inc PCCOM PCI 4 Port (serial)
		    Decision Computer Inc PCCOM PCI 8 Port (serial)
		    Digi International Digi Neo 4 (4 port serial)
		    Dolphin Peripherals 4014 (dual parallel) and
			4035 (dual serial)
		    Exsys EX-41098 (4 port serial)
		    Koutech IOFLEX-2S (dual serial
		    Kouwell Model-223 (2-port serial, 1 port parallel)
		    Lava Computers 2SP-PCI (parallel port)
		    Lava Computers 2SP-PCI and Quattro-PCI (dual serial)
		    Lava Computers Octopus-550
		    Lava LavaPort-650
		    Moxa Technologies Co., Ltd. PCI I/O Card 4S (4 port
			serial)
		    Moxa Technologies Co., Ltd. C104H/PCI (4 port serial)
		    Moxa Technologies Co., Ltd. CP104/PCI (4 port serial)
		    NEC PK-UG-X008 (serial)
		    NEC PK-UG-X001 K56flex PCI (modem)
		    NetMos 1P (1 port parallel)
		    NetMos 2S1P (2 port serial and 1 port parallel)
		    NetMos 4S (4 port serial)
		    Oxford OX16PCI952 (2 port serial, 1 port parallel)
		    Oxford OX16PCI954 (4 port serial, 1 port parallel)
		    SIIG Cyber 2P1S (dual parallel, single serial)
			and 2S1P (dual serial, single parallel)
		    SIIG Cyber 4S (quad serial)
		    SIIG Cyber I/O (single parallel, single serial)
		    SIIG Cyber Parallel, Parallel Dual, Serial,
			Serial Dual
		    SIIG Cyber 8S PCI 16C850
		    SUNIX 400x (1 port parallel)
		    SUNIX 401x (2 port parallel)
		    SUNIX 402x (1 port serial)
		    SUNIX 403x (2 port serial)
		    SUNIX 405x (4 port serial)
		    SUNIX 406x (8 port serial)
		    SUNIX 407x (2 port serial and 1 port parallel)
		    SUNIX 408x (2 port serial and 2 port parallel)
		    SUNIX 409x (4 port serial and 2 port parallel)
		    Syba Tech Ltd. PCI-4S2P-550-ECP (4 port serial, 2
			port parallel)
		    US Robotics 3CP5609 PCI (modem)
		    VScom PCI 800  (8 port serial)
		    VScom PCI 011H (1 port parallel)
		    VScom PCI 100H (1 port serial)
		    VScom PCI 110H (1 port serial and 1 port parallel)
		    VScom PCI 200H (2 port serial)
		    VScom PCI 210H (2 port serial and 1 port parallel)
		    VScom PCI 400H (4 port serial)
		    VScom PCI 410H (4 port serial and 1 port parallel)
		    VScom PCI 800H (8 port serial)
		    VScom PCI 100L (1 port serial)
		    VScom PCI 200L (2 port serial)
		    VScom PCI 210L (2 port serial and 1 port parallel)
		    VScom PCI 400L (4 port serial)
		    VScom PCI 800L (8 port serial)

	Sound devices
		onboard SBus CS4321 (audiocs)
		onboard EBus/PCI CS4231 (audioce)
		Trident 4DWAVE-DX/NX, SiS 7018, ALi M5451 (autri)
		Ensoniq AudioPCI (eap)
		ESS Solo-1 PCI AudioDrive (eso)

	Cryptography accelerators
		Hifn 6500 (lofn)
		Hifn 7751/7811/7951/7955/7956/9751 (hifn)
		Bluesteelnet 5501/5601 (ubsec)
		Broadcom 5801/5802/5805/5820/5821/5822/5823 (ubsec)

	Keyboard and mice
		Type 4, 5 and 6 keyboards on Zilog serial ports (zskbd)
		Type 4, 5 and 6 keyboards on NS16550 serial ports (comkbd)
		Type 6 and 7 keyboards on USB (ukbd)
		PS/2 AT keyboards (pckbd)
		Sun mice on Zilog serial ports (zstty)
		Sun mice on NS16550 serial ports (com)
		USB mice (ums)
		PS/2 mice (pms)

	Framebuffers
		SBUS framebuffers:
			bwtwo - monochrome, unaccelerated
			cgthree - 8 bit color, unaccelerated
			cgsix - 8 bit color, accelerated (GX, GX+, TGX, TGX+)
			cgtwelve - 24 bit color, 1 bit overlay,
			    accelerated (but the driver does not support
			    hardware acceleration)
			Fujitsu AG-10e (agten) - 24-bit color, accelerated
			    (currently only supported in 8-bit
			    unaccelerated mode)
			Parallax XVideo and PowerVideo (tvtwo) - 24-bit color,
			    accelerated (but the driver does not support
			    hardware acceleration)
			RasterFlex series (rfx) - 8/24-bit color,
			    accelerated (currently only supported in 8-bit
			    unaccelerated mode)
			Southland Media Systems MGX and MGXPlus (mgx) -
			    24-bit color, accelerated (currently only
			    supported in 8-bit accelerated mode)
			Vigra VS10, VS11 and VS12 framebuffers (8-bit color,
			    selectable VGA-compatible modes and connector)
			ZX (aka Leo) - 8/24-bit color, overlay planes,
			    double-buffered, 3-D acceleration
		PCI video boards:
			Sun PGX, PGX24 and PGX64 (machfb) - 8/24-bit color,
			    accelerated
			Tech Source Raptor GFX-4M/8M (raptor) -
			    8/24-bit color, accelerated
			Tech Source Raptor GFX-8P/Sun PGX32 (gfxp) -
			    8/24-bit color, accelerated
			Sun XVR-100 and XVR-300 (radeonfb) - 8/24-bit color,
			    accelerated
			Sun Exper3D, Expert3D-Lite, XVR-500, XVR-600 and
			     XVR-1200 (ifb) - 24-bit color, accelerated
			     (currently restricted to 8-bit, unaccelerated on
			     the XVR-500 and XVR-600, accelerated on the
			     Exper3D, Exper3D-Lite and XVR-1200)
		UPA Creator/Creator3D/Elite3D (creator) - 24-bit color,
		     accelerated

	PC Cards (PCMCIA)
		PCMCIA Controllers:
			SBus PCMCIA bridge (stp)
			PCI CardBus bridge (cbb)
		Wireless Ethernet adapters:
			See above.

	Radio Receiver Devices
		D-Link DSB-R100 USB radio

	Miscellaneous devices
		EBus beeper (beeper)
		LDOMs virtual disks (vdsk)
		LDOMs virtual network interfaces (vnet)
		performance counters/system controller (uperf)
		Watchdog timer (pmc)
		LED controller (led, ppm)
		SBus Expansion Subsystem (SUNW,xbox) (xbox)
		    (currently restricted to non-DMA devices)
		onboard floppy drive on SBus systems (such as Ultra 1 and
		    Ultra 2)
		Hardware monitoring sensors, including:
		    Analog Devices AD7416, AD7417 and AD7418 (adc)
		    Analog Devices ADM1021 (admtemp)
		    Analog Devices ADM1024 (admlc)
		    Analog Devices ADM1025 (admtm)
		    Analog Devices ADM1030 (admtmp)
		    Analog Devices ADM1031 (admtt)
		    Analog Devices ADT7460 (adt)
		    National Semiconductor LM75, LM77 (lmtemp)
		    National Semiconductor LM78, LM78-J, LM79 (lm)
		    National Semiconductor LM87 (lmenv)
		    Maxim DS1624/DS1631/DS1721 (maxds)
		    Maxim MAX6642/MAX6690 (maxtmp)
		    Philips PCF8591 (pcfadc)
		Meinberg Funkuhren radio clocks, including:
		    GPS170PCI 3.3V/5V 6-channel GPS receiver card
		    PCI32 5V DCF77 time signal station receiver card
		    PCI509 5V DCF77 time signal station receiver card
		    PCI511 3.3V/5V DCF77 time signal station receiver card




Getting the OpenBSD System onto Useful Media:
---------------------------------------------

Installation is supported from several media types, including:

	CD-ROM (NOT supported if booting from floppy)
	FFS partitions
	Tape
	FTP
	HTTP

If you have the OpenBSD CD-ROM distribution (and a CD-ROM drive), you may be
able to boot from it, or from the supplied bootable CD-ROM mini image. If you
can boot from the CD-ROM, you are home free and can proceed to the
installation steps.  If not, you will need to do some setup work to prepare
a bootable image, either a floppy, hard drive, or compatible net boot
server.

In addition to the bootable image, you also need to consider how to
access the binary distribution sets to actually install the system.

Although you can access the distribution sets directly from the CD-ROM or
from one of the FTP mirrors over the internet, you may wish to transfer
the sets to a local FTP server, or copy them to a partition on the target
system's disk.

Creating a bootable floppy disk using DOS/Windows:

	First you need to get access to the OpenBSD bootable floppy
	images.  If you can access the distribution from the CD-ROM under
	DOS, you will find the bootable disks in the 5.2/sparc64
	directory.  Otherwise, you will have to download them from one of
	the OpenBSD FTP or HTTP mirror sites, using an FTP client or a web
	browser.  In either case, take care to do "binary" transfers, since
	these are images files and any DOS cr/lf translations or Control-z
	EOF interpretations will result in corrupted transfers.
	
	You will also need to go to the "tools" directory and grab a
	copy of the rawrite.exe utility and its documentation.  This
	program is needed to correctly copy the bootable filesystem
	image to the floppy, since it's an image of a unix partition
	containing an ffs filesystem, not an MSDOS format diskette.

	Once you have installed rawrite.exe, just run it and specify the
	name of the bootable image, such as "floppy52.fs" and the name of
	the floppy drive, such as "a:".  Be sure to use good quality HD
	(1.44MB) floppies, formatted on the system you're using.  The
	image copy and boot process is not especially tolerant of read
	errors.

	Note that if you are using NT, 2000, or XP to write the
	images to disk, you will need to use ntrw.exe instead.  It
	is also available in the "tools" directory.  Grab it and
	run in with the correct arguments like this "ntrw <image>
	<drive>:"

	Note that, when installing, the boot floppy can be write-protected
	(i.e. read-only).

Creating a bootable floppy disk using SunOS, Solaris or other Un*x-like
system:

	First, you will need obtain a local copy of the bootable filesystem
	image as described above.  If possible use the sha1(1) command to
	verify the checksums of the images vs. the values in the SHA256 file
	on the mirror site.

	Next, use the dd(1) utility to copy the file to the floppy drive.
	The command would likely be, under SunOS:
		dd if=floppy52.fs of=/dev/rfd0c bs=36b
	and, under Solaris:
		dd if=floppy52.fs of=/dev/rdiskette0 bs=36b
	unless the volume management daemon, vold(1M), is running, in
	which case the following command is preferable:
		dd if=floppy52.fs of=/vol/dev/rdiskette0 bs=36b

	If you are using another operating system, you may have to adapt
	this to conform to local naming conventions for the floppy and
	options suitable for copying to a "raw" floppy image.  The key
	issue is that the device name used for the floppy *must* be one
	that refers to the correct block device, not a partition or
	compatibility mode, and the copy command needs to be compatible
	with the requirement that writes to a raw device must be in
	multiples of 512-byte blocks.  The variations are endless and
	beyond the scope of this document.

	If you're doing this on the system you intend to boot the floppy on,
	copying the floppy back to a file and doing a compare or checksum
	is a good way to verify that the floppy is readable and free of
	read/write errors.

	Note that, when installing, the boot floppy can be write-protected
	(i.e. read-only).

Creating a bootable hard disk using SunOS, Solaris or other Un*x-like system:

	If you don't have a floppy drive you can copy the miniroot
	"miniroot52.fs" onto the hard disk you intend to boot on.
	Traditionally, the way to do this is to use dd(1) to place the
	bootable filesystem image in the "swap" partition of the disk
	(while running in single user mode), and then booting from that
	partition.

	Using the "b" partition allows you to boot without overwriting
	any useful parts of the disk; you can also use another partition,
	but don't use the "a" or "c" partition without understanding the
	disk label issues described below under "incompatible systems".

	This requires that you be running SunOS, Solaris, OpenBSD, or NetBSD,
	which have a compatible view of SunOS disk labels and partitions.

	Use the dd(1) utility to copy the file to the hard drive.
	The command would likely be, under SunOS:
 		dd if=miniroot52.fs of=/dev/rsd0b bs=64b
	and under Solaris:
 		dd if=miniroot52.fs of=/dev/rdsk/c0t0d0s1 bs=64b

	The blocksize is arbitrary as long as it's a multiple of 512-bytes
	and within the maximum supported by the driver, i.e. bs=126b may
	not work for all cases.  Again, device/partition names may vary,
	depending on the OS involved.

	If you are preparing the hard drive on an incompatible system or
	don't care about the hard disk contents, you can also install the
	bootable image starting at the beginning of the disk. This lets
	you prepare a bootable hard-drive even if don't have a working
	operating system on your machine, but it is important to understand
	that the bootable image installed this way includes a "disk label"
	which can wipe out any pre-existing disklabels or partitioning for
	the drive.

Creating a network bootable setup using SunOS or other Un*x-like system:

	The details of setting up a network bootable environment vary
	considerably, depending on the network's host.  Extract the
	OpenBSD diskless(8) man page from the man52.tgz distribution
	set or see the copy on the OpenBSD web page.  You will also
	need to reference the relevant man pages or administrators guide
	for the host system.
	
	Basically, you will need to set up reverse-arp (rarpd) and boot
	parameter (rpc.bootparamd) information and make the OpenBSD
	bootblock, kernel/miniroot partition, and a swap file available
	as required by the netboot setup.


The steps necessary to prepare the distribution sets for installation
depend on which method of installation you choose.  Some methods
require a bit of setup first that is explained below.

The installation allows installing OpenBSD directly from FTP mirror
sites over the internet, however you must consider the speed and
reliability of your internet connection for this option.  It may save
much time and frustration to use ftp get/reget to transfer the
distribution sets to a local server or disk and perform the installation
from there, rather than directly from the internet.

The variety of options listed may seem confusing, but situations vary
widely in terms of what peripherals and what sort of network arrangements
a user has, the intent is to provide some way that will be practical.

Creating an installation tape:

	While you won't be able to boot OpenBSD from a tape, you can use
	one to provide the installation sets.  To do so, you need to make
	a tape that contains the distribution set files, each in "tar"
	format or in "gzipped tar format".  First you will need to
	transfer the distribution sets to your local system, using ftp or
	by mounting the CD-ROM containing the release.  Then you need to
	make a tape containing the files.

	If you're making the tape on a UN*X-like system, the easiest way
	to do so is make a shell script along the following lines, call it
	"/tmp/maketape".

	#! /bin/sh
	TAPE=${TAPE:-/dev/nrst0}
	mt -f ${TAPE} rewind
	for file in base etc comp game man xbase xetc xfont xserv xshare
	do
		dd if=${file}52.tgz of=${TAPE} obs=8k conv=osync
	done
	tar cf ${TAPE} bsd
	mt -f ${TAPE} offline
	# end of script

	And then:

	cd .../5.2/sparc64
	sh -x /tmp/maketape

	If you're using a system other than OpenBSD or SunOS, the tape
	name and other requirements may change.  You can override the
	default device name (/dev/nrst0) with the TAPE environment
	variable.  For example, under Solaris, you would probably run:

	TAPE=/dev/rmt/0n sh -x /tmp/maketape

	Note that, when installing, the tape can be write-protected
	(i.e. read-only).

If you are upgrading OpenBSD, you also have the option of installing
OpenBSD by putting the new distribution sets somewhere in your
existing file system, and using them from there.  To do that, do
the following:

	Place the distribution sets you wish to upgrade somewhere
	in your current file system tree.  At a bare minimum, you
	must upgrade the "base" binary distribution, and so must
	put the "base52" set somewhere in your file system.  It
	is recommended that you upgrade the other sets, as well.



Preparing your System for OpenBSD Installation:
-----------------------------------------------

If your UltraSPARC machine is somewhat old, it might need a firmware update
before it can be used under OpenBSD. You are advised to try to install
OpenBSD first; if it can't boot or fails mysteriously, you might need to
update your firmware. To do so, check the ``Updating your firmware''
section later in this document.

Your OpenBOOT ROM may need some setup.  You cannot use the security modes
of the OpenBOOT ROM.  Make sure that the ROM security modes are disabled:

    ok setenv security-mode none


Please note that while OpenBSD and Solaris have a reasonable degree of
compatibility between disk labels and filesystems there are some problems
to watch out for during initial installation or when trying to maintain
both OpenBSD and Solaris environments on the same system.

    If the OpenBSD fsck(8) utility is used on a Solaris filesystem, it will
    set OpenBSD "clean flags" and BSD4.4 summary fields in the superblock.
    Solaris does *not* like this and you will have to do a "fsck -b 32" under
    Solaris to access an alternate superblock to repair the filesystem.  You
    should always specify Solaris filesystems with a "pass number" of 0 in
    their /etc/fstab entry to prevent this, and preferably mount them "RO".

    If Solaris fsck is used on an OpenBSD filesystem in the default OpenBSD
    (4.4BSD) format, it will first complain about the superblock and then
    about missing . and .. entries.  Do *not* try to "correct" these
    problems, as attempting to do so will completely trash the filesystem.

    You should avoid using soft updates (option softdep in /etc/fstab)
    on your shared filesystems.  Although untested, it is likely that
    Solaris would be confused by a filesystem with soft update flags
    enabled.

The OpenBSD "Sun Compatible" disklabel has been extended to support 16
partitions, which may be compatible with Solaris, but Solaris only sees
the first 8 partitions and may "lose" information about the extended
partitions.



OpenBSD and Sun bootblocks are similar in concept, though implemented
differently.  The OpenBSD bootblocks are architecture independent and also
understand the extended disk labels with 16 partitions.  You can use Solaris
bootblocks, but remember that OpenBSD bootblocks must be installed with
OpenBSD installboot and Solaris bootblocks with Solaris installboot.

Most of the new Ultras shipped by Sun with a preinstalled Solaris have an
initial specific factory setup of the boot ROM, in order to start up
Solaris WebStart at the first boot; the boot-device variable is set to
disk:f.  Make sure you reset the boot device to its default value:

    ok set-default boot-device

will work for most systems. This can be adapted if you've multiple
systems installed and know what you're doing.

To disable automatic boot use the following command:

    ok setenv auto-boot? false

and then to enable it later use:

    ok setenv auto-boot? true

or on an installed system use the eeprom(8) command:

    # eeprom 'auto-boot?=true'

Updating your firmware:
-----------------------

If OpenBSD does not boot or install properly on your machine, it might need
a firmware update.

Updating your firmware is a dangerous operation which may damage your
hardware. Be sure to carefully follow these instructions and, if in doubt,
please don't do this.

You will need to have a working operating system installed on your machine,
in order to perform the update.  If this is not the case, you might be able
to boot the flash updater software via network, but this has not been tested
and is not supported by Sun.

The firmware update is delivered as a specific patch, depending on your
machine:

	Machine		Patch number
	Blade 100/150	111179
	Enterprise 220R	106455
	Enterprise 250	106503
	Enterprise 420R	109082
	Enterprise 450	106122
	Enterprise 3x00/4x00/5x00/6x00	103346
	Sun Fire 3800/4800/4810/6800	112883
	Sun Fire V480	113034
	Sun Fire V880	112186
	Netra T1 200	111991
	Netra X1	111952
	Ultra 1		104881
	Ultra 1E	104288
	Ultra 2		104169
	Ultra 5/10	106121
	Ultra 30	105930
	Ultra 60	106455
	Ultra 80	109082
	Ultra 450	106122

You can use SunSolve to get the patches by entering the
correct Patch-ID# to the corresponding field at
    http://sunsolve.sun.com/pub-cgi/show.pl?target=patchpage

Follow the patch installation notes very carefully. You will need to open
your machine in order to apply this patch.



Installing the OpenBSD System:
------------------------------

Installing OpenBSD is a relatively complex process, but if you have
this document in hand and are careful to read and remember the
information which is presented to you by the install program, it
shouldn't be too much trouble.

There are several ways to install OpenBSD onto a disk. The easiest way
in terms of preliminary setup is to use the OpenBSD installation
CD-ROM, or an installation floppy (if your machine can boot from floppy).

If your machine is hooked up to a network, try and find a server to
arrange for a diskless setup. This is a convenient way to install on a
machine whose disk does not currently hold a usable operating system.
This is difficult to get set up correctly the first time, but easy to
use afterwards.  (See ``Installing using a diskless setup'' below.)

It is also possible to install OpenBSD "manually" from a running Solaris
system, using the system tools, as well as gunzip; see ``Installing from
Solaris'' below.

Booting from the Installation Media:

Prior to attempting an installation, you should make sure that everything
of value on the target system has been backed up.  While installing OpenBSD
does not necessarily wipe out all the partitions on the hard disk, errors
during the install process can have unforeseen consequences and you will
probably render the system unbootable if you start, but do not complete
the installation.  Having the installation media for the prior installation,
be it a Solaris or OpenBSD CD-ROM or OpenBSD install diskettes, is good
insurance if you want to be able to "go back" for some reason.

After taking care of all that, bring your system down gracefully using
the shutdown(8) and/or halt(8) commands.  This will get you to the monitor
prompt.


Booting from Floppy Disk installation media:

       ok boot floppy bsd

This will cause the kernel contained in the floppy to be booted.
Not all systems are able to boot from floppy; also, Ultra 1, 1E, and 2
systems might need a firmware update to be able to boot from floppy;
refer to the ``Updating your firmware'' section earlier in
this document for details.


Booting From CD-ROM installation media:

	ok boot cdrom

If the boot is successful, you will get a loader version message,
executable sizes, and then the kernel copyright and device probe
messages.  Boot failure modes are typically a lot of CD-ROM drive
activity, but no messages or complaints about magic numbers,
checksums or formats.


Booting from disk:

Boot the miniroot by typing the appropriate command at the PROM:

	ok boot disk:b bsd

If you've loaded the miniroot onto some other disk than the default
drive 0, modify the boot specifier accordingly, keeping in mind the
partition naming a=0, b=1...

	ok boot disk1:b bsd     # example - scsi target 1 or
				# second ide drive


Installing using a diskless setup:

First, you must set up a diskless client configuration on a server. If
you are using an OpenBSD system as the boot-server, have a look at the
diskless(8) manual page for guidelines on how to proceed with this.
If the server runs another operating system, you'll have to consult
documentation that came with it (on SunOS systems, add_client(8) and
the Sun System/Networks administrators guide constitute a good start;
on Solaris systems, share(1M) is a good starting point as well).


Boot your workstation from the server by entering the appropriate `boot'
command at the monitor prompt:

	ok boot net bsd.rd


Installing using the Floppy, CD-ROM, miniroot or netboot procedure:

You should now be ready to install OpenBSD.

The following is a walk-through of the steps you will take while getting
OpenBSD installed on your hard disk.

The installation procedure is designed to gather as many information about
your system setup as possible at the beginning, so that no human interaction
is required as soon as the questions are over.

The order of these questions might be quite disconcerting if you are used to
other installation procedures, including older OpenBSD versions.

If any question has a default answer, it will be displayed in brackets ("[]")
after the question.  If you wish to stop the installation, you may hit
Control-C at any time, but if you do, you'll have to begin the installation
process again from scratch.  Using Control-Z to suspend the process may be a
better option, or at any prompt enter `!' to get a shell, from which 'exit'
will return you back to that prompt (no refresh of the prompt will occur,
though).

	Boot your machine from the installation media as described above.

	It will take a while to load the kernel especially from a floppy
	or slow network connection, most likely more than a minute.  If
	some action doesn't eventually happen, or the spinning cursor has
	stopped and nothing further has happened, either your boot media
	is bad, your diskless setup isn't correct, or you may have
	a hardware or configuration problem.

	Once the kernel has loaded, you will be presented with the
	OpenBSD kernel boot messages.  You will want to read them
	to determine your disks name and geometry.  Its name will
	be something like "sd0" for SCSI drives, or "wd0" for IDE
	drives.
	You will also need to know the device name to tell the
	install tools what disk to install on.  If you cannot read
	the messages as they scroll by, do not worry -- you can get
	at this information later inside the install program.

	After the kernel is done initialization, you will be asked whether
	you wish to do an "(I)nstall" or an "(U)pgrade".  Enter 'I' for a
	fresh install or 'U' to upgrade an existing installation.

	If you are connected with a serial console, you will next be
	asked for your terminal type.
	You should choose the terminal type from amongst those listed.
	(If your terminal type is xterm, just use vt220).

	The first question you will be asked is the system hostname.
	Reply with the name of the system, without any domain part.

	You will now be given an opportunity to configure the network.
	The network configuration you enter (if any) can then be used to
	do the install from another system using HTTP or FTP, and will
	also be the configuration used by the system after the installation
	is complete.

	The install program will give you a list of network interfaces you
	can configure.  For each network interface you select to configure,
	you will be asked for:

	- the symbolic host name to use (except for the first
	  interface setup, which will reuse the host name entered at the
	  beginning of the installation).

	- the IPv4 settings: address and netmask.  If the IP address
	  should be obtained from a DHCP server, simply enter ``dhcp''
	  when asked for the address.

	- the IPv6 settings (address, prefix length, and default router).
	  You may enter ``rtsol'' when asked for the address for the
	  interface to configure automatically via router solicitation
	  messages.

	After all interfaces have been configured, if there have been
	any IPv4 interfaces setup, you will be asked for the IPv4 default
	route.  This step is skipped if you only have one IPv4 interface
	setup, and it is configured with DHCP.

	The install program will also ask you for your DNS domain name,
	and the domain name servers, unless this information has
	already been obtained from a DHCP server during interface setup.

	You will also be presented with an opportunity to do more
	manual configuration.  If you accept, you will be dropped
	to a shell; when you are done, enter `exit' to return to
	the installation program.

	You will then be asked to enter the initial root password
	of the system, twice.
	Although the install program will only check that the two
	passwords match, you should make sure to use a strong password.
	As a minimum, the password should be at least eight characters
	long and a mixture of both lower and uppercase letters, numbers
	and punctuation characters.

	You will then be asked whether you want to start sshd(8) by
	default, as well as ntpd(8).  If you choose to start ntpd(8),
	you will be asked for your ntp server; if you don't have any
	preferred ntp server, press enter to confirm the default
	setting of using the pool.ntp.org servers.

	You will next be asked whether you intend to run the X Window
	System on your machine.  The install program needs to know
	this, to change a configuration setting controlling whether
	the X server will be able to access the xf86(4) driver; it
	is not necessary to answer `y' to this question if you only
	intend to run X client programs on a remote display.
	If you answered `y' to this question, you will get asked
	whether you want to start xdm on boot.

	You will now be given the possibility to setup a user account
	on the forthcoming system.  This user will be added to the
	`wheel' group.

	Enter the desired login name, or `n' if you do not want to
	add a user account at this point.  Valid login names are
	sequences of digits and lowercase letters, and must start
	with a lowercase letter.  If the login name matches this
	criteria, and doesn't conflict with any of the administrative
	user accounts (such as `root', `daemon' or `ftp'), you
	will be prompted with the users descriptive name, as well
	as its password, twice.
	As for the root password earlier, the install program will only
	check that the two passwords match, but you should make sure to
	use a strong password here as well.

	If you have chosen to setup a user account, and you had chosen
	to start sshd(8) on boot, you will be given the possibility to
	disable sshd(8) logins as root.

	You may now be given the opportunity to configure the time zone
	your system will be using (this depends on the installation
	media you are using).
	If the installation program skips this question, do not be
	alarmed, the time zone will be configured at the end
	of the installation.

	The installation program will now tell you which disks it can
	install on, and ask you which it should use.
	Reply with the name of your root disk.

	You will the be asked if you want to use DUID notation in
	/etc/fstab, instead of traditional device names. You are strongly
	advised to use DUIDs, as they allow you to move your disks to
	different controllers, or change their bus identifiers, without
	having to modify /etc/fstab every time your configuration changes.

	Next the disk label which defines the layout of the OpenBSD
	partitions must be set up.  Each file system you want will
	require a separate partition.

	You will be proposed a default partition layout, trying
	to set up separate partitions, disk size permitting.

	You will be given the possibility to either accept the proposed
	layout, or edit it, or create your own custom layout.  These last
	two choices will invoke the disklabel(8) interactive editor,
	allowing you to create your desired layout.

	Within the editor, you will probably start out with only the
	'c' partition of fstype 'unused' that represents the whole disk.
	This partition can not be modified.

	You must create partition 'a' as a native OpenBSD partition, i.e.
	one with "4.2BSD" as the fstype, to hold the root file system.

	In addition to partition 'a' you should create partition 'b' with
	fstype "swap", and native OpenBSD partitions to hold separate file
	systems such as /usr, /tmp, /var, and /home.

	You will need to provide a mount point for all partitions you
	define.  Partitions without mount points, or not of 4.2BSD fstype,
	will neither be formatted nor mounted during the installation.

	For quick help while in the interactive editor, enter '?'.  The
	`z' command (which deletes all partitions and starts with a
	clean label), the `A' command (which performs the automatic
	partition layout) and the `n' command (to change mount points)
	are of particular interest.

	Although the partitions position and size are written in exact
	sector values, you do not need a calculator to create your
	partitions!  Human-friendly units can be specified by adding `k',
	`m' or `g' after any numbers to have them converted to kilobytes,
	megabytes or gigabytes. Or you may specify a percentage of the
	disk size using `%' as the suffix.

	Enter 'M' to view the entire manual page (see the info on the
	``-E'' flag).  To exit the editor enter 'q'.

	After the layout has been saved, new filesystems will be
	created on all partitions with mount points.
	This will DESTROY ALL EXISTING DATA on those partitions.

	After configuring your root disk, the installer will
	return to the list of available disks to configure.

	You can choose the other disks to use with OpenBSD in
	any order, and will get to setup their layout similarly
	to the root disk above. However, for non-root disks,
	you will not be proposed a default partition layout.

	When all your disks are configured, simply hit return
	at the disk prompt.

	After these preparatory steps have been completed, you will be
        able to extract the distribution sets onto your system.  There
        are several install methods supported:
	FTP, HTTP, CD-ROM, tape, or a local disk partition.

	To install via FTP or HTTP:
		To begin an FTP or HTTP install you will need the following
		pieces of information:
		1) Proxy server URL if you are using a URL-based FTP or
		   HTTP proxy (squid, CERN FTP, Apache 1.2 or higher).
		   You need to define a proxy if you are behind a
		   firewall that blocks outgoing FTP or HTTP connections
		   (assuming you have a proxy available to use).
		2) The IP address (or hostname if you configured
		   DNS servers earlier in the install) of an FTP or HTTP
		   server carrying the OpenBSD 5.2 distribution.
		   The installation program will try to fetch a list
		   of such servers; depending on your network settings,
		   this might fail.  If the list could be fetched, it
		   will be displayed, and you can choose an entry from
		   the list (the first entries are expected to be the
		   closest mirrors to your location).
		3) The directory holding the distribution sets.
		   The default value of pub/OpenBSD/5.2/sparc64
		   is almost always correct on FTP servers; for HTTP
		   servers there is no standard location for this.
		4) For FTP installs only, the login and password for the
		   FTP account.  You will only be asked for a password for
		   non-anonymous FTP.

		Then refer to the section named "installation set selection"
		below.

	To install from CD-ROM:
		When installing from a CD-ROM, you will be asked which
		device holds the distribution sets.  This will typically
		be "cd0".  If there is more than one partition on the
		CD-ROM, you will be asked which partition the distribution
		is to be loaded from.  This is normally partition "a".

		You will also have to provide the relative path to the
		directory on the CD-ROM which holds the distribution, for
		the sparc64 this is "5.2/sparc64".

		Then refer to the section named "installation set selection"
		below.
		
	To install from a local disk partition:
		When installing from a local disk partition, you will
		first have to identify which disk holds the distribution
		sets.
		This is normally "wdN" or "sdN", where N is a number.
		Next you will have to identify the partition within that disk
		that holds the distribution; this is a single letter between
		'a' and 'p'.

		You will also have to identify the type of file system
		residing in the partition identified.  Currently, you can
		only install from partitions that have been formatted as the
		Berkeley fast file system (ffs).

		You will also have to provide the relative path to the
		directory on the file system where the distribution sets
		are located.  Note that this path should not be prefixed
		with a '/'.

		Then refer to the next section.

	Installation set selection:
		A list of available distribution sets found on the
		given location will be listed.

		You may individually select distribution sets to install,
		by entering their name, or wildcards (e.g. `*.tgz' or
		`base*|comp*', or `all' to select all the sets (which
		is what most users will want to do).
		You may also enter `abort' to deselect everything and
		restart the selection from scratch, or unselect sets
		by entering their name prefixed with `-' (e.g. `-x*').

		It is also possible to enter an arbitrary filename and
		have it treated as a file set.

		When you are done selecting distribution sets, enter
		`done'.  The files will begin to extract.

	To install from tape:
		Unlike all other installation methods, there is no way
		to know the names of the files on tape.  Because of this,
		it is impossible to check that the files on tape match
		the machine architecture and release of OpenBSD/sparc64.

		Moreover, since tape filenames are not known, the file
		checksums can not be verified.  Use this installation
		method only if there is no better option.

		In order to install from tape, the distribution sets to be
		installed must have been written to tape previously, either
		in tar format or gzip-compressed tar format.

		You will also have to identify the tape device where the
		distribution sets are to be extracted from.  This will
		typically be "nrst0" (no-rewind, raw interface).

		Next you will have to specify how many files have to be
		skipped on the tape.  This number is usually zero.

		The install program will not automatically detect whether
		an image has been compressed, so it will ask for that
		information before starting the extraction of each file.

	After the files have been extracted, you will be given the choice
	to select a new location from which to install distribution sets.
	If there have been errors extracting the sets from the previous
	location, or if some sets have been missing, this allows you to
	select a better source.
		
	Also, if the installation program complains that the distribution
	sets you have been using do not match their recorded checksums, you
	might want to check your installation source (although this can
	happen between releases, if a snapshot is being updated on an FTP
	or HTTP server with newer files while you are installing).

	The last thing you might need to configure, if you did not get
	the chance to earlier, is the time zone your system will be using.
	For this work properly, it is expected that you have installed at
	least the "base52", "etc52", and "bsd" distribution sets.

	The installation program will then proceed to save the system
	configuration, create all the device nodes needed by the installed
	system, and will install bootblocks on the root disk.

	On multiprocessor systems, if the bsd.mp kernel has been installed,
	it will be renamed to `bsd', which is the default kernel the boot
	blocks look for.  The single processor kernel, `bsd', will be
	available as `bsd.sp'.

	Finally, you will be asked whether you would like to install
	non-free firmware files (which can't be tightly integrated to
	the OpenBSD system) on first boot, by invoking fw_update(8) on
	the next boot.

After completing an installation:

Now try a reboot.  (If needed, swap your SCSI IDs first).

The UltraSPARC OpenFirmware will normally load the kernel from the device
and filename as instructed by the ``boot-device'' and ``boot-file''
variables.  If the ``boot-file'' variable is empty, the OpenBSD bootloader
will look for a kernel named ``bsd'', unless a different filename has been
specified in the boot command.  To reset this variable to its default,
empty, value, type the following:

    ok set-default boot-file

On multiprocessor systems, to boot the multiprocessor kernel automatically,
type the following:

    ok setenv boot-file bsd.mp



Congratulations, you have successfully installed OpenBSD 5.2.  When you
reboot into OpenBSD, you should log in as "root" at the login prompt.
You should create yourself an account and protect it and the "root"
account with good passwords.

The install program leaves root an initial mail message.  We recommend
you read it, as it contains answers to basic questions you might have
about OpenBSD, such as configuring your system, installing packages,
getting more information about OpenBSD, sending in your dmesg output
and more.  To do this, run

	mail

and then just enter "more 1" to get the first message.  You quit mail by
entering "q".

Some of the files in the OpenBSD 5.2 distribution might need to be
tailored for your site.  We recommend you run:

	man afterboot

which will tell you about a bunch of the files needing to be reviewed.
If you are unfamiliar with UN*X-like system administration, it's
recommended that you buy a book that discusses it.


Installing from Solaris:

You need a machine running under Solaris to install OpenBSD.  You will
also need at least the following pieces:

  - the *.tgz files you want to install (as a minimum, base52.tgz and
    etc52.tgz)
  - gunzip (GNU gzip) Solaris binary
  - the OpenBSD boot blocks (bootblk and ofwboot)
  - an OpenBSD kernel

All these pieces, except gunzip, are supplied in the OpenBSD/sparc64
distribution.

You need to format and partition the disk using Solaris (since
OpenBSD/sparc64 uses Sun compatible disk labels).  Give yourself adequate
partition sizes.  Here is an example layout:

    solaris# prtvtoc -s /dev/rdsk/c0t1d0s2
    *                          First     Sector    Last
    * Partition  Tag  Flags    Sector     Count    Sector  Mount Directory
           0      2    00          0     80000     79999   /
           1      3    01      80000    256000    335999
           2      5    00          0   4165271   4165270
           3      7    00     336000    100000    435999   /tmp
           4      7    00     436000    100000    535999   /var
           5      7    00     536000    400000    935999   /var/tmp
           6      4    00     936000   3229271   4165270   /usr

Use Solaris to newfs the partitions which will have filesystems on them.
(OpenBSD's filesystem format is almost identical to Solaris.)

    solaris# newfs /dev/rdsk/c0t1d0s0
    [... lots of output]

Repeat for any other partition (in this example, /dev/rdsk/c0t1d0s3,
/dev/rdsk/c0t1d0s4, /dev/rdsk/c0t1d0s5 and /dev/rdsk/c0t1d0s6).

NOTE: If you are able to, there is a performance benefit from
newfs'ing using OpenBSD.  If you newfs using the OpenBSD newfs command,
be sure to use the -O flag for your / partition, so that newfs will
use the 4.3BSD filesystem format, rather than the new 4.4BSD filesystem
format.  If you forget, you will not be able to boot -- the Solaris boot
blocks do not understand the extended 4.4BSD filesystem format.

Mount those partitions in a tree formation, under /mnt; ie:

    solaris# df -k
    Filesystem            kbytes    used   avail capacity  Mounted on
    [...]
    /dev/dsk/c0t1d0s0      38427       0   38427     0%    /mnt
    /dev/dsk/c0t1d0s3      48249       0   48249     0%    /mnt/tmp
    /dev/dsk/c0t1d0s4      48249       0   48249     0%    /mnt/var
    /dev/dsk/c0t1d0s5     193536       0  193536     0%    /mnt/var/tmp
    /dev/dsk/c0t1d0s6    1564024       0 1564024     0%    /mnt/usr

Place the boot blocks in /mnt (your new root partition), and use the Solaris
command "installboot" to make it work.
The installboot man page says to do something like this:

    solaris# cp bootblk ofwboot /mnt
    solaris# sync; sync
    solaris# /usr/sbin/installboot /mnt/bootblk /dev/rdsk/c0t1d0s0

You can now extract the provided "*.tgz" files onto your disk.

    solaris# ls -FC
    base52.tgz     etc52.tgz      xbase52.tgz     xshare52.tgz
    bsd            game52.tgz     xfont52.tgz
    comp52.tgz     man52.tgz      xserv52.tgz
    solaris# gunzip < base52.tgz | (cd /mnt; tar xvpf -)
    [...] for each set

And finally copy the OpenBSD kernel onto your disk.

    solaris# cp bsd /mnt/bsd

The GNU gunzip program is not distributed as part of Solaris, but may be
present in your /usr/local/bin.  If not, you will need to obtain it from a
GNU archive and install before proceeding.

After the files have been extracted, set up /mnt/etc/fstab to match
your actual disk layout.  (Minus the "/mnt" component of each path, of
course :-)

Now proceed to reboot the machine and the customize your installation.


Net Boot or Diskless Setup Information:

The set up is similar to the diskless setup, but not identical, because
the Sun setup assumes that the bootblocks load a kernel image, which then
uses NFS to access the exported root partition, while the OpenBSD bootblocks
use internal NFS routines to load the kernel image directly from the
exported root partition.

Please understand that no one gets this right the first try, since
there is a lot of setup and all the host daemons must be running and
configured correctly.  If you have problems, extract the diskless(8)
manpage, find someone who's been through it before and use the host
syslog and tcpdump(8) to get visibility of what's happening (or not).

Your UltraSPARC expects to be able to download a second stage bootstrap
program via TFTP after having acquired its IP address through RevARP when
instructed to boot "over the net". It will look for a filename composed of
the machine's IP address. For example, a machine which has been assigned IP
address 130.115.144.11 will make a TFTP request for `8273900B'.
Normally, this file is a symbolic link to an appropriate second-stage
boot program, which should be located in a place where the TFTP daemon
can find it (remember, many TFTP daemons run in a chroot'ed environment).

You can find the boot program in `/usr/mdec/boot' in the OpenBSD/sparc64
distribution.

After the boot program has been loaded into memory and given control by
the PROM, it starts locating the machine's remote root directory through
the BOOTPARAM protocol. First a BOOTPARAM WHOAMI request is broadcast
on the local net. The answer to this request (if it comes in) contains
the client's name. This name is used in the next step, a BOOTPARAM GETFILE
request -- sent to the server that responded to the WHOAMI request --
requesting the name and address of the machine that will serve the client's
root directory, as well as the path of the client's root on that server.

Finally, this information (if it comes in) is used to issue a REMOTE MOUNT
request to the client's root filesystem server, asking for an NFS file
handle corresponding to the root filesystem. If successful, the boot
program starts reading from the remote root filesystem in search of the
kernel which is then read into memory.

You will want export the miniroot52.fs filesystem to the client.  You
can dd this filesystem image to some spare partition, mount and export
that partition, or use tar to copy the contents to a more convenient spot.

Alternatively you can build a bootable partition from the distribution sets
as follows:

Unpack `base52.tgz' and `etc52.tgz' on the server in the root directory
for your target machine. If you elect to use a separately NFS-mounted
filesystem for `/usr' with your diskless setup, make sure the "./usr" base
files in base52.tgz end up in the correct location. One way to do this is
to temporarily use a loopback mount on the server, re-routing <root>/usr to
your server's exported OpenBSD "/usr" directory. Also put the kernel and
the install/upgrade scripts into the root directory.

A few configuration files need to be edited:

	<root>/etc/hosts
		Add the IP addresses of both server and client.

	<root>/etc/myname
		This files contains the client's hostname; use the same
		name as in <root>/etc/hosts.

	<root>/etc/fstab
		Enter the entries for the remotely mounted filesystems.
		For example:
			server:/export/root/client       /     nfs  rw 0 0
			server:/export/exec/sparc64.OpenBSD /usr  nfs  rw 0 0

Now you must populate the `/dev' directory for your client.  If the server
does not run OpenBSD you might save the MAKEDEV output:

	eo=echo ksh MAKEDEV all > all.sh

and then tailor it for your server operating system before running it.  Note
that MAKEDEV is written specifically for ksh, and may not work on any other
Bourne shell.

There will be error messages about unknown users and groups.  These errors are
inconsequential for the purpose of installing OpenBSD.  However, you may
want to correct them if you plan to use the diskless setup regularly.  In that
case, you may re-run MAKEDEV on your OpenBSD machine once it has booted.



Upgrading a previously-installed OpenBSD System:
------------------------------------------------

Warning! Upgrades to OpenBSD 5.2 are currently only supported from the
immediately previous release.  The upgrade process will also work with older
releases, but might not execute some migration tasks that would be necessary
for a proper upgrade.

The best solution, whenever possible, is to backup your data and reinstall
from scratch. As a minimum, if the toolchain (the ``comp'' set) was installed,
you should remove all files within /usr/include before attempting to
upgrade.

To upgrade OpenBSD 5.2 from a previous version, start with the general
instructions in the section "Installing OpenBSD".

Boot from CD-ROM, the miniroot, or an installation floppy.
When prompted, select the (U)pgrade option rather than the (I)nstall
option at the prompt in the install process.

You will be presented with a welcome message and asked if you really wish
to upgrade.

The upgrade script will ask you for the existing root partition, and
will use the existing filesystems defined in /etc/fstab to install the
new system in.  It will also use your existing network parameters.

From then, the upgrade procedure is very close to the installation
procedure described earlier in this document.  Note that the upgrade
procedure will not let you pick neither the ``etc52.tgz'' nor the
``xetc52.tgz'' sets, so as to preserve your files in `/etc' which
you are likely to have customized since a previous installation.

However, it is strongly advised that you unpack the etc52.tgz and
xetc52.tgz sets in a temporary directory and merge changes by hand, or
with the help of the sysmerge(8) helper script, since all components of
your system may not function correctly until your files in `/etc' are
updated.



Getting source code for your OpenBSD System:
--------------------------------------------

Now that your OpenBSD system is up and running, you probably want to get
access to source code so that you can recompile pieces of the system.

A few methods are provided.  If you have an OpenBSD CD-ROM, the source
code is provided.  Otherwise, you can get the pieces over the Internet
using anonymous CVS, CVSync or FTP.  For more information, see

	http://www.OpenBSD.org/anoncvs.html
	http://www.OpenBSD.org/cvsync.html
	http://www.OpenBSD.org/ftp.html


Using online OpenBSD documentation:
-----------------------------------

Documentation is available if you first install the manual pages
distribution set.  Traditionally, the UN*X "man pages" (documentation)
are denoted by 'name(section)'.  Some examples of this are

	intro(1),
	man(1),
	apropos(1),
	passwd(1),
	passwd(5) and
	afterboot(8).

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

The 'man' command is used to view the documentation on a topic, and is
started by entering 'man [section] topic'.  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
least-numbered section name will be displayed.  For instance, after
logging in, enter

	man passwd

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

	man 5 passwd

instead.

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

	apropos subject-word

where "subject-word" is your topic of interest; a list of possibly
related man pages will be displayed.


Adding third party software; ``packages'' and ``ports'':
--------------------------------------------------------

As complete as your OpenBSD system is, you may want to add any of several
excellent third party software applications.  There are several ways to do
this.  You can:

1) Use the OpenBSD ``package'' collection to grab a pre-compiled
   and tested version of the application for your hardware.

2) Use the OpenBSD ``ports'' collection to automatically get any
   needed source file, apply any required patches, create the
   application, and install it for you.

3) Obtain the source code and build the application based
   upon whatever installation procedures are provided with the
   application.

If you purchased the OpenBSD CD-ROM set you already have several popular
``packages'', and the ``ports'' collection.

Instructions for installing applications from the various sources using
the different installation methods follow.

You should also refer to the packages(7) manual page.

Installing applications from the CD-ROM package collection:

	The OpenBSD CD-ROM ships with several applications pre-built
	for various hardware architectures.  The number of applications
	vary according to available disk space.  Check the directory
	5.2/packages/sparc64 to see which packages are available for
	your hardware architecture.  That directory will be on the same
	CD-ROM containing the OS installation files for your architecture.

	To install one or more of these packages you must:
	1) become the superuser (root).
	2) mount the appropriate CD-ROM.
	3) use the ``pkg_add'' command to install the software.

	Example (in which we use su(1) to get superuser privileges, thus
	you have to be in group "wheel", see the manual page for su(1)).

    $ su
    Password: <enter your root password>
    # mkdir -p /cdrom
    # mount /dev/cd0a /cdrom
    # pkg_add /cdrom/5.2/packages/sparc64/<package-name>
    # <add more packages if desired>
    # umount /cdrom

	Package names are usually the application name and version
	with .tgz appended, e.g. emacs-21.3.tgz

Installing applications from the ftp.OpenBSD.org package collection:

	All available packages for your architecture have been placed on
	ftp.OpenBSD.org in the directory pub/OpenBSD/5.2/packages/sparc64/
	You may want to peruse this to see what packages are available.  The
	packages are also on the OpenBSD FTP mirror sites.  See

		http://www.OpenBSD.org/ftp.html

	for a list of current FTP mirror sites.

	Installation of a package is very easy.
	1) become the superuser (root)
	2) use the ``pkg_add'' command to install the software

	``pkg_add'' is smart enough to know how to download the software
	from the OpenBSD FTP server.  Example:

    $ su
    Password: <enter your root password>
    # pkg_add \
      ftp://ftp.OpenBSD.org/pub/OpenBSD/5.2/packages/sparc64/emacs-21.3.tgz

Installing applications from the CD-ROM ports collection:

	The CD-ROM ``ports'' collection is a set of Makefiles, patches,
	and other files used to control the building and installation
	of an application from source files.

	Creating an application from sources can require a lot of
	disk space, sometimes 50 megabytes or more.  The first step is
	to determine which of your disks has enough room.  Once you've
	made this determination, read the file PORTS located on the
	CD-ROM which contains the ports tree.

	To build an application you must:

	1) become the superuser (root)
	2) have network access, or obtain the actual source files by
	   some other means.
	3) cd to the ports directory containing the port you wish
	   to build.  To build samba, for example, where you'd
	   previously copied the ports files into the /usr/ports
	   directory: cd /usr/ports/net/samba
	4) make
	5) make install
	6) make clean

Installing applications from the OpenBSD ports collection:

	See http://www.OpenBSD.org/faq/ports/ports.html for current
	instructions on obtaining and installing OpenBSD ports.

	You should also refer to the ports(7) manual page.

Installing other applications:

	If an OpenBSD package or port does not exist for an application
	you're pretty much on your own.  The first thing to do is ask
	<ports@OpenBSD.org> if anyone is working on a port -- there may
	be one in progress.  If no such port exists, you might want to
	look at the FreeBSD ports or NetBSD pkgsrc for inspiration.

	If you can't find an existing port, try to make your own and
	feed it back to OpenBSD.  That's how our ports collection grows.
	Some details can be found in the OpenBSD Porter's Handbook at
	http://www.openbsd.org/faq/ports/
	with more help coming from the mailing list, <ports@OpenBSD.org>.



Administrivia:
--------------

There are various mailing lists available via the mailing list
server at <majordomo@OpenBSD.org>.  To get help on using the mailing
list server, send mail to that address with an empty body, and it will
reply with instructions.  There are also two OpenBSD Usenet newsgroups,
comp.unix.bsd.openbsd.announce for important announcements and
comp.unix.bsd.openbsd.misc for general OpenBSD discussion.

More information about the various OpenBSD mailing list and proper
netiquette is available at

	http://www.OpenBSD.org/mail.html

To report bugs, use the 'sendbug' command shipped with OpenBSD,
and fill in as much information about the problem as you can.  Good
bug reports include lots of details.  Additionally, bug reports can
be sent by mail to:

	bugs@OpenBSD.org

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

For more information about reporting bugs, see

	http://www.OpenBSD.org/report.html