INSTALLATION NOTES for OpenBSD/amiga 2.9


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 ipf, ipnat, and
bridging are also standard.  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.

To integrate more smoothly in other environments, OpenBSD 2.9 also
provides several binary emulation subsystems (which includes
iBCS2, Linux, OSF/1, SunOS, SVR4, Solaris, and Ultrix compatibility),
aiming at making the emulation as accurate as possible so that it is
transparent to the user.

Many new user programs and device drivers have been added in OpenBSD
2.9, as well, bringing it closer to our goal of supplying a complete
and modern UN*X-like environment.  Tools like perl and an improved ksh
are standard, as are numerous other useful tools.

Because OpenBSD is from Canada, the export of Cryptography pieces
(such as SSH, IPSEC, and KerberosIV) 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.)


OpenBSD/amiga is a port to the Amiga machines manufactured by
Commodore.  The ports supports a wide range of hardware and peripherals,
with all the stability and security you can expect from OpenBSD.


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

This is a list of currently known ftp servers:

Argentina:

ftp://ftp.openbsd.org.ar/pub/OpenBSD

Australia:

ftp://ftp.aba.net.au/pub/OpenBSD ==
	ftp://ftp.au.openbsd.org/pub/OpenBSD
ftp://ftp.it.net.au/mirrors/OpenBSD
ftp://ftp.planetmirror.com/pub/OpenBSD
ftp://ftp.wiretapped.net/pub/OpenBSD
ftp://mirror.aarnet.edu.au/pub/OpenBSD

Austria:

ftp://gd.tuwien.ac.at/opsys/OpenBSD

Belgium:

ftp://openbsd.rug.ac.be/pub/OpenBSD

Canada:

ftp://openbsd.sunsite.ualberta.ca/pub/OpenBSD ==
	ftp://ftp.openbsd.org/pub/OpenBSD
	ftp://ftp.ca.openbsd.org/pub/OpenBSD
	ftp://ftp1.ca.openbsd.org/pub/OpenBSD

China (Hong Kong):

ftp://ftp.shellhung.org/pub/OpenBSD

France:

ftp://ftp.lip6.fr/pub/OpenBSD == 
	ftp://ftp.fr.openbsd.org/pub/OpenBSD
ftp://ftp.grolier.fr/pub/OpenBSD ==
	ftp://ftp2.fr.openbsd.org/pub/OpenBSD
ftp://ftp.bsdfr.org/pub/OpenBSD ==
	ftp://ftp3.fr.openbsd.org/pub/OpenBSD

Germany:

ftp://ftp.fu-berlin.de/unix/OpenBSD ==
	ftp://ftp.de.openbsd.org/unix/OpenBSD
ftp://ftp.leo.org/pub/OpenBSD ==
	ftp://ftp2.de.openbsd.org/unix/OpenBSD
ftp://ftp.fh-wolfenbuettel.de/pub/os/openbsd
ftp://ftp.freenet.de/pub/ftp.openbsd.org/pub/OpenBSD
ftp://ftp.gigabell.net/pub/OpenBSD

Greece:

ftp://filoktitis.noc.uoa.gr/pub/OpenBSD
ftp://ftp.duth.gr/pub/OpenBSD

Hungary:

ftp://ftp.fsn.hu/pub/OpenBSD

Ireland:

ftp://ftp.esat.net/pub/OpenBSD

Italy:

ftp://ftp.volftp.mondadori.com/mirror/openbsd

Japan:

ftp://ftp.dti.ad.jp/pub/OpenBSD ==
	ftp://ftp.jp.openbsd.org/OpenBSD
	ftp://ftp2.jp.openbsd.org/OpenBSD
ftp://ftp.kddlabs.co.jp/OpenBSD
ftp://ftp.netlab.is.tsukuba.ac.jp/pub/os/OpenBSD
ftp://mirror.nucba.ac.jp/mirror/OpenBSD

The Netherlands:

ftp://ftp.calyx.nl/pub/OpenBSD
ftp://ftp.nl.uu.net/pub/OpenBSD
ftp://ftp.nluug.nl/pub/OpenBSD

New Zealand:

ftp://mirror.qsi.net.nz/pub/OpenBSD ==
	ftp://ftp.nz.openbsd.org/pub/OpenBSD

Norway:

ftp://ftp.inet.no/pub/OpenBSD
ftp://sunsite.uio.no/pub/OpenBSD

Romania:

ftp://quasar.uvt.ro/pub/OpenBSD

Russia:

ftp://ftp.chg.ru/pub/OpenBSD
ftp://ftp.radio-msu.net/pub/OpenBSD
ftp://vell.nsc.ru/pub/OpenBSD

Saudi Arabia:

ftp://ftp.isu.net.sa/pub/mirrors/ftp.openbsd.org/pub/OpenBSD

South Korea:

ftp://ftp.snu.ac.kr/pub/BSD/OpenBSD

Spain:

ftp://ftp.rediris.es/mirror/OpenBSD

Sweden:

ftp://ftp.stacken.kth.se/pub/OpenBSD ==
	ftp://ftp.se.openbsd.org/pub/OpenBSD
	ftp://ftp1.se.openbsd.org/pub/OpenBSD
ftp://ftp.luth.se/pub/OpenBSD
ftp://ftp.sunet.se/pub/OpenBSD

Switzerland:

ftp://sunsite.cnlab-switch.ch/pub/OpenBSD

