Create bootable floppy on Windows:
	cdrom:\3.0\i386\>format a:
	cdrom:\3.0\i386\>ntrw.exe floppy30.fs a:

Create bootable floppy on OpenBSD:
	dd if=floppy40.fs of=/dev/rfd0c bs=32k	# write image to raw fd0
	cmp /dev/rfd0c floppy40.fs		# verify write

--------------------------------------------------------------------------------

Quick Reference

Flow:
	(I)nstall, (U)pgrade or (S)hell? i
	Specify terminal type [vt220]: 

	Which disk is the root disk? [wd0] 
	Do you want to use the *entire* disk for OpenBSD? [no] yes

Parition Slicing (disklabel):
	> ?
	> p
	> d a (if you have an 'a' partition)
	> a a (80m , /    )
	> a b (300m,      )
	> a d (80m , /tmp )
	> a e (80m , /var )
	> a g (350m, /usr )
	> a h (    , /home)
	> p
	> w
	> q

Time Zone:
	Time Zone: America / Chicago

--------------------------------------------------------------------------------

At almost any point during the OpenBSD install process, you can terminate the
current install attempt by hitting CTRL-C and can restart it without rebooting
by running install at the shell prompt.

The i386 disk setup is done in two stages. First, the OpenBSD slice of the
hard disk is defined using fdisk(8), then that slice is subdivided into
OpenBSD partitions using disklabel(8). Other OSes will only see the first
partition created (the containing partition). The second type of partitions is
how the OpenBSD partition is sub-partitioned into individual filesystems.
The first partition, created with fdisk, is called the MBR partition, the other
partitions, created with disklabel, are called OpenBSD partitions.

To enable all available security features of OpenBSD, you should configure the
disk(s) to allow the creation of separate filesystems for /, /tmp, /var, /usr,
and /home.

The root disk is the disk the system will boot from, and normally where swap
space resides. IDE disks will show up as wd0, wd1, etc., SCSI disks and RAID
devices will show up as sd0, sd1, and so on.

Select fdisk options:

	fdisk -e /dev/rwd0c
	r or reinit:
	  Clears existing partition table, makes one big OpenBSD partition,
	  flags it active, and installs the OpenBSD MBR code. Equivalent to
	  saying "yes" to the "use *all* of ..." question.
	p or print:
	  Displays the current partition table in sectors. "p m" will show
	  the partition table in megabytes, "p g" will show it in gigabytes.
	e or edit:
	  edit or alter a table entry (OpenBSD type/id: A6).
	f or flag:
	  Marks a partition as the active partition, the one that will be
	  booted from.
	u or update:
	  Updates the MBR with the OpenBSD boot code, similar to "reinit",
	  except it doesn't alter the existing partition table.
	w or write
	  Write loaded MBR to disk / write partition table to disk.
	exit
	  Exit edit of current MBR, without saving changes.
	quit
	  Quit edit of current MBR, saving current changes.

The offsets used in the disklabel are ABSOLUTE, i.e. relative to the start of
the disk, NOT the start of the OpenBSD MBR partition.

Select disklabel options:

	p - displays (prints) the current disklabel to the screen, and you
	    can use the modifiers k, m or g for kilobytes, megabytes or
	    gigabytes. 
	D - Clears any existing disklabel, creates a new default disklabel
	    which covers just the current OpenBSD partition. This can be
	    useful if the disk previously had a disklabel on it, and the
	    OpenBSD partition was recreated to a different size -- the old
	    disk label may not get deleted, and may cause confusion. 
	m - Modifies an existing entry in a disklabel. Do not over estimate
	    what this will do for you. While it may alter the size of a
	    disklabel partition, it will NOT alter the filesystem on the
	    drive. Using this option and expecting it to resize existing
	    partitions is a good way of losing large amounts of data.

The 'b' partition is your swap partition, the 'c' partition is reserved and
represents the entire disk. The labels you will use are a, d, e, f, g, h, n.