INSTALLATION NOTES for OpenBSD/i386 2.1
What is OpenBSD?
----------------
OpenBSD is a Berkeley Networking Release 2 (Net/2) and 4.4BSD-Lite
-derived Operating System. It is a fully functional UN*X-like system
which runs on many architectures and is being ported to more.
Continuing the multi-platform tradition, OpenBSD has added ports to
mvme68k, powerpc and arc machines. Kernel interfaces have continued
to be refined, and now several subsystems and device drivers are
shared among the different ports. You can look for this trend to
continue.
Security of the system as a whole has been significantly improved.
Source code for all critical system components has been checked for
remote-access, local-access, denial-of-service, data destruction, or
information-gathering problems. Tools like ipf, ipnat, and nc have
been added to the tree because security conscious people often need
them.
OpenBSD 2.1 has significantly enhanced the binary emulation subsystem
(which includes iBCS2, Linux, OSF/1, SunOS, SVR4, Solaris and Ultrix
compatibility) and several kernel subsystems have been generalized to
support this more readily. The binary emulation strategy is aimed at
making the emulation as accurate as possible.
Cryptography components are part of OpenBSD. OpenBSD is from Canada,
and export of these pieces (such as kerberosIV) to the world is not
restricted. Note that it can not be re-exported from the US once it
has entered US. Because of this, take care NOT to get the distrib-
ution from an FTP server in the US if you are outside of Canada and
the US.
Many new user programs have been added in OpenBSD 2.1, as well,
bringing it closer to our goal of supplying a complete and modern
UN*X-like environment. Tools like perl and ksh are standard, as are
numerous other useful tools.
For the i386, OpenBSD 2.1 brings greater stability and security. As a
side effect of the full security audit, many userland programs have
been significantly cleaned up and debugged.
Sources of OpenBSD:
-------------------
This is a list of currently known ftp servers:
Germany:
ftp://ftp.fu-berlin.de/pub/unix/openbsd/mirrors/OpenBSD ==
ftp://ftp.de.openbsd.org/pub/unix/openbsd/mirrors/OpenBSD
Japan:
ftp://ftp.tut.ac.jp/OpenBSD == ftp://ftp.jp.openbsd.org/OpenBSD
ftp://ftp.dti.ad.jp/pub/OpenBSD
Switzerland:
ftp://ftp.openbsd.org/pub/OpenBSD ==
ftp://ftp.eu.openbsd.org/pub/OpenBSD
USA:
ftp://hydra.heuris.com/pub/OpenBSD ==
ftp://ftp1.usa.openbsd.org/pub/OpenBSD
ftp://freestuff.cs.colorado.edu/pub/OpenBSD ==
ftp://ftp2.usa.openbsd.org/pub/OpenBSD
ftp://ftp.ctaz.com/pub/OpenBSD ==
ftp://ftp5.usa.openbsd.org/pub/OpenBSD
ftp://pub.seastrom.com/pub/OpenBSD ==
ftp://ftp1.usa.openbsd.org/pub/OpenBSD
As well, the file ftp://ftp.openbsd.org/pub/OpenBSD/2.1/ftplist
contains a list which is continually updated. If you wish to become a
distribution site for OpenBSD, contact deraadt@cvs.openbsd.org.
OpenBSD 2.1 Release Contents:
-----------------------------
The OpenBSD 2.1 release is organized in the following way. In the
.../2.1 directory, there is one sub-directory per architecture, for
each of the architectures that OpenBSD 2.1 has a binary distribution
for. That is described further along in this document).
The i386-specific portion of the OpenBSD 2.1 release is found in the
"i386" subdirectory of the distribution. That subdirectory is laid
out as follows:
.../2.1/i386/
INSTALL.i386 Installation notes; this file.
floppy.fs The i386 boot and installation
floppy; see below.
*.gz i386 binary distribution sets;
see below.
bsd A stock GENERIC i386 kernel which
will be installed on your system
during the install.
As well you may be interested in
.../2.1/tools/
miscellaneous i386 installation utilities like
rawwrite.exe, gzip.exe, and pfdisk.exe; see
installation section, below.
In summary, there is one i386 floppy image called "floppy.fs" (which
you can copy to a floppy using rawrite.exe or `dd'; as described later
in this document). This is a bootable install floppy which can be
used both to install and to upgrade OpenBSD to the current version.
It is also useful for maintenance and disaster recovery. In addition,
the "tools/" directory contains some utilities that might be useful
for the installation.
Bootable installation/upgrade floppy:
This disk contains a file system, is bootable, and has
enough utilities on board to prepare your hard disk drive
for OpenBSD and to install the OpenBSD distribution.
It also holds the utilities needed in order to upgrade a
system to the current version of OpenBSD.
The OpenBSD/i386 binary distribution sets contain the binaries which
comprise the OpenBSD 2.1 release for the i386. There are seven binary
distribution sets. The binary distribution sets can be found in
subdirectories of the "i386/bins" subdirectory of the OpenBSD 2.1
distribution tree, and are as follows:
base21 The OpenBSD/i386 2.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.
[ 12.5M gzipped, 35.1M uncompressed ]
comp21 The OpenBSD/i386 Compiler tools. All of the tools
relating to C, C++, and FORTRAN (yes, there are two!).
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.
[ 7.7M gzipped, 24.2M uncompressed ]
etc21 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.)
[ 92K gzipped, 450K uncompressed ]
game21 This set includes the games and their manual pages.
[ 2.8M gzipped, 6.7M uncompressed ]
man21 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.
[ 2.5M gzipped, 9.6M uncompressed ]
misc21 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.7M gzipped, 6.1M uncompressed ]
text21 This set includes OpenBSD's text processing tools,
including groff, all related programs, and their
manual pages.
[ 1.0M gzipped, 3.5M uncompressed ]
OpenBSD System Requirements and Supported Devices:
--------------------------------------------------
OpenBSD/i386 2.1 runs on ISA (AT-Bus), EISA, PCI, and VL-bus systems
with 386-family processors, with or without math coprocessors. It
does NOT support MCA systems, such as some IBM PS/2 systems. The
minimal configuration is said to require 4M of RAM and 50M of disk space,
though we do not know of anyone running with a system quite this minimal today.
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 run X and/or compile, but it won't be speedy.
Note that until you have around 16M of RAM, getting more RAM is more
important than getting a faster CPU.)
Supported devices include:
Floppy controllers.
MFM, ESDI, IDE, and RLL hard disk controllers.
SCSI host adapters:
Adaptec AHA-154xA, -B, -C, and -CF
Adaptec AHA-174x
Adaptec AIC-6260 and AIC-6360 based boards, including
the Adaptec AHA-152x and the SoundBlaster SCSI
host adapter. (Note that you cannot boot from
these boards if they do not have a boot ROM;
only the AHA-152x and motherboards using this chip
are likely to be bootable, consequently.)
Adaptec AHA-294x[W] cards and some onboard PCI designs using
the AIC7870 chip. This driver does *not* currently
work with non-PCI AIC-7xxx boards or the Adaptec 3940.
Buslogic 54x (Adaptec AHA-154x clones; driver on kcadp floppy)
BusLogic 445, 74x, 9xx (But not the new "FlashPoint" series
of BusLogic SCSI adapters)
Symbios Logic (NCR) 53C8xx-based PCI SCSI host adapters
Ultrastor 14f, 34f, and (possibly) 24f
Seagate/Future Domain ISA SCSI adapter cards, including
ST01/02
Future Domain TMC-885
Future Domain TMC-950
MDA, CGA, VGA, SVGA, and HGC Display Adapters. (Note that not
all of the display adapters OpenBSD/i386 can work with
are supported by X. See the XFree86 FAQ for more
information.)
Serial ports:
8250/16450-based ports
16550-based ports
AST-style 4-port serial boards [*]
BOCA 8-port serial cards [*]
Cyclades Cyclom-{4, 8, 16}Y serial boards [*]
IBM PC-RT 4-port serial boards [*]
Parallel ports.
Ethernet adapters:
AMD LANCE and PCnet-based ISA Ethernet adapters [*], including:
Novell NE1500T
Novell NE2100
Kingston 21xx
AMD PCnet-based PCI Ethernet adapters, including:
BOCALANcard/PCI
AT&T StarLAN 10, EN100, and StarLAN Fiber
3COM 3c501
3COM 3c503
3COM 3c505 [*]
3COM 3c507
3COM 3c509, 3c579, 3c589, 3c59x and 3c9xx
Digital DC21x4x-based PCI Ethernet adapters, including:
SMC EtherPower 10, 10/100 (PCI only!)
Znyx ZX34X
Cogent EM100
Digital DE450
Digital DE500
BICC Isolan [* and not recently tested]
Intel EtherExpress 16
SMC/WD 8003, 8013, and the SMC "Elite16" ISA boards
SMC/WD 8216 (the SMC "Elite16 Ultra" ISA boards) [X SEE BELOW]
Novell NE1000, NE2000
Digital DEFPA PCI FDDI adapters
Tape drives:
Most SCSI tape drives
QIC-02 and QIC-36 format (Archive- and Wangtek-
compatible) tape drives [*] [+]
CD-ROM drives:
Mitsumi CD-ROM drives [*] [+]
[Note: The Mitsumi driver device probe is known
to cause trouble with several devices!]
Most SCSI CD-ROM drives
Mice:
"Logitech"-style bus mice [*] [+]
"Microsoft"-style bus mice [*] [+]
"PS/2"-style mice [*] [+]
Serial mice (no kernel support necessary)
Sound Cards:
SoundBlaster [*] [+]
Gravis Ulrasound and Ultrasound Max [*] [+]
[The following drivers are not extensively tested]
Personal Sound System [*] [+]
Windows Sound System [*] [+]
ProAudio Spectrum [*] [+]
Miscellaneous:
Drivers for hardware marked with "[*]" are NOT included on the
distribution floppies. Except as noted above, all other drivers are
present on both kernel-copy disks. Also, at the present time, the
distributed kernels support only one SCSI host adapter per machine.
OpenBSD normally allows more, though, so if you have more than one, you
can use all of them by compiling a custom kernel once OpenBSD is
installed.
Support for devices marked with "[+]" IS included in the "generic" kernels,
although it is not in the kernel on the installation floppy.
Hardware the we do NOT currently support, but get many questions
about:
Adaptec AIC-7770-based SCSI host adapters (including the
Adaptec AHA-274x, AHA-284x families).
NCR 5380-based SCSI host adapters.
APM power management -- if your system supports it, turn it off!
QIC-40 and QIC-80 tape drives. (Those are the tape drives
that connect to the floppy disk controller.)
WD-7000 SCSI host adapters.
PCI-PCI bridges and cards which include them, such as the AHA-394x
SCSI host adapter and some DC21x4x-based multi-Ethernet cards.
Multiprocessor Pentium and Pentium Pro systems. (Though they should
run fine using one processor only.)
Intel EtherExpress 100 Fast Ethernet adapters.
We are planning future support for many of these devices.
To be detected by the distributed kernels, the devices must
be configured as follows:
Device Name Port IRQ DRQ Misc
------ ---- ---- --- --- ----
Serial ports com0 0x3f8 4 [8250/16450/16550/clones]
com1 0x2f8 3 [8250/16450/16550/clones]
com2 0x3e8 5 [8250/16450/16550/clones]
Parallel ports lpt0 0x378 7 [interrupt-driven or polling]
lpt1 0x278 [polling only]
lpt2 0x3bc [polling only]
MFM/ESDI/IDE/RLL hard disk controllers
wdc0 0x1f0 14 [supports two disks or atapi]
wdc1 0x170 15 [supports two disks or atapi]
Floppy controller
fdc0 0x3f0 6 2 [supports two disks]
AHA-154x, AHA-174x (in compatibility mode), or BT-54x SCSI host adapters
aha0 0x330 any any
AHA-174x SCSI host adapters (in enhanced mode)
ahb0 any any any
BT445, BT74x, or BT9xx SCSI host adapters
bt0 0x330 any any
Ultrastor 14f, 24f (if it works), or 34f SCSI host adapters
uha0 0x330 any any
AHA-152x, AIC-6260- or AIC-6360-based SCSI host adapters
aic0 0x340 11 6
Symbios Logic/NCR 53C8xx based PCI SCSI host adapters
ncr0 any any any
SCSI disks sd0 first SCSI disk (by SCSI id)
sd1 second SCSI disk (by SCSI id)
sd2 third SCSI disk (by SCSI id)
sd3 fourth SCSI disk (by SCSI id)
SCSI tapes st0 first SCSI tape (by SCSI id)
st1 second SCSI tape (by SCSI id)
SCSI CD-ROMs cd0 first SCSI CD-ROM (by SCSI id)
cd1 second SCSI CD-ROM (by SCSI id)
SMC/WD 8003, 8013, Elite16, and Elite16 Ultra Ethernet boards, 3c503,
Novell NE1000, or NE2000 Ethernet boards
ed0 0x280 2 iomem 0xd0000
ed1 0x250 2 iomem 0xd8000
ed2 0x300 10 iomem 0xcc000 [X SEE BELOW]
3COM 3c509, 3c579, 3c595 Ethernet boards (the 3c590 has problems)
ep0 any any
AT&T StarLAN 10, EN100, or StarLAN Fiber, or 3COM 3c507 Ethernet boards
ie0 0x360 7 iomem 0xd0000
PCNet-PCI based Ethernet boards; see above for partial list
le0 any any [you must assign an interrupt in your
PCI BIOS, or let it do so for you]
DC21x4x based Ethernet boards; see above for partial list
de0 any any [you must assign an interrupt in your
PCI BIOS, or let it do so for you]
SPECIAL CARE FOR SMC ULTRA ELITE
--------------------------------
Note for SMC Elite Ultra ethernet card users: The Elite Ultra is very
sensitive to how it's i/o port is treated. Mistreating it can cause
a number of effects -- everything from the card not responding when the
kernel probes, or the soft configuration being corrupted or wiped completely.
By default, the kernel ships with device ed2 configured for the 'default'
Elite Ultra locations, comprising of port 0x300, irq 10, and memory location
0xcc000. This matches a hard coded jumper on the board as well a common
soft config setting.
Unfortunately, the kernel's autconfiguration process (specifically, some
of the devices it probes for) cause conflicts with the SMC Elite Ultra, and
very often cause it to lose it's configuration and fail it's own probe.
If thise happens, you must boot the computer into DOS, and run the EzSetup
program available from SMC. The complete URL of which is
ftp://ftp.smc.com/pub/nics/ethernet/elite_ultra/gez122.exe. This program
will allow you to reconfigure and recover a card that has lost it's
configuration with a minimum of hassle.
In order to avoid blowing away the card, one *must* use the run-time kernel
configuration system when booting the Install kernel. This is done by
giving the -c flag to the initial boot request. Following the loading of
the kernel, the user is presented with a
UKC>
prompt. At this prompt, as variety of commands may be issued, but the
relevant one to getting the SMC Elite Ultra running is 'disable'. The
wt0, el0, and ie1 devices all need to be disabled. This is done by typing
'disable' followed by the name of the device, i.e., 'disable wt0', and
pressing return.
If, for some reason, your Elite Ultra is not configured at the 'default'
location the kernel is expecting it, you may also use the 'change' command
in the UKC system to modify where the kernel will look for it. Typing
'change ed2' will allow you to modify those settings. Note that running the
card at an i/o port of anything other then 0x300 at this point is not
recommended, and is beyond the scope of this document-- by doing so you
risk other device probes wreaking the havoc we are trying to avoid.
When all three extra devices are disabled and any changes made, the
'quit' command will exit the UKC. The kernel should then boot, and find
your Elite Ultra on device ed2.
Getting the OpenBSD System onto Useful Media:
---------------------------------------------
Installation is supported from several media types, including:
DOS partitions
FFS partitions
Tape
Remote NFS partition
FTP
HTTP
rsh & restore
No matter which installation medium you choose, you'll need to have
a floppy disk (1.44Mb required).
If you are using a UN*X-like system to write the floppy image to
disk, you should use the "dd" command to copy the file system image
(floppy.fs) directly to the raw floppy disks. It is suggested that
you read the dd(1) manual page or ask your system administrator to
determine the correct set of arguments to use; it will be slightly
different from system to system, and a comprehensive list of the
possibilities is beyond the scope of this document.
If you are using DOS to write the floppy image to disk, you should
use the "rawrite" utility, provided in the "i386/inst" directory of
the OpenBSD distribution. It will write the file system image
(floppy.fs) to a disk.
Note that when installing, the floppy can be write-protected (i.e.
read-only).
Obviously, the steps necessary to prepare the distribution sets for
installation or upgrade depend on which installation medium you
choose. The steps for the various media types are outlined below.
To install or upgrade OpenBSD using a tape, you need to do the
following:
To install OpenBSD from a tape, you need to make a tape that
contains the distribution set files, in "tar" format. If
you're making the tape on a UN*X-like system, the easiest way
to do so is probably something like:
tar cf
where "" is the name of the tape device that
describes the tape drive you're using (possibly /dev/rst0, or
something similar, but it will vary from system to system.
(If you can't figure it out, ask your system administrator.)
In the above example, "" are the
distribution sets' directories, for the distribution sets you
wish to place on the tape. For instance, to put the "base21"
and "etc21" distributions on tape (in order to do the absolute
minimum installation to a new disk), you would do the
following:
cd .../1.2 # the top of the tree
cd i386/
tar cf base21 etc21
(Note that you still need to fill in "" in the
example.)
Once you have the files on the tape, you can proceed to the
next step in the installation or upgrade process. If you're
installing OpenBSD from scratch, go to the section on preparing
your hard disk, below. If you're upgrading an existing
installation, go directly to the section on upgrading.
To install or upgrade 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 on
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 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're installing
OpenBSD from scratch, go to the section on preparing your hard
disk, below. If you're upgrading an existing installation, go
directly to the section on upgrading.
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
"base21" 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:
-----------------------------------------------
NOTE: If you wish to install OpenBSD on your whole disk, i.e. you do
not want DOS or any other operating system to reside on your hard
disk, you can skip this section and go on to the section that
describes installation, below. If you're upgrading your system from a
previous release of OpenBSD, you should have proceeded directly to the
section about upgrading; you need none of the information presented
here.
First and foremost, before beginning the installation process, MAKE
SURE YOU HAVE A RELIABLE BACKUP of any data on your hard disk that you
wish to keep. Repartitioning your hard disk is an excellent way to
destroy important data.
Second, if you are using a disk controller which supports disk geometry
translation, be sure to use the same parameters for OpenBSD as for DOS
or the other operating systems installed on your disk. If you do not,
it will be much harder to make OpenBSD properly coexist with them.
Utilities exist which will print out the disk geometry which DOS sees;
some versions of DOS "fdisk" also do this. If you have an "EIDE" hard
disk, DOS and OpenBSD probably won't see the same geometry, and you must
be careful to find out the DOS geometry and tell OpenBSD about it during
the installation.
Third (but related to the second point above), if you are using a hard
disk with more sectors than DOS or your controller's BIOS supports without
some kind of software translation utility or other kludge, you MUST
BE SURE that all partitions which you want to boot from must start and end
below cylinder 1024 by the BIOS's idea of the disk, and that all DOS
partitions MUST EXIST ENTIRELY BELOW cylinder 1024, or you will either not
be able to boot OpenBSD, not be able to boot DOS, or you may experience
data loss or filesystem corruption. Be sure you aren't using geometry
translation that you don't know about, but that the DOS "fdisk" program
does!
Fourth, use the other operating system's "fdisk" program or partition
editor to create at least one of the partitions to be used for that
operating system. If that operating system is already set up to use the
entire disk, you will have to back it up, remove and recreate a smaller
partition for it, and then restore the data from that partition. You do
not have to create an OpenBSD partition at this time, the OpenBSD install-
ation will give you an oppotunity to create the partition needed for
OpenBSD.
Finally, do whatever is necessary to restore order to the partition
you took space away from. If it was a DOS partition, you probably
will need to use "format" to create a new file system on it, and then
restore your important files from your backups. Other operating
systems will have different needs; most will need to reformat the
partition, and if it was their "main" partition, will probably need
to be reinstalled.
Your hard disk is now prepared to have OpenBSD installed on it, and
you should proceed with the installation instructions.
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.)
If OpenBSD will be sharing the disk with DOS or another operating
system, you should have already completed the section of these notes
that instructed you on how to prepare your hard disk. You should know
the size of the OpenBSD area of the disk and its offset from the
beginning of the disk. You will need this information when setting up
your OpenBSD partitions. If you BIOS uses translated geometry, you
should use this geometry for the remainder of the install. This is
only necessary if you are sharing the disk with other operating systems
that use the translated geometry.
You should now be ready to install OpenBSD. It might be handy for you
to have a pencil, some paper, and a calculator handy.
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.
Boot your machine using the floppy.fs floppy. When
presented with the boot prompt hit return. If the boot prompt
does not appear in a reasonable amount of time, you either
have a bad boot floppy or a hardware problem. Try writing the
floppy.fs floppy image to a different disk, and using that.
If that doesn't work, try booting after disabling your CPU's
internal and external caches (if any). If it still doesn't
work, OpenBSD probably can't be run on your hardware. This can
probably be considered a bug, so you might want to report it.
If you do, please include as many details about your system
configuration as you can.
It will take a while to load the kernel from the floppy,
most likely more than a minute. If some action doesn't
eventually happen, or the spinning cursor has stopped and
nothing further has happened, either your boot floppy is
bad or you are having hardware problems, and should proceed
as outlined above.
You will then 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's partitions. You will
also need to know the 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.
While booting, you will probably see several warnings. You
should be warned that no swap space is present, and that
init(8) cannot find /etc/rc. 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 presented with a welcome message and a prompt. At
this time you should enter the command "install" to start the
installation process.
You will be asked which terminal type to use, you should just
hit return to select the default (pc3).
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 "wd0" for IDE/RLL/ESDI/ST506
drives or "sd0" for SCSI drives. Reply with the name of your
disk.
Next you will have to edit or create a disklabel 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 and create an OpenBSD partition.
If fdisk is being invoked on your behalf, 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
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. 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. It is recommended that
you create separate partitions for /usr and /var, and if you have
room for it, also for /home.
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 if the disk is not being
shared with other operating systems, and within the OpenBSD fdisk
partition if the disk is being shared.
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 (eg.
"wd0") with the letter identifying the partition (eg. "d")
appended (eg. "wd0d"). Then it will ask where this partition is
to be mounted, eg. /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.
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 has 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 passive mode ftp? Most modern
ftp servers are capable of dealing with passive
ftp connections. You only need to enable this
option if you are behind a firewall that allows
outgoing ftp but blocks incoming tcp ports > 1023.
If in doubt say yes to this option.
Note that you will not be asked about passive
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.1 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.1/i386
is almost always correct.
5) The login and password for the ftp account.
The default will be correct unless you are
doing 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.1 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.
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
i386 this is "2.1/i386".
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 fast
file system (ffs) or MS-DOS.
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. If
any sets has already been extracted, those will be marked
with an X. Enter the name of one distribution set at a
time, until all desired distribution sets has been
installed on your system.
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.
(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 "base21" and "etc21" distribution sets.
Congratulations, you have successfully installed OpenBSD 2.1. When you
reboot into OpenBSD, you should log in as "root" at the login prompt.
There is no initial password, but if you're using the machine in a
networked environment, you should create yourself an account and
protect it and the "root" account with good passwords.
Some of the files in the OpenBSD 2.1 distribution might need to be
tailored for your site. In particular, the /etc/sendmail.cf file will
almost definitely need to be adjusted, and other files in /etc will
probably need to be modified, as well. 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:
------------------------------------------------
NOTE! If you are going to do the upgrade manually, you MUST use the
"-r" flag when invoking disklabel(8). You MUST also change the
partition table such that partition 'c' encompasses the entire drive,
and not only the OpenBSD partition. Finally, partition 'd' is no
longer special and can be used for any purpose whatsoever.
Also, OpenBSD now uses partition ID 0xA6 (166 decimal), but will
continue to work with 0xA5 for compatibility reasons. However, if
you change the partition ID to 0xA6, you will be able to share the
disk with 386BSD, FreeBSD or NetBSD. Note that the latter three can
NOT easily share the disk with each others.
To do the upgrade, you must have the appropriate kernel-copy floppy
image on a disk, and the upgr20.fs floppy image on another. You must
also have at least the "base20" 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 boot blocks on your OpenBSD
partition, 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:
Boot your machine using of the appropriate kernel-copy floppy.
When presented with the boot prompt (the prompt begins with
"Boot" and ends with ":-"), hit return.
You will be prompted to insert a file system floppy. Remove
the kernel-copy floppy and insert the upgr20 floppy, then hit
any key to continue booting.
While booting, you will probably see several warnings. You
should be warned that no swap space is present, and that
init(8) cannot find /etc/rc. 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 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.
You may be asked if you wish to upgrade your file systems to
the new file system format. If you do, reply affirmatively.
If you don't have your file systems upgraded now, you should
probably do it manually after the install process is complete,
by using "fsck -c 2". Read the fsck(8) manual page for more
details. Note that this step is only important when upgrading
from a pre-OpenBSD 1.0 release.
The upgrade program will then check your root file system,
and, if you approved, will upgrade it to the new file system
format. It will then mount your root file system on /mnt.
If your file systems are being upgraded, the upgrade script
will copy the new fsck(8) program to your hard disk and
upgrade your remaining file systems.
The upgrade program will then automatically replace the boot
blocks on your disk with newer versions, and mount all of your
file systems under /mnt. (In other words, your root partition
will be mounted on /mnt, your /usr partition on /mnt/usr, etc.)
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.
If you have only one floppy drive, and don't have the disk
space to copy all of the distribution onto the hard drive, you
can do the following:
Install a kernel on the hard drive as detailed a few
paragraphs below, then boot off the hard drive. Now
you can copy and install distribution sets
incrementally from your lone floppy drive.
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), change into the
directory containing the "base20" distribution set. Once you
are there, run the "Set_tmp_dir" command, and hit return at
the prompt to select the default answer for the temporary
directory's path name. (It should be the path name of the
directory that you're in.)
Run the command "Extract base20" to upgrade the base
distribution.
Repeat the above two steps for all of the sets you wish to
upgrade. (For each, change into the directory containing the
set, run "Set_tmp_dir" and accept the default path name, then
run the "Extract " command.)
If you were previously using the security distribution set,
you MUST upgrade to the new version, or you will not be able
to log in when the upgrade process is complete. Similarly, if
you were not previously using the security set, you must NOT
upgrade to the new version.
When you are done upgrading all of the distribution sets you
wish to upgrade, issue the command "Cleanup". It will clean
up the installation, by remaking some system databases. When
it is complete, you should use "halt" to halt the system.
When the system is halted, remove the "upgr20" floppy from
the floppy drive, and replace it with the OpenBSD 2.1
kernel-copy floppy that you previously booted from. Reboot
with that floppy.
Once again, you will be prompted to insert a file system
floppy. DO NOT replace the kernel-copy floppy, just hit any
key.
Again, While booting, you may see several warnings. You may
be warned that no swap space is present, that init(8) cannot
find /etc/rc, and that one or more databases with names like
"pwd.db" cannot be found. Do not be alarmed, as, again, these
are completely normal. Hit return at the prompt asking you
for a shell name.
You will be presented with a shell prompt, at which you should
enter the "copy_kernel" command. It will ask you what
partition to copy the kernel to, and you should reply with the
name of your root partition (e.g. sd0a or wd0a).
You will be asked if you are sure that you want to copy the
kernel. Reply affirmatively, and it will check the file
system on your root partition, mount it, and copy the kernel.
Once the kernel is copied, you should use "halt" to halt the
system.
Once the system is halted, remove the kernel-copy floppy from
the floppy disk drive, and hit any key to reboot.
Your system has now been upgraded to OpenBSD 2.1.
After a new kernel has been copied to your hard disk, your
machine is a complete OpenBSD 2.1 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.
Second, you will probably want to get the etc20 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.
Third, you will probably want to update the set of device
nodes you have in /dev. If you've changed the contents of
/dev by hand, you will need to be careful about this, but if
not, you can just cd into /dev, and run the command "sh
MAKEDEV all".
Fourth, 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. *IMPORTANT*: ANY INSTANCES OF "ufs"
IN /etc/fstab MUST BE CHANGED TO "ffs". 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 "ffs",
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. If you are
upgrading from a pre-1.0 OpenBSD, 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.
Administrivia:
--------------
There are various mailing lists available via the mailing list
server at . 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.