Taiwan:

ftp://openbsd.csie.nctu.edu.tw/pub/OpenBSD

Thailand:

ftp://ftp.riubon.ac.th/pub/OpenBSD ==
	ftp://ftp.th.openbsd.org/pub/OpenBSD
ftp://ftp.kmitl.ac.th/pub/OpenBSD

United Kingdom:

ftp://ftp.knowledge.com/pub/mirrors/OpenBSD
ftp://ftp.plig.org/pub/OpenBSD
ftp://sunsite.org.uk/Mirrors/ftp.openbsd.org/pub/OpenBSD

USA:

ftp://openbsd.cs.colorado.edu/pub/OpenBSD ==
	ftp://ftp.usa.openbsd.org/pub/OpenBSD
	ftp://ftp3.usa.openbsd.org/pub/OpenBSD
	ftp://ftp6.usa.openbsd.org/pub/OpenBSD
ftp://ftp.eecs.umich.edu/pub/OpenBSD ==
	ftp://ftp1.usa.openbsd.org/pub/OpenBSD
	ftp://ftp4.usa.openbsd.org/pub/OpenBSD
ftp://ftp.cerias.purdue.edu/pub/os/OpenBSD ==
	ftp://ftp7.usa.openbsd.org/pub/os/OpenBSD
ftp://archive.progeny.com/OpenBSD
ftp://carroll.cac.psu.edu/pub/OpenBSD
ftp://download.sourceforge.net/pub/mirrors/OpenBSD
ftp://ftp.geto.net/OpenBSD
ftp://ftp.op.net/pub/OpenBSD
ftp://ftp.src.uchicago.edu/pub/OpenBSD
ftp://ftp.tux.org/bsd/openbsd
ftp://ftp.twoguys.org/pub/OpenBSD
ftp://gandalf.neark.org/pub/distributions/OpenBSD
ftp://mirror.csit.fsu.edu/pub/OpenBSD
ftp://mirrors.rcn.net/pub/OpenBSD
ftp://rt.fm/pub/OpenBSD

As well, the file ftp://ftp.openbsd.org/pub/OpenBSD/2.9/ftplist
contains a list which is continually updated.  If you wish to become a
distribution site for OpenBSD, contact miod@openbsd.org.





OpenBSD 2.9 Release Contents:
-----------------------------

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

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

.../2.9/amiga/
		INSTALL.amiga	Installation notes; this file.

		CKSUM		Output of the cksum(1) and md5(1) programs
		MD5		usable for verification of the correctness
				of downloaded files.

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

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

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

		*.tgz		amiga binary distribution sets;
				see below.

		utils/		Miscellaneous amiga installation
				utilities; see installation section, below.

Installation/upgrade miniroot file system:

	This file contains a BSD root file system setup to help
	you install or upgrade the rest of OpenBSD.  This includes
	formatting root and /usr partitions in the case of an install
	or converting existing ones if doing an upgrade (this conversion
	is only needed if you are coming from a real old NetBSD world),
	then mounting your root and /usr partitions and getting
	ready to extract (and possibly first fetching) the distribution
	sets.  There is enough on this file system to allow you to
	make a slip or ppp connection, configure an Ethernet, mount an
	NFS file system or ftp.  You can also load distribution sets from
	a SCSI tape or from one of your existing AmigaDOS partitions.

	This file is named "miniroot29.fs".


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

	base29	 The OpenBSD/amiga 2.9 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.
		 [ 19.3M gzipped, 61.4M uncompressed ]

	comp29	 The OpenBSD/amiga Compiler tools.  All of the tools
		 relating to C, C++, and FORTRAN (yes, there are two!) 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.
		 [ 13.1M gzipped, 30.6M uncompressed ]

	etc29	 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.)
		 [ 982.6K gzipped, 3.3M uncompressed ]

	game29	 This set includes the games and their manual pages.
		 [ 2.6M gzipped, 6.4M uncompressed ]

	man29	 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.
		 [ 4.8M gzipped, 18.4M uncompressed ]

	misc29	 This set includes the system dictionaries (which are
		 rather large), the typesettable document set, and
		 man pages for other architectures which happen to be
		 installed from the source tree by default.
		 [ 1.6M gzipped, 5.5M uncompressed ]

	xbase29  This set includes the base X distribution.  This includes
		 programs, headers, libraries, configuration files.
		 [ 3.6M gzipped, 10.0M uncompressed ]

	xshare29 This set includes all text files equivalent between
		 all architectures.
		 [ 1.5M gzipped, 8.5M uncompressed ]

	xfont29  This set includes all of the X fonts.
		 [ 6.0M gzipped, 7.3M uncompressed ]

	xserv29  This set includes all of the X servers.
		 [ 2.6M gzipped, 6.3M uncompressed ]



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

OpenBSD/amiga 2.9 runs on any amiga that has a 68020, 68030, 68040 or
68060 CPU with some form of FPU and MMU.  It should also run on
MacroSystem's DraCo computer.  The minimal configuration requires 4M of
RAM and about 55M 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.  (4M of RAM will actually allow you to compile, however it
won't be speedy.  X really isn't usable on a 4M system.)

Here is a table of recommended HD partition sizes for a full install:
	partition:	advise,	with X,	needed,	with X
	root (/)	 30M	 30M	25M	 25M
	user (/usr)	210M    245M   140M     175M
	/usr/local      depends on what extra software you want
	swap		---- 1MB for every MB RAM ----
			-- but the sum of swap and ---
			- RAM should be at least 16 --

