INSTALLATION NOTES for OpenBSD/mac68k 4.1
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.
To integrate more smoothly in other environments, OpenBSD 4.1 also
provides, on some platforms, 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.
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 4.1 release
is available on the web at http://www.OpenBSD.org/41.html.
OpenBSD/mac68k runs on some of the old Macintosh (Motorola 680x0-based)
computers.
Sources of OpenBSD:
-------------------
This is a list of currently known FTP servers at the time of the 4.1 release.
For a more recent list, please refer to
http://www.OpenBSD.org/ftp.html
Main server in Canada:
ftp://ftp.OpenBSD.org/pub/OpenBSD (Alberta)
2nd level mirrors:
ftp://spargel.kd85.com/pub/OpenBSD (Vienna)
ftp://openbsd.informatik.uni-erlangen.de/pub/OpenBSD (Erlangen)
ftp://ftp.stacken.kth.se/pub/OpenBSD (Stockholm)
ftp://ftp5.usa.openbsd.org/pub/OpenBSD (Redwood City, CA)
ftp://ftp3.usa.openbsd.org/pub/OpenBSD (Boulder, CO)
ftp://rt.fm/pub/OpenBSD (Lake in the Hills, IL)
Argentina:
ftp://ftp.openbsd.md5.com.ar/pub/OpenBSD (Buenos Aires)
Australia:
ftp://ftp.it.net.au/mirrors/OpenBSD (Perth)
ftp://mirror.pacific.net.au/OpenBSD (Sydney)
Austria:
ftp://playboy.wu-wien.ac.at/pub/OpenBSD (Vienna)
Belgium:
ftp://ftp.scarlet.be/pub/openbsd (Brussels)
ftp://ftp.belnet.be/packages/openbsd (Brussels)
Brazil:
ftp://ftp.das.ufsc.br/pub/OpenBSD (Florianopolis, Santa Catarina)
Bulgaria:
ftp://ftp.bg.openbsd.org/pub/OpenBSD (Plovdiv)
Canada:
ftp://mirror.arcticnetwork.ca/pub/OpenBSD (Calgary)
ftp://ftp.ca.openbsd.org/pub/OpenBSD (Edmonton)
ftp://gulus.usherbrooke.ca/pub/distro/OpenBSD (Quebec)
China:
ftp://ftp.freebsdchina.org/pub/OpenBSD (Shanghai)
Denmark:
ftp://mirrors.dotsrc.org/openbsd (Aalborg)
ftp://ftp.dkuug.dk/pub/OpenBSD (Copenhagen)
Estonia:
ftp://ftp.aso.ee/pub/OpenBSD (Tallinn)
Finland:
ftp://mirrors.nic.funet.fi/pub/OpenBSD (Espoo)
ftp://ftp.jyu.fi/pub/OpenBSD (Jyvaskyla)
France:
ftp://ftp.arcane-networks.fr/pub/OpenBSD (Paris)
ftp://ftp.crans.org/pub/OpenBSD (Paris)
ftp://ftp.irisa.fr/pub/OpenBSD (Rennes)
Germany:
ftp://openbsd.ftp.fu-berlin.de/pub/OpenBSD (Berlin)
ftp://ftp.freenet.de/pub/ftp.openbsd.org/pub/OpenBSD (Duesseldorf)
ftp://ftp-stud.fht-esslingen.de/pub/OpenBSD (Esslingen)
ftp://mirror.roothell.org/pub/OpenBSD (Nuremberg)
ftp://ftp.bytemine.net/pub/OpenBSD (Oldenburg)
Greece:
ftp://filoktitis.noc.uoa.gr/pub/OpenBSD (Athens)
ftp://ftp.physics.auth.gr/pub/mirrors/OpenBSD/OpenBSD (Thessaloniki)
ftp://ftp.duth.gr/pub/OpenBSD (Thrace)
Hungary:
ftp://ftp.fsn.hu/pub/OpenBSD (Budapest)
Ireland:
ftp://ftp.esat.net/pub/OpenBSD (Dublin)
Israel:
ftp://mirror.inter.net.il/pub/OpenBSD (Petach Tiqwa)
Italy:
ftp://ftp.unina.it/pub/OpenBSD (Napoli)
Japan:
ftp://ftp.jaist.ac.jp/pub/OpenBSD (Ishikawa)
ftp://ftp.nara.wide.ad.jp/pub/OpenBSD (Nara)
ftp://ftp.jp.openbsd.org/pub/OpenBSD (Tokyo)
ftp://ftp.kddlabs.co.jp/OpenBSD (Tokyo)
Korea:
ftp://ftp.kaist.ac.kr/pub/OpenBSD (Daejeon)
Latvia:
ftp://ftp.secure.lv/pub/OpenBSD (Riga)
ftp://ftp.bsd.lv/pub/OpenBSD (Riga)
The Netherlands:
ftp://ftp.calyx.nl/pub/OpenBSD (Amsterdam)
ftp://ftp.nluug.nl/pub/OpenBSD (Utrecht)
ftp://mirror.hostfuss.com/pub/OpenBSD (Amsterdam)
Norway:
ftp://ftp.inet.no/pub/OpenBSD (Oslo)
ftp://ftp.uninett.no/pub/OpenBSD (Oslo)
ftp://jane.tihlde.org/pub/OpenBSD (Trondheim)
Poland:
ftp://ftp.task.gda.pl/pub/OpenBSD (Gdansk)
Portugal:
ftp://ftp.fmed.uc.pt/pub/OpenBSD (Coimbra)
Russia:
ftp://ftp.chg.ru/pub/OpenBSD (Chernogolovka-Moscow)
ftp://ftp.gamma.ru/pub/OpenBSD (Moscow)
South Africa:
ftp://ftp.is.co.za/pub/OpenBSD (Johannesburg)
Spain:
ftp://ftp.rediris.es/mirror/OpenBSD (Madrid)
Sweden:
ftp://ftp.su.se/pub/OpenBSD (Stockholm)
ftp://ftp.btradianz.se/pub/OpenBSD (Stockholm)
Switzerland:
ftp://mirror.switch.ch/pub/OpenBSD (Zurich)
Ukraine:
ftp://gaia.colocall.net/pub/OpenBSD (Kiev)
United Kingdom:
ftp://ftp.public-internet.co.uk/pub/OpenBSD (London)
ftp://ftp.mirrorservice.org/pub/OpenBSD (Kent)
USA:
ftp://mirror.sese.asu.edu/pub/OpenBSD (Tempe, AZ)
ftp://mirror.planetunix.net/pub/OpenBSD (Chicago, IL)
ftp://osmirrors.cerias.purdue.edu/pub/OpenBSD (West Lafayette, IN)
ftp://mirror.iawnet.sandia.gov/pub/OpenBSD (Albuquerque, NM)
ftp://ftp.cse.buffalo.edu/pub/OpenBSD (Buffalo, NY)
ftp://ftp.nyc.openbsd.org/pub/OpenBSD (New York, NY)
ftp://mirrors.24-7-solutions.net/pub/OpenBSD (New York, NY)
ftp://openbsd.mirrors.pair.com (Pittsburgh, PA)
ftp://carroll.cac.psu.edu/pub/OpenBSD (PA)
ftp://openbsd.mirrors.tds.net/pub/OpenBSD (Madison, WI)
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 4.1 Release Contents:
-----------------------------
The OpenBSD 4.1 release is organized in the following way. In the
.../4.1 directory, for each of the architectures having an OpenBSD 4.1
binary distribution, there is a sub-directory.
The mac68k-specific portion of the OpenBSD 4.1 release is found in the
"mac68k" subdirectory of the distribution. That subdirectory is laid
out as follows:
.../4.1/mac68k/
INSTALL.mac68k Installation notes; this file.
CKSUM, MD5 Output of the cksum(1) and md5(1) programs,
usable for verification of the correctness of
downloaded files.
*.tgz mac68k binary distribution sets; see below.
bsd A stock GENERIC mac68k kernel which will be
installed on your system during the install.
bsdsbc A slightly different GENERIC mac68k kernel, using
a different SCSI driver for some mac68k models, which
may allow some otherwise incompatible SCSI devices to
function with OpenBSD/mac68k.
bsd.rd A compressed RAMDISK kernel; the embedded
filesystem contains the installation tools.
Used for simple installation from a pre-existing
system.
bsdsbc.rd A slightly different RAMDISK kernel, using
a different SCSI driver for some mac68k models, which
may allow some otherwise incompatible SCSI devices to
function with OpenBSD/mac68k.
utils/ The OpenBSD/mac68k boot program for Mac OS.
The OpenBSD/mac68k binary distribution sets contain the binaries which
comprise the OpenBSD 4.1 release for mac68k systems. There are eleven
binary distribution sets. The binary distribution sets can be found in
the "mac68k" subdirectory of the OpenBSD 4.1 distribution tree,
and are as follows:
base41 The OpenBSD/mac68k 4.1 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.
[ 39.3 MB gzipped, 127.4 MB uncompressed ]
comp41 The OpenBSD/mac68k Compiler tools. All of the tools relating
to C, C++, Objective-F and Fortran 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.
[ 46.3 MB gzipped, 162.6 MB uncompressed ]
etc41 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.)
[ 1.0 MB gzipped, 3.8 MB uncompressed ]
game41 This set includes the games and their manual pages.
[ 2.5 MB gzipped, 6.0 MB uncompressed ]
man41 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.
[ 6.5 MB gzipped, 23.2 MB uncompressed ]
misc41 This set includes the system dictionaries (which are rather
large), and the typesettable document set.
[ 2.1 MB gzipped, 7.1 MB uncompressed ]
xbase41 This set includes the base X distribution. This includes
programs, headers and libraries.
[ 6.0 MB gzipped, 17.9 MB uncompressed ]
xetc41 This set includes the X window system configuration files
that reside in /etc. It's the equivalent of etc41 for X.
[ 64.4 KB gzipped, 255.0 KB uncompressed ]
xfont41 This set includes all of the X fonts.
[ 31.6 MB gzipped, 35.8 MB uncompressed ]
xserv41 This set includes all of the X servers.
[ 482.1 KB gzipped, 1.0 MB uncompressed ]
xshare41 This set includes all text files equivalent between all
architectures.
[ 1.9 MB gzipped, 10.5 MB uncompressed ]
The directory '../4.1/mac68k/utils' contains the OpenBSD/mac68k boot
program, used to load the OpenBSD kernel. This program is distributed
as a self-extracting archive in Macintosh BinHex format. If there is no
BSD/Mac68k booter already installed on your Mac OS system, you will need to
download this file.
OpenBSD System Requirements and Supported Devices:
--------------------------------------------------
OpenBSD/mac68k 4.1 runs on several of the older Macintosh computers.
8MB of RAM should be sufficient to boot and a minimal system can probably
be squeezed onto a 120MB partition by installing just the minimum sets.
To actually do much compiling or anything more interesting than
booting, more RAM and disk space is highly recommended. About 250MB will be
necessary to install all of the OpenBSD 4.1 binary distribution (note that
this does not count swap space!).
A Mac OS partition is also required to install OpenBSD/mac68k 4.1 and boot
it, see below.
OpenBSD/mac68k 4.1 runs on most 680x0 Macintosh's. Specifically, it
should work on:
* 68020 with 68851 PMMU and 68881 FPU
* 68030 with 68882 FPU (many Macs do not have this)
* 68040 (not including the 68LC040)
The following Macintosh models are supported and tested. This means that at
least the SCSI controller, serial console and on-board ethernet will function on
these models. On some of these machines, a full 68040 CPU is required to
replace the default 68LC040 CPU.
* LC family: LC 475, Performa 475, Performa 476
* Centris family: 610, 650
* Quadra family: 605, 610, 630, 650, 660AV, 700, 800, 840AV, 900, 950
Supported devices:
* Internal SCSI controllers and peripherals:
- Quadra/Centris series' onboard NCR 53c96 SCSI controller
(esp).
- Macintosh II-series', Performa, and LC-series' onboard NCR
5380 SCSI controller (ncrscsi, sbc).
- SCSI disk drives (sd).
- SCSI cdrom drives (cd).
- Autochangers (ch).
- Tape drives (st).
* Internal sound (asc).
* NuBus internal expansion bus (nubus).
* Most NuBus video cards.
* Both internal serial ports (zsc).
* ADB keyboards and mice (adb) (except on the IIfx, Quadra 900 and 950).
* Ethernet cards based on the Natl. Semiconductor 8390 (Asante, Apple,
and a few others) (ae).
* Quadra/Centris AV series' onboard MACE ethernet (mc).
* Some ethernet cards based on the SONIC chip including internal
Ethernet on many of Apple's non-AV Quadras/Centrises (sn).
Untested systems:
The following Macintosh models are untested and/or lack support for
major subsystems. It is very likely that many of these system don't
work at all.
* Classic family: Color Classic, Classic II
* Macintosh II family: Mac II, IIx, IIcx, IIci, IIsi, IIfx, IIvi, IIvx,
Performa 600
* LC family: LC, LC II, LC III, LC III+, Performa 400-430,
Performa 450, Performa 460
* 500 family: 520, 550, 575, 580, Mac TV
OpenBSD/mac68k 4.1 does NOT run on these machines:
* PowerPC-based Macs. Newer Mac PPC systems are supported by the
OpenBSD/macppc port.
* Powerbook family. Hardware capabilities limit the usability of these
systems.
* Machines based on the 68LC040 processor. Unfortunately, the chip
itself contains a major bug for which there is no software workaround
available in OpenBSD.
Hardware that we do NOT currently support, but get many questions about:
* Apple Communication Slot (CS) Ethernet cards.
* Floppy drive.
* IOP ADB subsystem on the IIfx, Quadra 900 and 950.
* IDE drives.
Getting the OpenBSD System onto Useful Media:
---------------------------------------------
Installation is supported from several media types, including:
CD-ROM
FFS partitions (for upgrades only)
Tape
Remote NFS partition
FTP
HTTP
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.
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 misc xbase xetc xfont xserv xshare
do
dd if=${file}41.tgz of=${TAPE} obs=8k conv=sync
done
tar cf ${TAPE} bsd
mt -f ${TAPE} offline
# end of script
And then:
cd .../4.1/mac68k
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).
To install OpenBSD using a remote partition, mounted via
NFS, you must do the following:
NOTE: This method of installation is recommended only for
those already familiar with using BSD network
configuration and management commands. If you aren't,
this documentation should help, but is not intended to
be all-encompassing.
Place the OpenBSD distribution sets you wish to install
into a directory on an NFS server, and make that directory
mountable by the machine on which you are installing or
upgrading OpenBSD. This will probably require modifying
the /etc/exports file of the NFS server and resetting
its mount daemon (mountd). (Both of these actions will
probably require superuser privileges on the server.)
You need to know the numeric IP address of the NFS
server, and, if the server is not on a network directly
connected to the machine on which you're installing or
upgrading OpenBSD, you need to know the numeric IP address
of the router closest to the OpenBSD machine. Finally,
you need to know the numeric IP address of the OpenBSD
machine itself.
Once the NFS server is set up properly and you have the
information mentioned above, you can proceed to the next
step in the installation or upgrade process.
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 "base41" 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 machine only has one SCSI disk, you will need to share the disk
with Mac OS. You might have to repartition and/or reinstall Mac OS in
order to make room available for OpenBSD.
Find your favorite disk partitioning utility. Some of the ones that have
been tried and seem to work are:
APS Powertools 2.7.3
SCSI Directory Lite
Disk Manager Mac from OnTrack
HD SC Setup from Apple
I/O Formatter from Diversified (?)
Silverlining from LaCie
"HD SC Setup" is included with the supported versions of Mac OS.
This utility ignores non-Apple hard disks unless you patch it with the
application found at the following URL:
http://www.euronet.nl/users/ernstoud/hdpatch.html
Alternatively, one might prefer to use the A/UX version which does not
have such a restriction, and can be found at the following URL:
http://www.euronet.nl/users/ernstoud/hdsetup.html
Prior to attempting to repartition your disk, everything of value on the
drive should be backed up. All information on the drive you will be
repartitioning will be lost.
That done, use your favorite partitioning utility and make any necessary
Mac OS partitions, then restore your data.
You might want to create your OpenBSD partitions at this time, rather than
with the "pdisk" utility during the installation itself. In this case,
create one "A/UX Root" partition (for the / filesystem), one "Swap"
partition (for swap, obviously), and as many "Usr file system" or
"Unreserved" partitions as you want (for the other filesystems, such as
/tmp, /usr, /var, etc).
You will also need to install the BSD/Mac68k Booter on your Mac OS
system. It is available in the utils/ subdirectory of the distribution,
in self-extracting and binhex form as booter.sea.hqx.
Extract it as you would for any other Macintosh application.
Before moving on, you should make sure that your machine is running the
correct software on the Mac OS side. In the Memory control panel, you
should turn Virtual Memory off whenever you are planning to use the
BSD/Mac68k Booter.
You should also make sure that your machine is using 32-bit addressing.
If there is no "Addressing:" option in your Memory control panel and your
machine is supported, you will probably need Mode32. Mode32 is a control
panel and extension combination which enables 32-bit addressing on older
Macs which do not use it by default. This program is available from any
Info-Mac mirror.
All of that done and accounted for, you are now set to install OpenBSD on
your hard drive.
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.
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).
Double-click on the BSD/Mac68k Booter icon on the desktop to
start the application. Go to the "Booting..." entry in the
"Options" menu, and make it point to the bsd.rd kernel on your
Mac OS filesystem. For the Quadra 605, LC 475, Performa 475 and
Performa 476 models it is also necessary to activate the video address
hack. Now boot the kernel.
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".
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.
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 vt100).
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. 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. You will first be given an
opportunity to run pdisk and create OpenBSD partitions.
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 creation of partitions for 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_Patches Patch Partition 512 @ 192
5: Apple_HFS untitled 61440 @ 704 ( 30.0M)
6: Apple_Free Extra 17711380 @ 62144 ( 8.4G)
After editing the table, it should look like:
#: type name length base ( size )^M
1: Apple_partition_map Apple 63 @ 1
2: Apple_Driver43*Macintosh 54 @ 64
3: Apple_Driver43*Macintosh 74 @ 118
4: Apple_Patches Patch Partition 512 @ 192
5: Apple_HFS untitled 61440 @ 704 ( 30.0M)
6: Apple_UNIX_SVR2 OpenBSD_Root 2097152 @ 62144 ( 1.0G) S0 RUFS k0 /
7: Apple_UNIX_SVR2 OpenBSD_Swap 262144 @ 2159296 (128.0M) S1 SFS k0 (swap)
8: Apple_UNIX_SVR2 OpenBSD_Usr 8388608 @ 2421440 ( 4.0G) S2 UFS k0 /usr
9: Apple_UNIX_SVR2 OpenBSD_Tmp 2097152 @ 10810048 ( 1.0G) S2 UFS k0
10: Apple_UNIX_SVR2 OpenBSD_Var 4866323 @ 12907200 ( 2.3G) S2 UFS k0
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. The pdisk
tool will automatically adjust the Apple_Free partition.
---
Command (? for help): c
First block: 62144
Length in blocks: 2097152
Name of partition: OpenBSD_Root
Available partition slices for Apple_UNIX_SVR2:
a root partition
b swap partition
c do not set any bzb bits
g user partition
Other lettered values will create user partitions
Select a slice for default bzb values: a
---
For the OpenBSD_Root slice, chose a bzb value of 'a', for
OpenBSD_Swap 'b'. For any other slice do not set any bzb value ('c')
except for OpenBSD_Usr, which can be set to 'g'.
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'.
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).
OpenBSD/mac68k can share a disk with Mac OS by using
an HFS partitioned disk. For proper layout, the disk should be
partitioned with Mac OS first with unused space where OpenBSD can
be installed.
The swap partition (usually 'b') should have a type of "swap", all
other native OpenBSD partitions should have a type of "4.2BSD".
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.
"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 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.
If you select to configure the network, the install program will
ask you for the 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. Typically no media flags are required
as autodetection normally works, but you will be prompted with a
list of the acceptable media flags, and asked if you want to provide
any. In doubt, do not enter any media flags; or you can refer to
the manual page for your interface for the appropriate flags.
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 have been completed, you will be
able to extract the distribution sets onto your system. There
are several install methods supported; FTP, HTTP, tape,
{:耶D-ROMor a local disk partition.
Note that installation from floppies is 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 4.1 distribution.
If you don't know, answer ``y'' 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/4.1/mac68k
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).
2) The IP address (or hostname if you enabled
DNS earlier in the install) of an HTTP server
carrying the OpenBSD 4.1 distribution.
If you don't know, answer ``y'' when asked if
you want to see a list of such hosts.
3) 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 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.
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". 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-ROM
distribution uses the CD9660 format.
You will also have to provide the relative path to the
directory on the CD-ROM which holds the distribution, for
the mac68k this is "4.1/mac68k".
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 an NFS mounted directory:
When installing from an 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.
Common file system installations:
The following instructions are common to installations
from mounted 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 "base41", "etc41", and "bsd" distribution sets.
Once the installation is complete, reboot into Mac OS, and start the
BSD/Mac68k Booter again. This time, point to the OpenBSD kernel location
on its own partition. You will have to change the kernel name to "bsd"
or "bsdsbc", depending which one you have installed. Be sure to check that
the SCSI ID is correct as well.
Note that by setting the BSD/Mac68k Booter to boot automatically
after starting, and by placing an alias to the booter in the "Startup Items"
folder, one can make the Mac68k autoload OpenBSD upon startup.
Congratulations, you have successfully installed OpenBSD 4.1. 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 4.1 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:
------------------------------------------------
Warning! Upgrades to OpenBSD 4.1 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.
To upgrade OpenBSD 4.1 from a previous version, start with the general
instructions in the section "Installing OpenBSD".
Boot from the bsd.rd kernel.
When prompted, select the (U)pgrade option rather than the (I)nstall
option at the prompt in the install process.
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 the ``etc41.tgz'' set, 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 etc41.tgz set in
a temporary directory and merge changes by hand, 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, CTM, CVSync or FTP. For more information, see
http://www.OpenBSD.org/anoncvs.html
http://www.OpenBSD.org/ctm.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) 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 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
4.1/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/4.1/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-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/4.1/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/4.1/packages/m68k/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/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 tinker with the NetBSD
pkgsrc.
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.
For more information about reporting bugs, see
http://www.OpenBSD.org/report.html