After entering the terminal type 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. You will be presented with a welcome message and asked if you really wish to install (or upgrade). Assuming you answered yes, 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. Reply with the name of your disk. Next you will have to edit or create a disk label for the disk OpenBSD is being installed on. If there are any existing partitions defined (for any operating system), and a disk label is not found, you will first be given an opportunity to run fdisk (MBR partitioned disk) or pdisk (HFS partitioned disk) and create an OpenBSD partition. If pdisk is being invoked, you will be issued a command prompt allowing you to modify the partition table. The most common operation, and the example presented here, deals with the conversion of an existing partition into one usable by OpenBSD. Before editing, the partition table may look like the following: #: type name length base ( size ) 1: Apple_partition_map Apple 63 @ 1 2: Apple_Driver43*Macintosh 54 @ 64 3: Apple_Driver43*Macintosh 74 @ 118 4: Apple_Driver_ATA*Macintosh 54 @ 192 5: Apple_Driver_ATA*Macintosh 74 @ 246 6: Apple_FWDriver Macintosh 200 @ 320 7: Apple_Driver_IOKit Macintosh 512 @ 520 8: Apple_Patches Patch Partition 512 @ 1032 9: Apple_HFS untitled 2142310 @ 1544 ( 1.0G) 10: Apple_HFS untitled 2 4120589 @ 2143854 ( 2.0G) 11: Unused untitled 3 6330517 @ 6264443 ( 3.0G) After editing the table, it should look like: #: type name length base ( size ) 1: Apple_partition_map Apple 63 @ 1 2: Apple_Driver43*Macintosh 54 @ 64 3: Apple_Driver43*Macintosh 74 @ 118 4: Apple_Driver_ATA*Macintosh 54 @ 192 5: Apple_Driver_ATA*Macintosh 74 @ 246 6: Apple_FWDriver Macintosh 200 @ 320 7: Apple_Driver_IOKit Macintosh 512 @ 520 8: Apple_Patches Patch Partition 512 @ 1032 9: Apple_HFS untitled 2142310 @ 1544 ( 1.0G) 10: Apple_HFS untitled 2 4120589 @ 2143854 ( 2.0G) 11: OpenBSD OpenBSD 6330517 @ 6264443 ( 3.0G) This will likely be different based on the number of partitions created on the disk by the Apple partition editor. It is _VERY_ important to not change the start, sizes, or types of partitions other than the ones that are to be used by OpenBSD, including the Apple_Driver.* and Apple_partition_map. --- Command (? for help): p Command (? for help): t Partition number: 11 Existing partition type ``Unused''. New type of partition: OpenBSD Command (? for help): p --- If fdisk is being invoked, it will start by displaying the current partitions defined and then allow you to modify this information, add new partitions, and change which partition to boot from by default. If you make a mistake, you will be allowed to repeat this procedure as necessary to correct this. Note that you should make OpenBSD be the active partition at least until the install has been completed. Next the disk label which defines the layout of the OpenBSD file systems must be set up. The installation script will invoke an interactive editor allowing you to do this. Note that partition 'c' inside this disk label should ALWAYS reflect the entire disk, including any non-OpenBSD portions. If you are labeling a new disk, you will probably start out with an 'a' partition that spans the disk. In this case you should delete 'a' before adding new partitions. The root file system should be in partition 'a', and swap is usually in partition 'b'. If you have DOS or Linux partitions defined on the disk, these will usually show up as partition 'h', 'i' and so on. OpenBSD/macppc can share a disk with Mac OS or Mac OS X by using an HFS partitioned disk. For proper layout, the disk should be partitioned with Mac OS or Mac OS X first with unused space or a spare partition where OpenBSD can be installed. No low disk boundaries exist on macppc. macppc is unable to install the bootloader into the HFS(+) partition to boot OpenBSD so it is necessary to copy 'ofwboot' from the installation media into the first HFS(+) partition using Mac OS or Mac OS X. If the disk is partitioned using MBR, the bootloader is automatically installed. However because fdisk is not LBA knowledgeable it may be necessary to run the 'b' command in disklabel to allow OpenBSD to use the entire disk. Note that all OpenBSD partitions in the disk label must have an offset that makes it start within the OpenBSD part of the disk, and a size that keeps it inside of that portion of the disk. This is within the bounds of the 'c' partition. It is recommended that you create separate partitions for /usr, /tmp, and /var, and if you have room for it, one for /home. In doing this, remember to skip 'c', leaving it as type "unused". For help in the disk label editor, enter '?' or 'M' to view the manual page (see the info on the ``-E'' flag). The swap partition (usually 'b') should have a type of "swap", all other native OpenBSD partitions should have a type of "4.2BSD". Block and fragment sizes are usually 8192 and 1024 bytes, but can also be 4096 and 512 or even 16384 and 2048 bytes. The install program will now label your disk and ask which file systems should be created on which partitions. It will auto- matically 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. "wd0") with the letter identifying the partition (e.g. "d") appended (e.g. "wd0d"). Then it will ask where this partition is to be mounted, e.g. /usr. This process will be repeated until you enter "done". 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. 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 HTTP or FTP, and will also be the configuration used by the system after the installation is complete.