As you may note the recommended size of /usr is 70M greater than
needed. This is to leave room for a kernel source and compile tree
as you will probably want to compile your own kernel. (GENERIC is
large and bulky to accommodate all people).

Starting with OpenBSD 2.7, you should be able to leave /usr mounted ro
on production machines, and use a separate /usr/local partition for
packages.


If you only have 4M of fast memory, you should make your swap partition
larger, as your system will be doing much more swapping.

Supported devices include:
	A4000/A1200 IDE controller.
	ISA IDE & ATAPI with a supported ISA bridge.
		[Note: With single ATAPI device IDE busses, the
		ATAPI device should be set to SLAVE.]
	SCSI host adapters:
		33c93 based boards: A2091, A3000 and GVP series II.
		53c80 based boards: 12 Gauge, IVS, Emplant and
				    Wordsync/Bytesync.
		53c710 based boards: A4091, Magnum, Warp Engine, Zeus
				     and DraCo.
		FAS216 based boards: FastLane Z3, Blizzard.
	Video controllers:
		ECS, AGA and A2024 built in on various amigas
		Retina Z2 and Retina Z3.
		Picasso II.
		GVP Spectrum.
		Piccolo.
		A2410.
		Cybervision 64. (Not Cybervision 64/3D)
		oMnibus.
		Domino.
		Merlin.
	Ethernet controllers:
		A2065.
		Hydra.
		ASDG.
		A4066.
		Ariadne (currently broken).
		AriadneII.
		Quicknet.
		Via a supported ISA bridge:
			NE[12]000, SMC/WD 8003/8013/8216 and 3COM 3c503.
		
	Arcnet controllers:
		A2060.
	Tape drives:
		Most SCSI tape drives.
	CD-ROM drives:
		Most SCSI CD-ROM drives.
	Serial ports:
		Amiga serial port.
		DraCo serial port.
		MultiFaceCard II and III.
		A2232.
		PC COM ports attached to a supported ISA bridge.
	Parallel ports:
		Amiga parallel port.
		PC LPT ports attached to a supported ISA bridge.
	ISA bridges:
		The GoldenGate Bus+ (aka GG2).
		The CrossLink.
	Amiga floppy drives.
	Amiga mouse.
	Amiga joystick.

If its not on this list, there is no support for it in this release.



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

Installation is supported from several media types, including:

	AmigaDOS Fast file system partitions
	FFS partitions
	Tape
	Remote NFS partition
	FTP
	HTTP

The installation program is run under a minimal OpenBSD environment
provided by one of two means: a ramdisk or a miniroot filesystem.
We recommend using the ramdisk if your machine is big enough (at
least 6MB of fastmem is required), otherwise a miniroot filesystem
needs to be transferred to the OpenBSD swap partition.  This can be
done from AmigaDOS in the case of a new install or upgrade, or from
OpenBSD when doing an upgrade.  See the "Preparing your System for
OpenBSD Installation" section for details.

The steps necessary to prepare the distribution sets for
installation depend on which method of installation you choose.
The various methods are explained below.  However, for all methods
you need to transfer a OpenBSD kernel binary to your AmigaDOS
partition, optionally you must also get the miniroot image there
for later transfer to your swap partition as explained elsewhere.
For ramdisk installs you need to get both the bsd and bsd.rd
kernel images, and for miniroot installs you need bsd and the
miniroot29.fs image.

To prepare for installing via an AmigaDOS partition:

	To install OpenBSD from an AmigaDOS partition, you need to
	get the OpenBSD distribution sets you wish to install
	on your system on to an AmigaDOS fast file system partition.
	All of the set_name29.tgz pieces can be placed in a single
	directory instead of separate ones for each distribution set.
	This will also simplify the installation work later on.

	Note where you place the files, you will need this later.
	Also, it might be a good idea to type down the AmigaDOS
	partition structure of the disk you put these files on.  In
	the context of the install program you will only be able to
	identify the partition by starting sector (block) number
	and/or size.  The partition names are *not* available.

	Once you have done this, you can proceed to the next
	step in the installation process, preparing your hard disk.

To prepare for installing via a tape:

	To install OpenBSD from a tape, you need to somehow
	get the OpenBSD filesets you wish to install on
	your system on to the appropriate kind of tape,
	in tar format.

	If you're making the tape on a UN*X system, the easiest
	way to do so is:

		tar cvf <tape_device> <files>

	where "<tape_device>" is the name of the tape device
	that describes the tape drive you're using (possibly
	something like /dev/nrst0, but we make no guarantees 8-).
	If you can't figure it out, ask your system administrator.
	"<files>" are the names of the "set_name29.tgz" files
	which you want to be placed on the tape.

	Once you have done this, you can proceed to the next
	step in the installation process, preparing your hard disk.

To prepare for installing via NFS:

	Place the OpenBSD software you wish to install into
	a directory on an NFS server, and make that directory
	mountable by the machine which you will be installing
	OpenBSD on.  This will probably require modifying the
	/etc/exports file of the NFS server and resetting
	mountd, acts which will require superuser privileges.
	Note the numeric IP address of the NFS server and of
	the router closest to the new OpenBSD machine,
	if the NFS server is not on a network which is
	directly attached to the OpenBSD machine.

	Once you have done this, you can proceed to the next
	step in the installation process, preparing your hard disk.

