INSTALLATION NOTES for OpenBSD/landisk 5.2
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.
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 5.2 release
is available on the web at http://www.OpenBSD.org/52.html.
OpenBSD/landisk runs on various network appliances based on an
IO-DATA design with an Hitachi/Renesas SuperH CPU.
Sources of OpenBSD:
-------------------
This is a list of currently known FTP and HTTP servers at the time
of the 5.2 release. For a more recent list, please refer to
http://www.OpenBSD.org/ftp.html
Argentina:
http://openbsd.org.ar/pub/OpenBSD (Buenos Aires)
ftp://ftp.openbsd.org.ar/pub/OpenBSD (Buenos Aires)
Australia:
http://mirror.internode.on.net/pub/OpenBSD (Adelaide)
ftp://mirror.internode.on.net/pub/OpenBSD (Adelaide)
http://mirror.aarnet.edu.au/pub/OpenBSD (Brisbane)
ftp://mirror.aarnet.edu.au/pub/OpenBSD (Brisbane)
http://ftp.iinet.net.au/pub/OpenBSD (Perth)
ftp://ftp.iinet.net.au/pub/OpenBSD (Perth)
http://mirror.as24220.net/pub/OpenBSD (Melbourne)
ftp://mirror.as24220.net/pub/OpenBSD (Melbourne)
Austria:
http://ftp5.eu.openbsd.org/ftp/pub/OpenBSD (Vienna)
ftp://ftp5.eu.openbsd.org/pub/OpenBSD (Vienna)
http://ftp2.eu.openbsd.org/pub/OpenBSD (Vienna)
ftp://ftp2.eu.openbsd.org/pub/OpenBSD (Vienna)
Brazil:
http://openbsd.locaweb.com.br/pub/OpenBSD (Sao Paulo)
ftp://openbsd.locaweb.com.br/pub/OpenBSD (Sao Paulo)
Bulgaria:
http://mirror.telepoint.bg/OpenBSD (Sofia)
Canada:
http://ftp.OpenBSD.org/pub/OpenBSD (Alberta)
ftp://ftp.OpenBSD.org/pub/OpenBSD (Alberta)
Costa Rica:
http://mirrors.ucr.ac.cr/OpenBSD
ftp://mirrors.ucr.ac.cr/OpenBSD
Denmark:
http://ftp.openbsd.dk/pub/OpenBSD (Aalborg)
ftp://ftp.openbsd.dk/pub/OpenBSD (Aalborg)
Estonia:
http://ftp.aso.ee/pub/OpenBSD (Tallinn)
ftp://ftp.aso.ee/pub/OpenBSD (Tallinn)
France:
http://ftp.fr.openbsd.org/pub/OpenBSD (Paris)
ftp://ftp.fr.openbsd.org/pub/OpenBSD (Paris)
http://ftp.arcane-networks.fr/pub/OpenBSD (Paris)
ftp://ftp.arcane-networks.fr/pub/OpenBSD (Paris)
http://ftp2.fr.openbsd.org/pub/OpenBSD (Paris)
ftp://ftp2.fr.openbsd.org/pub/OpenBSD (Paris)
Germany:
http://openbsd.cs.fau.de/pub/OpenBSD (Erlangen)
ftp://openbsd.cs.fau.de/pub/OpenBSD (Erlangen)
http://ftp.spline.de/pub/OpenBSD (Berlin)
ftp://ftp.spline.de/pub/OpenBSD (Berlin)
ftp://ftp-stud.fht-esslingen.de/pub/OpenBSD (Esslingen)
http://ftp.bytemine.net/pub/OpenBSD (Oldenburg)
ftp://ftp.bytemine.net/pub/OpenBSD (Oldenburg)
http://ftp.halifax.rwth-aachen.de/openbsd (Aachen)
ftp://ftp.halifax.rwth-aachen.de/pub/OpenBSD (Aachen)
http://artfiles.org/openbsd (Hamburg)
Greece:
http://ftp.cc.uoc.gr/mirrors/OpenBSD (Heraklion)
ftp://ftp.cc.uoc.gr/mirrors/OpenBSD (Heraklion)
Hungary:
http://ftp.fsn.hu/pub/OpenBSD (Budapest)
ftp://ftp.fsn.hu/pub/OpenBSD (Budapest)
Ireland:
http://ftp.heanet.ie/pub/OpenBSD (Dublin)
ftp://ftp.heanet.ie/pub/OpenBSD (Dublin)
Japan:
http://ftp.jaist.ac.jp/pub/OpenBSD (Ishikawa)
ftp://ftp.jaist.ac.jp/pub/OpenBSD (Ishikawa)
http://www.ftp.ne.jp/OpenBSD (Saitama)
ftp://ftp.kddilabs.jp/OpenBSD (Saitama)
Korea:
http://mirror.yongbok.net/OpenBSD (Seoul)
ftp://mirror.yongbok.net/pub/OpenBSD (Seoul)
The Netherlands:
http://ftp.nluug.nl/pub/OpenBSD (Utrecht)
ftp://ftp.nluug.nl/pub/OpenBSD (Utrecht)
http://ftp.bit.nl/pub/OpenBSD (Ede)
ftp://ftp.bit.nl/pub/OpenBSD (Ede)
Norway:
http://baksmell.netrunner.nu/pub/OpenBSD (Trondheim)
ftp://baksmell.netrunner.nu/pub/OpenBSD (Trondheim)
Pakistan:
http://stingray.cyber.net.pk/pub/OpenBSD (Karachi)
ftp://stingray.cyber.net.pk/OpenBSD (Karachi)
Poland:
http://piotrkosoft.net/pub/OpenBSD (Oswiecim)
ftp://ftp.piotrkosoft.net/pub/OpenBSD (Oswiecim)
http://ftp.icm.edu.pl/pub/OpenBSD (Warszawa)
ftp://ftp.icm.edu.pl/pub/OpenBSD (Warszawa)
Russia:
http://mirror.corbina.net/pub/OpenBSD (Moscow)
ftp://mirror.corbina.net/pub/OpenBSD (Moscow)
Saudi Arabia:
http://mirrors.isu.net.sa/pub/ftp.openbsd.org (Riyadh)
ftp://mirrors.isu.net.sa/pub/ftp.openbsd.org (Riyadh)
Slovenia:
http://www.obsd.si/pub/OpenBSD (Ljubljana)
ftp://ftp.obsd.si/pub/OpenBSD (Ljubljana)
South Africa:
http://mirror.is.co.za/mirror/ftp.openbsd.org (Johannesburg)
ftp://ftp.is.co.za/mirror/ftp.openbsd.org (Johannesburg)
Spain:
http://mirror.cdmon.com/pub/OpenBSD (Barcelona)
ftp://mirror.cdmon.com/pub/OpenBSD (Barcelona)
Sweden:
http://ftp.eu.openbsd.org/pub/OpenBSD (Stockholm)
ftp://ftp.eu.openbsd.org/pub/OpenBSD (Stockholm)
http://ftp.netbsd.se/OpenBSD (Stockholm)
Switzerland:
http://mirror.switch.ch/ftp/pub/OpenBSD (Zurich)
ftp://mirror.switch.ch/pub/OpenBSD (Zurich)
http://ftp.ch.openbsd.org/pub/OpenBSD (Zurich)
ftp://ftp.ch.openbsd.org/pub/OpenBSD (Zurich)
Turkey:
ftp://ftp.ulak.net.tr/OpenBSD
United Kingdom:
http://www.mirrorservice.org/pub/OpenBSD (Kent)
ftp://ftp.mirrorservice.org/pub/OpenBSD (Kent)
http://mirror.bytemark.co.uk/OpenBSD (Manchester)
ftp://mirror.bytemark.co.uk/OpenBSD (Manchester)
USA:
http://ftp5.usa.openbsd.org/pub/OpenBSD (Redwood City, CA)
ftp://ftp5.usa.openbsd.org/pub/OpenBSD (Redwood City, CA)
http://ftp3.usa.openbsd.org/pub/OpenBSD (Boulder, CO)
ftp://ftp3.usa.openbsd.org/pub/OpenBSD (Boulder, CO)
http://mirror.team-cymru.org/pub/OpenBSD (Chicago, IL)
ftp://mirror.team-cymru.org/pub/OpenBSD (Chicago, IL)
http://mirror.planetunix.net/pub/OpenBSD (Chicago, IL)
ftp://mirror.planetunix.net/pub/OpenBSD (Chicago, IL)
http://filedump.se.rit.edu/pub/OpenBSD (Rochester, NY)
ftp://filedump.se.rit.edu/pub/OpenBSD (Rochester, NY)
http://openbsd.mirror.frontiernet.net/pub/OpenBSD (Rochester, NY)
ftp://openbsd.mirror.frontiernet.net/pub/OpenBSD (Rochester, NY)
http://ftp.lambdaserver.com/pub/OpenBSD (Chicago, Illinois)
ftp://ftp.lambdaserver.com/pub/OpenBSD (Chicago, Illinois)
http://openbsd.mirrors.hoobly.com (Pittsburgh, PA)
http://mirror.ece.vt.edu/pub/OpenBSD (Blacksburg, VA)
http://mirror.servihoo.net/pub/OpenBSD (Kansas City, MO)
ftp://mirror.servihoo.net/pub/OpenBSD (Kansas City, MO)
http://openbsd.mirrors.pair.com (Pittsburgh, PA)
ftp://openbsd.mirrors.pair.com (Pittsburgh, PA)
http://mirrors.gigenet.com/pub/OpenBSD (Arlington Heights, IL)
ftp://mirrors.gigenet.com/pub/OpenBSD (Arlington Heights, IL)
http://mirror.esc7.net/pub/OpenBSD (Dallas, TX)
ftp://mirror.esc7.net/pub/OpenBSD (Dallas, TX)
http://openbsd.mirrorcatalogs.com/pub/OpenBSD (Denver, CO)
ftp://openbsd.mirrorcatalogs.com/pub/OpenBSD (Denver, CO)
http://mirrors.nycbug.org/pub/OpenBSD (New York City, NY)
ftp://mirrors.nycbug.org/pub/OpenBSD (New York City, NY)
http://mirrors.syringanetworks.net/pub/OpenBSD (Boise, ID)
ftp://mirrors.syringanetworks.net/pub/OpenBSD (Boise, ID)
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 5.2 Release Contents:
-----------------------------
The OpenBSD 5.2 release is organized in the following way. In the
.../5.2 directory, for each of the architectures having an OpenBSD 5.2
binary distribution, there is a sub-directory.
The landisk-specific portion of the OpenBSD 5.2 release is found in the
"landisk" subdirectory of the distribution. That subdirectory is laid
out as follows:
.../5.2/landisk/
INSTALL.landisk Installation notes; this file.
SHA256 Output of the sum(1) program using the option
-a sha256, usable for verification of the
correctness of downloaded files.
miniroot52.fs A miniroot filesystem image to be copied to
the beginning of the disk to allow installing
OpenBSD 5.2.
*.tgz landisk binary distribution sets; see below.
bsd A stock GENERIC landisk kernel which will be
installed on your system during the install.
bsd.rd A compressed RAMDISK kernel; the embedded
filesystem contains the installation tools.
Used for simple installation from a pre-existing
system.
The OpenBSD/landisk binary distribution sets contain the binaries which
comprise the OpenBSD 5.2 release for landisk systems. There are ten
binary distribution sets. The binary distribution sets can be found in
the "landisk" subdirectory of the OpenBSD 5.2 distribution tree,
and are as follows:
base52 The OpenBSD/landisk 5.2 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.
[ 51.8 MB gzipped, 155.5 MB uncompressed ]
comp52 The OpenBSD/landisk Compiler tools. All of the tools relating
to C, C++ and Objective-C 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.
[ 96.0 MB gzipped, 274.2 MB uncompressed ]
etc52 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.)
[ 512.6 KB gzipped, 1.5 MB uncompressed ]
game52 This set includes the games and their manual pages.
[ 2.5 MB gzipped, 5.6 MB uncompressed ]
man52 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.
[ 9.0 MB gzipped, 34.9 MB uncompressed ]
xbase52 This set includes the base X distribution. This includes
programs, headers and libraries.
[ 14.9 MB gzipped, 40.3 MB uncompressed ]
xetc52 This set includes the X window system configuration files
that reside in /etc. It's the equivalent of etc52 for X.
[ 70.6 KB gzipped, 266.7 KB uncompressed ]
xfont52 This set includes all of the X fonts.
[ 37.5 MB gzipped, 48.5 MB uncompressed ]
xserv52 This set includes all of the X servers.
[ 2.1 MB gzipped, 4.7 MB uncompressed ]
xshare52 This set includes all text files equivalent between all
architectures.
[ 3.2 MB gzipped, 17.5 MB uncompressed ]
OpenBSD System Requirements and Supported Devices:
--------------------------------------------------
OpenBSD/landisk runs on the following SH4-based IO-DATA made models:
IO-DATA USL-5P, using CF storage (Japan)
IO-DATA HDL-U, HDL-AV, HDL-W and HDLM-U series (Japan)
SuperTank LAN Tank (SOTO-HDLWU) (Japan)
IO-DATA UHDL-160U and UHDL-300U (May be found in USA)
Plextor PX-EH16L, PX-EH25L and PX-EH40L
Supported devices include:
Ethernet Adapters
ADMtek AN986-based USB adapters, including:
Abocom UFE1000
Abocom DSB650TX
Accton USB320-EC
Accton SpeedStream Ethernet
Admtek Pegasus, Pegasus II
Billionton Systems USB100
Corega FEther USB-TX
D-Link DSB-650, 650TX, 650TX-PNA
Elecom LD-USB
Elsa Microlink USB2Ethernet
I/O Data USB ETTX
Kingston KNU101TX
Linksys USB100TX, USB100H1 and USB10TA
Melco Inc. LUA-TX
Siemens SpeedStream USB
SmartBridges smartNIC 2
SMC 2202USB/ETH
SMC 2206USB/ETH
SOHOware NUB100
ASIX Electronics AX88172/AX88178/AX88772 USB Ethernet adapters,
including:
ATEN UC210T
BAFO BF-320
Billionton Systems USB2AR
Buffalo(MELCO) LUA-U2-KTX
Corega FEther USB2-TX
D-Link DUB-E100
Good Way GWUSB2E
Hawking UF200
Intellinet USB 2.0 to Ethernet (rev A)
IO-Data ETG-US2
JVC MP-PRX1
Level One USB-0200
Linksys USB200M
Netgear FA120
Nintendo Wii USB Lan Ethernet Adapter RVL-015
OQO model 01+ Ethernet
Sitecom LN-029
SMC 2209USB/ETH
SnapPort USB 2.0 LAN Adapter
ST Lab USB 2.0 Fast Ethernet
Surecom EP-1427X-2
System TALKS SGC-X2UL
TRENDnet TU2-ET100
Z-TEK ZK-R01-2
CATC USB-EL1210A-based USB adapters, including:
CATC Netmate and Netmate II
Belkin F5U011/F5U111
Davicom DM9601 based USB adapters, including:
Corega FEther USB-TXC
HenTong WK-668
ShanTou ST268
Kawasaki LSI KL5KUSB101B-based USB adapters, including:
3Com 3c19250
3Com 3c460 HomeConnect
AboCom Systems URE450 Ethernet
ADS Technologies USB-10T
Aox USB101
Asante USB to Ethernet
ATen DSB-650C
ATen UC10T
Corega USB-T
D-Link DSB-650C
Entegra NET-USB-E45
I/O Data USB-ET/T
Jaton USB XpressNet
Kawasaki USB101
Kingston Ethernet
Linksys USB10T
Mobility Ethernet
Netgear EA101
Peracom USB
Portgear Ethernet
Portsmith Express Ethernet
Psion Dacom Gold Port Ethernet
Shark Pocket Adapter
Silicom U2E
SMC 2102/2104USB
RealTek RTL8150L based USB adapters, including:
Abocom RTL8151
BAFO BF-310
Billionton USBKR-100
Compex UE202-B
GreenHouse GH-USB100B
GreenHouse GH-USB100B with HomePNA
Hawking Technology HUF11
Linksys USB100M
Longshine LCS-8138TX
Melco Inc. LUA-KTX
Micronet SP128AR
NetComm NP1010
Repotec RP-USB100-A
SMC 2208USB/ETH
TRENDnet TU-ET100C
Zt USB10/100
Z-TEK ZK-R02
Wireless Ethernet Adapters
Atheros USB IEEE 802.11a/b/g adapters
Atmel AT76C50x based USB IEEE 802.11b adapters
Intersil PRISM 2.5/3 based USB IEEE 802.11b adapters
Ralink RT2500 based USB 2.0 IEEE 802.11b/g adapters
Ralink RT2501USB/RT2601USB USB 2.0 IEEE 802.11/a/b/g adapters
Ralink Technology USB IEEE 802.11a/b/g/Draft-N USB adapters
ZyDAS ZD1211/ZD1211B USB IEEE 802.11b/g adapters
Serial ports
On-board serial (scif) port
Universal Serial Bus (USB) Devices
USB Audio
USB Diamond Multimedia Rio MP3 players
USB Ethernet adapters, see above
USB Generic Human Interface Devices (catch-all)
USB Handspring Visor
USB Hubs
USB Keyboards
USB Mass Storage devices, i.e., USB floppy drives and
USB memory stick controllers
USB Mice
USB Modems
USB Printers
USB Scanners
USB-USB cables
USB Y@p phone
Getting the OpenBSD System onto Useful Media:
---------------------------------------------
Installation is supported from several media types, including:
CD-ROM
FFS partitions
DOS (FAT) partitions
EXT2 partitions
FTP
HTTP
Although you can access the distribution sets directly from the CD-ROM or
from one of the FTP mirrors over the internet, you may wish to transfer
the sets to a local FTP server, or copy them to a partition on the target
system's disk (for upgrades only).
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.
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 "base52" set somewhere in your file system. It
is recommended that you upgrade the other sets, as well.
Preparing your System for OpenBSD Installation:
-----------------------------------------------
The default configuration of the landisk systems comes with a Linux
installation on the disk (either an IDE hard drive, or a CompactFlash
card). At the moment, there is no known way to log in this installation
as ``root'' or interrupt the boot process, and start an OpenBSD
installation procedure.
Because of this, the only way to boot the OpenBSD install is to copy
the miniroot "miniroot52.fs" image to the hard drive or CompactFlash
(on the other hand, upgrades can be started by copying bsd.rd to the
OpenBSD disk and booting from it).
As a result, you will need another machine to plug the machine's disk
or CompactFlash in. Any machine type will do, as long as it supports
ATA-compatible storage devices, regardless of the partition scheme
it uses. Under OpenBSD, it will appear as a ``wd'' device, for example
``wd1''.
Use the dd(1) utility to copy the miniroot to the hard drive.
The command would likely be, under OpenBSD:
dd if=miniroot52.fs of=/dev/rwd1c
Replace ``rwd1c'' with the appropriate device name for the raw device
on the system used to do the copy.
If the machine has a hard drive, and you had to change jumpers on it
to change its ``master'' status, do not forget to configure it back
to ``master'' or ``single drive'', as slave drives are not bootable.
In addition to the disk preparation, you will need to connect a serial
port connector to the machine. Please refer to the OpenBSD/landisk
page at
http://www.OpenBSD.org/landisk.html
for more information.
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.
The installation procedure is designed to gather as many information about
your system setup as possible at the beginning, so that no human interaction
is required as soon as the questions are over.
The order of these questions might be quite disconcerting if you are used to
other installation procedures, including older OpenBSD versions.
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 will occur,
though).
If you have copied the miniroot image to the disk, it will
boot automatically upon power-up.
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 "wd0".
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.
After the kernel is done initialization, 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 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 vt220).
The first question you will be asked is the system hostname.
Reply with the name of the system, without any domain part.
You will now be given 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.
The install program will give you a list of network interfaces you
can configure. For each network interface you select to configure,
you will be asked for:
- the symbolic host name to use (except for the first
interface setup, which will reuse the host name entered at the
beginning of the installation).
- the IPv4 settings: address and netmask. If the IP address
should be obtained from a DHCP server, simply enter ``dhcp''
when asked for the address.
- the IPv6 settings (address, prefix length, and default router).
You may enter ``rtsol'' when asked for the address for the
interface to configure automatically via router solicitation
messages.
After all interfaces have been configured, if there have been
any IPv4 interfaces setup, you will be asked for the IPv4 default
route. This step is skipped if you only have one IPv4 interface
setup, and it is configured with DHCP.
The install program will also ask you for your DNS domain name,
and the domain name servers, unless this information has
already been obtained from a DHCP server during interface setup.
You will also be presented with an opportunity to do more
manual configuration. If you accept, you will be dropped
to a shell; when you are done, enter `exit' to return to
the installation program.
You will then be asked to enter the initial root password
of the system, twice.
Although the install program will only check that the two
passwords match, you should make sure to use a strong password.
As a minimum, the password should be at least eight characters
long and a mixture of both lower and uppercase letters, numbers
and punctuation characters.
You will then be asked whether you want to start sshd(8) by
default, as well as ntpd(8). If you choose to start ntpd(8),
you will be asked for your ntp server; if you don't have any
preferred ntp server, press enter to confirm the default
setting of using the pool.ntp.org servers.
You will now be given the possibility to setup a user account
on the forthcoming system. This user will be added to the
`wheel' group.
Enter the desired login name, or `n' if you do not want to
add a user account at this point. Valid login names are
sequences of digits and lowercase letters, and must start
with a lowercase letter. If the login name matches this
criteria, and doesn't conflict with any of the administrative
user accounts (such as `root', `daemon' or `ftp'), you
will be prompted with the users descriptive name, as well
as its password, twice.
As for the root password earlier, the install program will only
check that the two passwords match, but you should make sure to
use a strong password here as well.
If you have chosen to setup a user account, and you had chosen
to start sshd(8) on boot, you will be given the possibility to
disable sshd(8) logins as root.
The installation program will now tell you which disks it can
install on, and ask you which it should use.
Reply with the name of your root disk.
You will the be asked if you want to use DUID notation in
/etc/fstab, instead of traditional device names. You are strongly
advised to use DUIDs, as they allow you to move your disks to
different controllers, or change their bus identifiers, without
having to modify /etc/fstab every time your configuration changes.
Disks on OpenBSD/landisk are partitioned using the so-called
``MBR'' partitioning scheme. You will need to create one
MBR partition, in which all the real OpenBSD partitions will
be created.
The installation program will ask you if you want to use the
whole disk for OpenBSD. If you don't need to or don't intend
to share the disk with other operating systems, answer `w'
here. The installation program will then create a single
MBR partition spanning the whole disk, dedicated to OpenBSD.
Otherwise, fdisk(8) will be invoked to let you to edit your MBR
partitioning. The current MBR partitions defined will be
displayed and you will be allowed to modify them, add new
partitions, and change which partition to boot from by default.
Note that you should make the OpenBSD partition the active
partition at least until the install has been completed.
After your OpenBSD MBR partition has been setup, the real
partition setup can follow.
Next the disk label which defines the layout of the OpenBSD
partitions must be set up. Each file system you want will
require a separate partition.
You will be proposed a default partition layout, trying
to set up separate partitions, disk size permitting.
You will be given the possibility to either accept the proposed
layout, or edit it, or create your own custom layout. These last
two choices will invoke the disklabel(8) interactive editor,
allowing you to create your desired layout.
Within the editor, you will probably start out with only the
'c' partition of fstype 'unused' that represents the whole disk.
This partition can not be modified.
You must create partition 'a' as a native OpenBSD partition, i.e.
one with "4.2BSD" as the fstype, to hold the root file system.
In addition to partition 'a' you should create partition 'b' with
fstype "swap", and native OpenBSD partitions to hold separate file
systems such as /usr, /tmp, /var, and /home.
You will need to provide a mount point for all partitions you
define. Partitions without mount points, or not of 4.2BSD fstype,
will neither be formatted nor mounted during the installation.
For quick help while in the interactive editor, enter '?'. The
`z' command (which deletes all partitions and starts with a
clean label), the `A' command (which performs the automatic
partition layout) and the `n' command (to change mount points)
are of particular interest.
Although the partitions position and size are written in exact
sector values, you do not need a calculator to create your
partitions! Human-friendly units can be specified by adding `k',
`m' or `g' after any numbers to have them converted to kilobytes,
megabytes or gigabytes. Or you may specify a percentage of the
disk size using `%' as the suffix.
Enter 'M' to view the entire manual page (see the info on the
``-E'' flag). To exit the editor enter 'q'.
After the layout has been saved, new filesystems will be
created on all partitions with mount points.
This will DESTROY ALL EXISTING DATA on those partitions.
After configuring your root disk, the installer will
return to the list of available disks to configure.
You can choose the other disks to use with OpenBSD in
any order, and will get to setup their layout similarly
to the root disk above. However, for non-root disks,
you will not be proposed a default partition layout.
When all your disks are configured, simply hit return
at the disk prompt.
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, CD-ROM, tape, or a local disk partition.
To install via FTP or HTTP:
To begin an FTP or HTTP install you will need the following
pieces of information:
1) Proxy server URL if you are using a URL-based FTP or
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 FTP or HTTP connections
(assuming you have a proxy available to use).
2) The IP address (or hostname if you configured
DNS servers earlier in the install) of an FTP or HTTP
server carrying the OpenBSD 5.2 distribution.
The installation program will try to fetch a list
of such servers; depending on your network settings,
this might fail. If the list could be fetched, it
will be displayed, and you can choose an entry from
the list (the first entries are expected to be the
closest mirrors to your location).
3) The directory holding the distribution sets.
The default value of pub/OpenBSD/5.2/landisk
is almost always correct on FTP servers; for HTTP
servers there is no standard location for this.
4) For FTP installs only, the login and password for the
FTP account. You will only be asked for a password for
non-anonymous FTP.
Then refer to the section named "installation set selection"
below.
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". If there is more than one partition on the
CD-ROM, you will be asked which partition the distribution
is to be loaded from. This is normally partition "a".
You will also have to provide the relative path to the
directory on the CD-ROM which holds the distribution, for
the landisk this is "5.2/landisk".
Then refer to the section named "installation set selection"
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.
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 have been formatted as the
Berkeley fast file system (ffs), Linux (ext2) 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 '/'.
Then refer to the next section.
Installation set selection:
A list of available distribution sets found on the
given location will be listed.
You may individually select distribution sets to install,
by entering their name, or wildcards (e.g. `*.tgz' or
`base*|comp*', or `all' to select all the sets (which
is what most users will want to do).
You may also enter `abort' to deselect everything and
restart the selection from scratch, or unselect sets
by entering their name prefixed with `-' (e.g. `-x*').
It is also possible to enter an arbitrary filename and
have it treated as a file set.
When you are done selecting distribution sets, enter
`done'. The files will begin to extract.
After the files have been extracted, you will be given the choice
to select a new location from which to install distribution sets.
If there have been errors extracting the sets from the previous
location, or if some sets have been missing, this allows you to
select a better source.
Also, if the installation program complains that the distribution
sets you have been using do not match their recorded checksums, you
might want to check your installation source (although this can
happen between releases, if a snapshot is being updated on an FTP
or HTTP server with newer files while you are installing).
The last thing you'll need to configure is the time zone your system
will be using. For this to work properly, it is expected that you
have installed at least the "base52", "etc52",
and "bsd" distribution sets.
The installation program will then proceed to save the system
configuration, create all the device nodes needed by the installed
system, and will install bootblocks on the root disk.
Finally, you will be asked whether you would like to install
non-free firmware files (which can't be tightly integrated to
the OpenBSD system) on first boot, by invoking fw_update(8) on
the next boot.
Congratulations, you have successfully installed OpenBSD 5.2. 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 5.2 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 5.2 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. As a minimum, if the toolchain (the ``comp'' set) was installed,
you should remove all files within /usr/include before attempting to
upgrade.
To upgrade OpenBSD 5.2 from a previous version, start with the general
instructions in the section "Installing OpenBSD".
Boot from bsd.rd on the boot disk.
When prompted, select the (U)pgrade option rather than the (I)nstall
option at the prompt in the install process.
You will be presented with a welcome message and asked if you really wish
to upgrade.
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 neither the ``etc52.tgz'' nor the
``xetc52.tgz'' sets, 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 etc52.tgz and
xetc52.tgz sets in a temporary directory and merge changes by hand, or
with the help of the sysmerge(8) helper script, 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, CVSync or FTP. For more information, see
http://www.OpenBSD.org/anoncvs.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) Use the OpenBSD ``package'' collection to grab a pre-compiled
and tested version of the application for your hardware.
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) Obtain the source code and build the application based
upon whatever installation procedures are provided with the
application.
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
5.2/packages/sh 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/5.2/packages/sh/<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/5.2/packages/sh/
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/5.2/packages/sh/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/faq/ports/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
look at the FreeBSD ports or NetBSD pkgsrc for inspiration.
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 in the OpenBSD Porter's Handbook at
http://www.openbsd.org/faq/ports/
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.
More information about the various OpenBSD mailing list and proper
netiquette is available at
http://www.OpenBSD.org/mail.html
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
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