To prepare for installing via FTP/HTTP:

	The preparations for this method of installation
	are easy: all you have to do is make sure that
	there's some FTP- or website from which you can
	retrieve the OpenBSD installation when it's time to
	do the install.  You should know the numeric IP
	address of that site, and the numeric IP address of
	your nearest router if one is necessary

	Once you have done this, you can proceed to the next
	step in the installation process, preparing your hard disk.

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, you must 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
	"base29.tgz" set somewhere in your file system.  If you wish,
	you can do the other sets, as well, but you should NOT upgrade
	the "etc" distribution; the "etc" distribution contains system
	configuration files that you should review and update by hand.

	Once you have done this, you can proceed to the next step in
	the upgrade process, actually upgrading your system.



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

You will need an AmigaDOS hard drive prep tool to prepare you hard
drives for use with OpenBSD/amiga.  HDToolBox is provided with the
system software and on floppy installation disks since Release 2.0
of AmigaDOS so we will provide instructions for its use.

Preparing your hard disk with HDToolBox:

	If you intend to use a harddisk larger than 4 Gb, or partitions 
	larger than 2Gb be advised to either get HDToolBox for AmigaDOS 3.5 
	or a third party harddisk preparation tool (such as HdInstTools) 
	from Aminet, together with the appropriate patches from 
	www.amiga.com to let AmigaDOS see the full size of the drive.

	A full explanation of HDToolBox can be found with your
	AmigaDOS manuals and is beyond the scope of this document.

	Note that you will be modifying your HD. If you mess something 
	up here you could lose *EVERYTHING* on all the drives that 
	you configure.  You are therefore advised to:

		Write down your current configuration.  Do this
		by examining each partition on the drive and the
		drives parameters (from Change drive type.)

		Back up all partitions you want to keep.

	What you need to do is partition your drives; creating at least
	root, swap and /usr partitions and possibly some more for
	/tmp, /var, /home or others of your own choice.  (The root and
	swap partitions must be on the same drive for your initial
	installation. You can use other configurations after building a
	customized kernel once your system is running.)  Partitioning is
	traditionally an area of great confusion and disagreement, and
	religion plays a large role in most advice you'll get.  The
	author of this paragraph is a fan of large and few partitions,
	normally one per disk, unless it's the root disk, where I tend
	to have /, swap, /tmp, /var & /usr.  I must admit that I step
	aside from my normal rules of thumb very often due to the context
	the machine will work in.

	This should be done as the HDToolBox manual describes.  One thing
	to note is that if you are not using a Commodore controller you
	will need to specify the device your SCSI controller uses e.g.
	if you have a Warp Engine you would:

		from cli,
			hdtoolbox warpdrive.device

		from wb set the tooltype,
			SCSI_DEVICE_NAME=warpdrive.device

	The important things you need to do above and beyond normal
	partitioning includes (from Partition Drive section):

		Marking all OpenBSD partitions as non-bootable.

		Changing the file system parameters of the partitions
		to OpenBSD ones.  This must be done from the
		partitioning section and `Advanced options' must
		be enabled.  To Make the needed changes:

		- Click the `Adv. Options' button
		- Click the `Change filesystem' button

		- Choose `Custom File System'
		- Turn off `Automount' if on.
		- Set the dostype to one of these three choices:

			root partition  : 0x4e425207 ("NBR\7")
			swap partition  : 0x4e425301 ("NBS\1")
			other partitions: 0x4e425507 ("NBU\7")

		Here `other' refers to other partitions you will
		format for reading and writing under OpenBSD (e.g.
		/usr)

		Make sure you hit the return key to enter this value
		as some versions of HDToolBox will forget your entry
		if you don't.

		- Turn custom boot code off
		- Set Reserved Blocks start and end to 0.
		- Click Ok.

		Mask and maxtransfer are not used with OpenBSD.

		Until you compile your own kernel your swap partition
		must exist on the drive that also holds your root
		partition.

	
	Once this is done OpenBSD/amiga will be able to recognize your
	disks and which partitions it should use.

Choosing installation root filesystem type:

	The OpenBSD/amiga operating system can be installed using two
	different root filesystems: ramdisk or miniroot.  The ramdisk
	is strongly recommended as it requires less preparatory work.
	However the ramdisk kernel requires that your system has at
	least 6MB of fastmem.  The miniroot requires less (installs on
	a 4MB system should be possible) and has tools to make SLIP or
	PPP connections, which the ramdisk doesn't, however you need
	to be an experienced user to make use of these as the install
	scripts doesn't deal with them.  Furthermore the miniroot
	install requires you to do the preparation described in the
	following paragraph.  To use the ramdisk install you should get
	the bsd.rd kernel as well as the standard bsd one, and *do*
	skip the next section!

Transferring the miniroot filesystem:

	The OpenBSD/amiga installation or upgrade can use a "miniroot"
	filesystem which is installed on the partition used by OpenBSD
	for swapping.

	Once the hard disk has been prepared for OpenBSD, the miniroot
	filesystem (miniroot29.fs) is transferred to the swap partition
	configured during the hard disk prep (or the existing swap
	partition in the case of an upgrade).  The xstreamtodev utility
	provided in the "amiga/utilities" directory can be used on
	AmigaDOS to transfer the filesystem for either a new installation
	or an upgrade.  The filesystem can also be transferred on an
	existing OpenBSD (or NetBSD) system for an update by using dd.
	This should only be done after booting the former OS into single-
	user state.  It may also be possible to shutdown to single-user,
	providing that the single-user state processes are not using the
	swap partition.

	On AmigaDOS, the command:
		xstreamtodev --input=miniroot29.fs --rdb-name=<swap partition>
	where <swap partition> is the name you gave to the OpenBSD
	partition to be used for swapping.  If xstreamtodev is unable to
	determine the SCSI driver device name or the unit number of the
	specified partition, you may also need to include the option
	"--device=<driver.name>" and/or "--unit=<SCSI unit number>".

	To transfer the miniroot using an older BSD, you should be booted
	up in single user state on the current system, or use the
	"shutdown now" command to shutdown to single-user state.  Then
	copy the miniroot using dd:
		dd if=miniroot29.fs of=/dev/rsdXb
	where /dev/rsdXb should be the device path of the swap partition
	your system is configured to use.  Once the file is copied,
	reboot back to AmigaDOS to boot the new OpenBSD kernel.  NOTE:
	the release kernel is a "generic" kernel, and requires that the
	swap partition be on the same device as the root partition.



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.

Before you begin, you should know the geometry of your hard disk, i.e.
the sector size (note that sector sizes other than 512 bytes are not
currently supported), the number of sectors per track, the number of
tracks per cylinder (also known as the number of heads), and the
number of cylinders on the disk.  The OpenBSD kernel will try to
discover these parameters on its own, and if it can it will print them
at boot time.  If possible, you should use the parameters it prints.
(You might not be able to because you're sharing your disk with
another operating system, or because your disk is old enough that the
kernel can't figure out its geometry.)

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

	If you have a small machine (less than 6MB of fast RAM) you'll
	have to setup a miniroot filesystem in the swap partition, as
	described in the "Preparing your System for OpenBSD Installation"
	section above.  If your machine has 6MB or more we strongly
	recommend using the ramdisk kernel instead.  This way you don't
	need to setup any root image beforehand.

	You need to have the "loadbsd" program in your command path.
	If AmigaDOS complains about loadbsd not being an executable file,
	be sure that the "Execute" protection bit is set.  If not, set it
	with the command:
		Protect loadbsd add e

	Next you need to get yourself into OpenBSD by loading the
	kernel from AmigaDOS with loadbsd like so:

		loadbsd bsd.rd

	or, if you are doing a miniroot install:

		loadbsd -b bsd


	If you have an AGA machine, and your monitor will handle
	the dblNTSC mode, you may also include the "-A" option to
	enable the dblNTSC display mode.

	Once the kernel has loaded, you will be presented with the
	OpenBSD kernel boot messages.  You will want to read them
	to determine your disk's name and geometry.  Its name will
	be something like "sd0" or "wd0" and the geometry will be
	printed on a line that begins with its name.  As mentioned
	above, you will need your disk's geometry when creating
	OpenBSD partitions.  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.

	If you are doing the miniroot install you will be prompted for a
	root device.  At this time type 'sd0*', where '0' is the device
	which holds the miniroot-containing swap partition you created
	during the hard disk preparation.  If the system should hang
	after entering the root device, try again with

		loadbsd -I ff -b bsd

	This disables synchronous transfer on all SCSI devices.  For
	ramdisk installations this kind of hang might occur later during
	the install when accessing the SCSI disk for the first time.  If
	such a hang occurs, try again with:

		loadbsd -I ff bsd.rd

	While booting, you will probably see several warnings.  You
	should be warned that no swap space is present.  Do not be
	alarmed, these are completely normal.  When you reach the prompt
	asking you for a shell name, just hit return.

	You will be asked which terminal type to use, you should just
	hit return to select the default (vt220).

	The install program will then tell you which disks of that
	type it can install on, and ask you which it should use.  The
	name of the disk is typically "sd0" for SCSI drives or the
	A4000 IDE drives or "wd0" for ISA-connected IDE drives.  Reply
	with the name of your disk.

	The install program will now ask which file systems should be
	created on which partitions.  It will automatically select the
	'a' partition to be the root file system. Next it will ask for
	which disk and partition you want a file system created on.
	This will be the same as the disk name (e.g. "sd0") with the
	letter identifying the partition (e.g. "d") appended (e.g.
	"sd0d").  Then it will ask where this partition is to be
	mounted, e.g. /usr.  This process will be repeated until you
	just hit return.

	At this point you will be asked to confirm that the file system
	information you have entered is correct, and given an opportunity
	to change the file system table.  Next it will create the new file
	systems as specified, OVERWRITING ANY EXISTING DATA.  This is the
	point of no return.

	The install program will now make the filesystems you specified.
	There should be only one error in this section of the installation.
	It will look like this:

		newfs: ioctl (WDINFO): Invalid argument
		newfs: /dev/rsd0a: can't rewrite disk label

	If there are any others, restart from the beginning of
	the installation process.  This error is ok as the Amiga
	does not write disklabels currently.  You should expect
	this error whenever using newfs.

	After all your file systems have been created, the install program
	will give you 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 NFS, HTTP or FTP, and will also be the
	configuration used by the system after the installation is complete.

	If you select to configure the network, the install program will
	ask you for a name of your system and the DNS domain name to use.
	Note that the host name should be without the domain part, and that
	the domain name should NOT include the host name part.

	Next the system will give you a list of network interfaces you can
	configure.  For each network interface you select to configure, it
	will ask for the IP address to use, the symbolic host name to use,
	the netmask to use and any interface-specific flags to set.  The
	interface-specific flags are usually used to determine which media
	the network card is to use.  The flags usually carry the following
	meaning:

		-link0 -link1	Use BNC (coaxial) port [default]
		link0 -link1	Use AUI port
		link0 link1		Use UTP (twisted pair) port

	After all network interfaces have been configured the install pro-
	gram will ask for a default route and IP address of the primary
	name server to use.  You will also be presented with an opportunity
	to edit the host table.

	At this point you will be allowed to edit the file system table
	that will be used for the remainder of the installation and that
	will be used by the finished system, following which the new file
	systems will be mounted to complete the installation.

	After these preparatory steps has been completed, you will be
	able to extract the distribution sets onto your system.  There
	are several install methods supported; FTP, HTTP, tape, CD-ROM, NFS
	or a local disk partition.  To install from a tape, the distrib-
	ution sets must have been written to tape prior to running the
	installation program, either as tar images or as gzipped tar
	images.  Note that installation from floppies are not currently
	supported.

	To install via FTP:
		To begin an FTP install you will need the following
		pieces of information.  Don't be daunted by this list;
		the defaults are sufficient for most people.
		    1) Proxy server URL if you are using a URL-based
		       ftp 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 (assuming you
		       have a proxy available to use).
		    2) Do you need to use active mode ftp?  By default,
		       ftp will attempt to use passive mode and fall
		       back to an active connection if the server does
		       not support passive mode.  You only need to enable
		       this option if you are connecting to a buggy ftp
		       daemon that implements passive ftp incorrectly.
		       Note that you will not be asked about active
		       ftp if you are using a proxy.
		    3) The IP address (or hostname if you enabled
		       DNS earlier in the install) of an ftp server
		       carrying the OpenBSD 2.9 distribution.
		       If you don't know, just hit return when
		       asked if you want to see a list of such hosts.
		    4) The ftp directory holding the distribution sets.
		       The default value of pub/OpenBSD/2.9/amiga
		       is almost always correct.
		    5) The login and password for the ftp account.
		       You will only be asked for a password for
		       non-anonymous ftp.

		For instructions on how to complete the installation via
		ftp, see the section named "Common URL installations" below.

	To install via HTTP:
		To begin an HTTP install you will need the following
		pieces of information:
		    1) Proxy server URL if you are using a URL-based
		       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 http connections
		       (assuming you have a proxy available to use).
		    3) The IP address (or hostname if you enabled
		       DNS earlier in the install) of an http server
		       carrying the OpenBSD 2.9 distribution.
		       If you don't know, just hit return when
		       asked if you want to see a list of such hosts.
		    4) The directory holding the distribution sets.
		       There is no standard location for this;
		       You should use the directory specified
		       along with the server in the list of official
		       http mirror sites that you received in step 3.

		For instructions on how to complete the installation via
		http, see the section named "Common URL installations" below.

	To install from tape:
		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 provide the file number of the set
		that is to be extracted.  Note that the file number starts
		at 1, which is the first file written to the tape, unless
		you have created a bootable tape, in which case the file
		number starts at 3.

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

	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 either "cd0" or "acd0".  Next you will be asked which
		partition on the CD-ROM the distribution is to be loaded
		from.  This is normally partition "a".

		Next you will have to identify the file system type that
		has been used to create the distribution on the CD-ROM,
		this can be either FFS or ISO CD9660.  The OpenBSD CD
		distribution uses the CD9660 format.

		You will also have to provide the relative path to the
		directory on the CD which holds the distribution, for the
		amiga this is "2.9/amiga".

		For instructions on how to complete the installation from
		the CD-ROM distribution, see the section named "Common
		file system installations" below.

	To install from a NFS mounted directory:
		When installing from a NFS-mounted directory, you must
		have completed network configuration above, and also
		set up the exported file system on the NFS server in
		advance.

		First you must identify the IP address of the NFS server
		to load the distribution from, and the file system the
		server expects you to mount.

		The install program will also ask whether or not TCP
		should be used for transport (the default is UDP).  Note
		that TCP only works with newer NFS servers.

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

		For instructions on how to complete the installation from
		the CD-ROM distribution, see the section named "Common
		file system installations" 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
		0 through 9.  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
		install from partitions that has been formatted as the
		Berkeley fast file system (ffs) or AmigaDOS FFS (ados).

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

		For instructions on how to complete the installation from
		the a local disk partition, see the next section.
		
	Common file system installations:
		The following instructions are common to installations
		from local disk partitions, NFS mounted directories and
		CD-ROMs.

		A list of available distribution sets will be listed.
		You may individually select distribution sets to install
		or enter `all' to install all of the sets (which is what
		most users will want to do).  You may also enter `list'
		to get a file list or `done' when you are done selecting
		distribution sets.  You may also use wildcards in place of
		a file name, e.g. `*.tgz' or even `base*|comp*'.  It is
		also possible to enter an arbitrary filename and have it
		treated as a file set.

		Once you have selected the file sets you want to install
		and entered `done' you will be prompted to verify that
		you really do want to extract file sets.  Assuming you
		acquiesce, the files will begin to extract.  If not, you
		will be given the option of installing sets via one of
		the other install methods.

	Common URL installations:
		Once you have entered the required information, the
		install program will fetch a file list and present
		a list of all the distribution sets that were found
		in the specified directory.  (If no valid sets were found,
		you will be notified and given the option of unpacking
		any gzipped tar files found or getting a file list if
		none were found.)

		At this point you may individually select distribution
		sets to install or enter `all' to install all of the
		sets (which is what most users will want to do).  You
		may also enter `list' to get a file list or `done' when
		you are done selecting distribution sets.  You may also
		use wildcards in place of a file name, e.g. `*.tgz' or
		even `base*|comp*'.  It is also possible to enter an
		arbitrary filename and have it treated as a file set.

		Once you have selected the file sets you want to install
		and entered `done' you will be prompted to verify that
		you really do want to download and install the files.
		Assuming you acquiesce, the files will begin to download
		and unpack.  If not, you will be given the option of
		installing sets via one of the other install methods.


	When all the selected distribution sets has been extracted, you
	will be allowed to select which time zone your system will be
	using, all the device nodes needed by the installed system will
	be created for you and the file systems will be unmounted.  For
	this to work properly, it is expected that you have installed
	at least the "base29", "etc29", and "bsd" distribution sets.

Congratulations, you have successfully installed OpenBSD 2.9.  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.  You should have got a mail from the install program we 
recommend you to read, it contains answers to basic questions you might
have about OpenBSD (like setting up your system, installing packages, getting
more information about OpenBSD, sending in your dmesg output and more).
This you can do by running

	mail

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

Some of the files in the OpenBSD 2.9 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.



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

To do the upgrade, and if you are using the miniroot installation, you
must have the OpenBSD kernel on AmigaDOS and you must transfer the root
filesystem miniroot29.fs onto the swap partition of the OpenBSD hard disk.
If you are using the ramdisk installation, the bsd.rd kernel is enough.
You must also have at least the "base29" binary distribution set available,
so that you can upgrade with it, using one of the upgrade methods described
above.  Finally, you must have sufficient disk space available to install
the new binaries.  Since the old binaries are being overwritten in place,
you only need space for the new binaries, which weren't previously
on the system.  If you have a few megabytes free on each of your
root and /usr partitions, you should have enough space.

Since upgrading involves replacing the kernel, and most of the system
binaries, it has the potential to cause data loss.  You are strongly
advised to BACK UP ANY IMPORTANT DATA ON YOUR DISK, whether on the
OpenBSD partition or on another operating system's partition, before
beginning the upgrade process.

To upgrade your system, follow the following instructions:

	If you know you need an -I option to loadbsd, you should add it
	to the loadbsd invocation you'll use for the upgrade.

	Miniroot installation:

	Transfer the upgrade miniroot filesystem onto the hard disk
	partition used by OpenBSD for swapping, as described in the
	"Preparing your System for OpenBSD Installation" section above.

	Now boot up OpenBSD using the 2.9 kernel using the loadbsd
	command:

		loadbsd -b bsd

	You should see the screen clear and some information about
	your system as the kernel configures the hardware.  Note which
	hard disk device is configured that contains your root and
	swap partition.  When prompted for the root device, type
	'sd0*' (replacing 0 with the disk number that OpenBSD used for
	your root/swap device).  The '*' character indicates that the
	root filesystem is contained on the swap partition.  Continue
	reading below the ramdisk installation description:

	Ramdisk installation:

	Now boot up OpenBSD using the 2.9 kernel using the loadbsd
	command:

		loadbsd bsd.rd

	You should see the screen clear and some information about
	your system as the kernel configures the hardware.

	Common instructions for both miniroot/ramdisk installations:

	When you reach the prompt asking you for a shell name, just
	hit return.

	You will be asked which terminal type to use, you should just
	hit return to select the default (vt220).

	At the question whether to (I)nstall or (U)pgrade choose "U".

	You will be presented with some information about the upgrade
	process and a warning message, and will be asked if you wish
	to proceed with the upgrade process.  If you answer
	negatively, the upgrade process will stop, and your disk will
	not be modified.  If you answer affirmatively, the upgrade
	process will begin, and your disk will be modified.  You may
	hit Control-C to stop the upgrade process at any time.
	However, if you hit it at an inopportune moment, your system
	may be left in an inconsistent (and possibly unusable) state.

	The upgrade program will then check & mount your root filesystem
	under /mnt and grab some configuration info from it for the
	continued upgrade process.  You'll be asked if the network
	should be enabled at this point.  After that is done the rest
	of the filesystems will be checked and mounted.

	If you don't already have the OpenBSD distribution sets on your
	disk, look in the installation section for information on how
	to transfer them to your disk.

	Once the distribution sets are transferred to your disk,
	continue here.  (Obviously, if the OpenBSD distribution sets
	are already on your disk, because you've transferred them
	before starting the upgrade process, you don't need to
	transfer them again now!)

	After the software has been transferred to the machine (or
	mounted, in the case of upgrading via NFS).

Your system has now been upgraded to OpenBSD 2.9.

	After all this, your machine is a complete OpenBSD 2.9 system.
	However, that doesn't mean that you're finished with the upgrade
	process.  There are several things that you should do, or might
	have to do, to insure that the system works properly.

	First, you will probably want to get the etc29.tgz distribution,
	extract it, and compare its contents with those in your /etc/
	directory.  You will probably want to replace some of your
	system configuration files, or incorporate some of the changes
	in the new versions into yours.

	Second, you might want to check your /dev against the new MAKEDEV
	script found there, if you have changed the nodes locally.  The
	upgrade process runs "sh MAKEDEV all" but that may not be enough
	for your personal setup.

	Third, you must deal with certain changes in the formats of
	some of the configuration files.  The most notable change is
	that the "options" given to many of the file systems in
	/etc/fstab or by hand have changed, and some of the file
	systems have changed names.  To find out what the new options
	are, it's suggested that you read the manual page for the
	file systems' mount commands, for example mount_nfs(8) for
	NFS.  (Note that the information for mounts of type "ufs",
	i.e. Fast File Systems, are contained in the mount(8) man
	page.)

	Finally, you will want to delete old binaries that were part
	of the version of OpenBSD that you upgraded from and have since
	been removed from the OpenBSD distribution.  You might also
	want to recompile any locally-built binaries, to take
	advantage of the shared libraries.  (Note that any new
	binaries that you build will be dynamically linked, and
	therefore take advantage of the shared libraries, by default.
	For information on how to make statically linked binaries,
	see the cc(1) and ld(1) manual pages.)



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, the source code
is provided.  Otherwise, you can get the pieces over the Internet using
ANONCVS, CTM or FTP.  For more information, see

	http://www.openbsd.org/anoncvs.html
	http://www.openbsd.org/ctm.html
	http://www.openbsd.org/ftp.html


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

Documentation is available if you first install the manual
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), and
	passwd(5).

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

The '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) Obtain the source code and build the application based
   upon whatever installation procedures are provided with the
   application.

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) Use the OpenBSD ``package'' collection to grab a pre-compiled
   and tested version of the application for your hardware.

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

Instructions for installing applications from the various sources using
the different installation methods follow.  If emacs is to be installed
it should be installed first as it creates the ``info'' directory file
that may be modified by other applications.

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
	2.9/packages/m68k 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/2.9/packages/m68k/<package-name>
    # <add more packages if desired>
    # umount /cdrom
	
	Package names are usually the application name and version
	with .tgz appended, e.g. emacs-20.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/2.9/packages/m68k/
	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/2.9/packages/m68k/emacs-20.3.tgz

	Packages available include (at least):

		ImageMagick-4.2.0.tgz		m4-1.4.tgz
		Xaw3d-1.3.tgz			mm-2.7.tgz
		aalib-1.2.tgz			mpeg_lib-1.2.1.tgz
		afm-1.0.tgz			mpeg_play-2.4.tgz
		autoconf-2.13.tgz		netpbm-19940301.tgz
		bash-2.03.tgz			netpipes-4.1.1-export.tgz
		bison-1.25.tgz			nmh-1.0.tgz
		bzip2-0.9.0c.tgz		pgp-2.6.3-intl.tgz
		compface-1.0.tgz		pgp-2.6.3-usa.tgz
		cucipop-1.31.tgz		pine-4.10.tgz
		dejagnu-1.3.tgz			png-1.0.3.tgz
		egcs-1.1.2.tgz			psutils-1.17-a4.tgz
		emacs-20.3.tgz			psutils-1.17-letter.tgz
		enscript-1.6.1.tgz		screen-3.7.6.tgz
		ethereal-0.5.1.tgz		sharutils-4.2.tgz
		expect-5.28.tgz			sniffit-0.3.5.tgz
		fetchmail-4.7.9.tgz		freetype-1.2.tgz		
		gettext-0.10.35.tgz		tar-1.12.tgz
		ghostscript-5.10.tgz		tcl-8.0.5.tgz
		gimp-1.1.4.tgz			tcsh-6.08.00.tgz
		glib-1.2.1.tgz			teTeX-0.4.tgz
		glimpse-4.1.tgz			tiff-3.4.tgz
		gmake-3.77.tgz			tk-8.0.5.tgz
		gnuplot-3.7.tgz			transfig-3.2.1.tgz
		gtk+-1.2.1.tgz			unzip-5.40.tgz
		gv-3.5.8.tgz			viewfax-2.3.tgz
		id-utils-3.2.tgz		wget-1.5.3.tgz
		idled-1.16.tgz			xcolors-1.3.tgz
		iozone-2.01.tgz			xfig-3.2.2.tgz
		ircii-2.8.2-epic3.004.tgz	xntp3-5.93e-export.tgz
		ispell-3.1.20.tgz		xpaint-2.5.5.tgz
		jove-4.16.tgz			xpdf-0.80.tgz
		jpeg-6b.tgz			xphoon-91.9.18.tgz
		lesstif-0.88.0.tgz		xspread-2.1.tgz
		libslang-1.2.2.tgz		xv-3.10a.tgz

	Note: these packages may not exist for all architectures; other
	packages may be added.  Some packages are only available via
	ftp.

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 README.ports on CD-ROM 2
	to see how to copy or mount the ports directory.

	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/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 luck there you may try the FreeBSD
	ports or NetBSD package collection.  If you are on an i386 based
	machine it is quite possible that the FreeBSD port, if one exists,
	will work for you.

	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 at http://www.openbsd.org/porting.html
	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.

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

Use of 'sendbug' is encouraged, however, because bugs reported with it
are entered into the OpenBSD bugs database, and thus can't slip through
the cracks.

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.