INSTALLATION NOTES for OpenBSD/macppc 3.9
What is OpenBSD?
----------------
OpenBSD is a fully functional, multi-platform UN*X-like Operating
System based on Berkeley Networking Release 2 (Net/2) and 4.4BSD-Lite.
There are several operating systems in this family, but OpenBSD
differentiates itself by putting security and correctness first. The
OpenBSD team strives to achieve what is called a 'secure by default'
status. This means that an OpenBSD user should feel safe that their
newly installed machine will not be compromised. This 'secure by
default' goal is achieved by taking a proactive stance on security.
Since security flaws are essentially mistakes in design or implement-
ation, the OpenBSD team puts as much importance on finding and fixing
existing design flaws and implementation bugs as it does writing new
code. This means that an OpenBSD system will not only be more secure,
but it will be more stable. The source code for all critical system
components has been checked for remote-access, local-access, denial-
of-service, data destruction, and information-gathering problems.
In addition to bug fixing, OpenBSD has integrated strong cryptography
into the base system. A fully functional IPsec implementation is
provided as well as support for common protocols such as SSL and SSH.
Network filtering and monitoring tools such as packet filtering, NAT,
and bridging are also standard, as well as several routing services,
such as BGP and OSPF. For high performance demands, support for
hardware cryptography has also been added to the base system. Because
security is often seen as a tradeoff with usability, OpenBSD provides
as many security options as possible to allow the user to enjoy secure
computing without feeling burdened by it.
To integrate more smoothly in other environments, OpenBSD 3.9 also
provides, on some platforms, several binary emulation subsystems
(which includes iBCS2, Linux, OSF/1, SunOS, SVR4, Solaris, and Ultrix
compatibility), aiming at making the emulation as accurate as possible
so that it is transparent to the user.
Because OpenBSD is from Canada, the export of Cryptography pieces
(such as OpenSSH, IPsec, and Kerberos) to the world is not restricted.
(NOTE: OpenBSD can not be re-exported from the US once it has entered
the US. Because of this, take care NOT to get the distribution from
an FTP server in the US if you are outside of Canada and the US.)
A comprehensive list of the improvements brought by the 3.9 release
is available on the web at http://www.OpenBSD.org/39.html.
OpenBSD/macppc runs on the ``New World'' 32 bit PowerPC-based Apple
Macintosh systems (i.e. from the iMac onwards).
Sources of OpenBSD:
-------------------
This is a list of currently known FTP servers at the time of the 3.9 release.
For a more recent list, please refer to
http://www.OpenBSD.org/ftp.html
Main server in Canada:
ftp://ftp.OpenBSD.org/pub/OpenBSD (Alberta)
Argentina:
ftp://ftp.openbsd.md5.com.ar/pub/OpenBSD (Buenos Aires)
ftp://mirrors.localhost.net.ar/pub/OpenBSD (Buenos Aires)
Australia:
ftp://mirror.aarnet.edu.au/pub/OpenBSD (Canberra, .au only)
ftp://ftp.it.net.au/mirrors/OpenBSD (Perth)
ftp://ftp.planetmirror.com/pub/OpenBSD (Sydney)
ftp://mirror.pacific.net.au/OpenBSD (Sydney)
ftp://openbsd.wiretapped.net/pub/OpenBSD (Sydney)
Austria:
ftp://gd.tuwien.ac.at/opsys/OpenBSD (Vienna)
ftp://ftp.catai.net/pub/OpenBSD (Vienna)
ftp://ftp.kd85.com/pub/OpenBSD (Vienna)
Belgium:
ftp://ftp.scarlet.be/pub/openbsd
ftp://ftp.belnet.be/packages/openbsd (Brussels)
Brazil:
ftp://ftp.openbsd.org.br/pub/OpenBSD (Curitiba)
ftp://ftp.das.ufsc.br/pub/OpenBSD (Santa Catarina)
Bulgaria:
ftp://ftp.bg.openbsd.org/pub/OpenBSD (Plovdiv)
Canada:
ftp://ftp.ca.openbsd.org/pub/OpenBSD (Edmonton)
Czech Republic:
ftp://ftp.openbsd.cz/pub/OpenBSD (Prague)
Denmark:
ftp://mirrors.dotsrc.org/openbsd (Aalborg)
ftp://ftp.dkuug.dk/pub/OpenBSD (Copenhagen)
Finland:
ftp://ftp.jyu.fi/pub/OpenBSD (Jyvaskyla)
France:
ftp://ftp.ac-creteil.fr/OpenBSD
ftp://ftp.crans.org/pub/OpenBSD (Paris)
Germany:
ftp://ftp.de.openbsd.org/unix/OpenBSD (Berlin)
ftp://ftp.freenet.de/pub/ftp.openbsd.org/pub/OpenBSD (Duesseldorf)
ftp://openbsd.informatik.uni-erlangen.de/pub/OpenBSD (Erlangen)
ftp://ftp-stud.fht-esslingen.de/pub/OpenBSD (Esslingen)
ftp://openbsd.bay13.net/pub/OpenBSD (Hamburg)
ftp://ftp.leo.org/pub/OpenBSD (Muenchen)
ftp://ftp.bytemine.net/pub/OpenBSD (Oldenburg)
Greece:
ftp://filoktitis.noc.uoa.gr/pub/OpenBSD (Athens)
ftp://ftp.physics.auth.gr/pub/mirrors/OpenBSD/OpenBSD (Thessaloniki)
ftp://ftp.duth.gr/pub/OpenBSD (Thrace)
Ireland:
ftp://ftp.esat.net/pub/OpenBSD (Dublin)
Italy:
ftp://ftp.unina.it/pub/OpenBSD (Napoli)
Japan:
ftp://ftp.netlab.is.tsukuba.ac.jp/pub/os/OpenBSD (Ibaraki)
ftp://ftp.jaist.ac.jp/pub/OpenBSD (Ishikawa)
ftp://ftp.nara.wide.ad.jp/pub/OpenBSD (Nara)
ftp://ftp.iij.ad.jp/pub/OpenBSD (Tokyo)
ftp://ftp.jp.openbsd.org/pub/OpenBSD (Tokyo)
ftp://ftp.kddlabs.co.jp/OpenBSD (Tokyo)
Latvia:
ftp://ftp.secure.lv/pub/OpenBSD
ftp://ftp.bsd.lv/pub/OpenBSD (Riga)
Lithuania:
ftp://ftp.openbsd.lt/pub/OpenBSD
The Netherlands:
ftp://ftp.nl.uu.net/pub/OpenBSD (Amsterdam)
ftp://ftp.calyx.nl/pub/OpenBSD (Amsterdam)
ftp://muk.kd85.com/pub/OpenBSD (Amsterdam)
ftp://ftp.nluug.nl/pub/OpenBSD (Utrecht)
Norway:
ftp://ftp.inet.no/pub/OpenBSD (Oslo)
Poland:
ftp://sunsite.icm.edu.pl/pub/OpenBSD
Portugal:
ftp://ftp.fmed.uc.pt/pub/OpenBSD
Romania:
ftp://mirrors.evolva.ro/OpenBSD (Bucharest)
ftp://mirrors.obs.utcluj.ro/pub/OpenBSD (Cluj-Napoca)
ftp://ftp.physics.uvt.ro/pub/OpenBSD (Timisoara)
Russia:
ftp://ftp.chg.ru/pub/OpenBSD (Chernogolovka-Moscow)
ftp://ftp.radio-msu.net/pub/OpenBSD (Moscow)
South Africa:
ftp://ftp.is.co.za/pub/OpenBSD (Johannesburg)
Spain:
ftp://ftp.rediris.es/mirror/OpenBSD (Madrid)
Sweden:
ftp://ftp.su.se/pub/OpenBSD (Stockholm)
ftp://ftp.stacken.kth.se/pub/OpenBSD (Stockholm)
ftp://ftp.btradianz.se/pub/OpenBSD (Stockholm)
ftp://ftp.sunet.se/pub/OpenBSD (Uppsala)
Switzerland:
ftp://mirror.switch.ch/pub/OpenBSD (Zurich)
Taiwan:
ftp://openbsd.cc.ntu.edu.tw/pub/OpenBSD (NTU)
Thailand:
ftp://ftp.ce.kmitl.ac.th/pub/OpenBSD (Bangkok)
Turkey:
ftp://ftp.enderunix.org/pub/OpenBSD (Istanbul)
Ukraine:
ftp://ftp.openbsd.org.ua/pub/OpenBSD (Kiev)
United Kingdom:
ftp://ftp.plig.org/pub/OpenBSD (London)
USA:
ftp://ftp5.usa.openbsd.org/pub/OpenBSD (Redwood City, CA)
ftp://ftp3.usa.openbsd.org/pub/OpenBSD (Boulder, CO)
ftp://mirror.sg.depaul.edu/pub/OpenBSD (Chicago, IL)
ftp://rt.fm/pub/OpenBSD (Lake in the Hills, IL)
ftp://osmirrors.cerias.purdue.edu/pub/OpenBSD (West Lafayette, IN)
ftp://ftp.cse.buffalo.edu/pub/OpenBSD (Buffalo, NY)
ftp://ftp.crimelabs.net/pub/OpenBSD (New York, NY)
ftp://ftp.nyc.openbsd.org/pub/OpenBSD (New York, NY)
ftp://mirrors.24-7-solutions.net/pub/OpenBSD (New York, NY)
ftp://openbsd.mirrors.pair.com (Pittsburgh, PA)
ftp://ftp.ptptech.com/pub/OpenBSD (Ashburn, VA)
ftp://openbsd.secsup.org/pub/openbsd (Fairfax, VA)
ftp://ftp.tux.org/bsd/openbsd (Springfield, VA)
ftp://openbsd.mirrors.tds.net/pub/OpenBSD (Madison, WI)
Additionally, the file ftp://ftp.OpenBSD.org/pub/OpenBSD/ftplist
contains a list which is continually updated. If you wish to become a
distribution site for OpenBSD, contact <www@OpenBSD.org>.
OpenBSD 3.9 Release Contents:
-----------------------------
The OpenBSD 3.9 release is organized in the following way. In the
.../3.9 directory, for each of the architectures having an OpenBSD 3.9
binary distribution, there is a sub-directory.
The macppc-specific portion of the OpenBSD 3.9 release is found in the
"macppc" subdirectory of the distribution. That subdirectory is laid
out as follows:
.../3.9/macppc/
INSTALL.macppc Installation notes; this file.
CKSUM, MD5 Output of the cksum(1) and md5(1) programs,
usable for verification of the correctness of
downloaded files.
*.tgz macppc binary distribution sets; see below.
bsd A stock GENERIC macppc 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.
cd39.iso A miniroot filesystem image suitable to be used
as a bootable CD-ROM image; otherwise similar to
the bsd.rd image above.
The OpenBSD/macppc binary distribution sets contain the binaries which
comprise the OpenBSD 3.9 release for macppc systems. There are eleven
binary distribution sets. The binary distribution sets can be found in
the "macppc" subdirectory of the OpenBSD 3.9 distribution tree,
and are as follows:
base39 The OpenBSD/macppc 3.9 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.
[ 49.4 MB gzipped, 146.2 MB uncompressed ]
comp39 The OpenBSD/macppc Compiler tools. All of the tools
relating to C, C++, and fortran are supported. This set
includes the system include files (/usr/include), the
linker, the compiler tool chain, and the various system
libraries (except the shared libraries, which are
included as part of the base set).
This set also includes the manual pages for all
of the utilities it contains, as well as the system
call and library manual pages.
[ 89.0 MB gzipped, 233.8 MB uncompressed ]
etc39 This distribution set contains the system configuration
files that reside in /etc and in several other places.
This set MUST be installed if you are installing the
system from scratch, but should NOT be used if you are
upgrading. (If you are upgrading, it's recommended that
you get a copy of this set and CAREFULLY upgrade your
configuration files by hand; see the section named "Upgrading
a previously-installed OpenBSD System" below.)
[ 1.1 MB gzipped, 3.6 MB uncompressed ]
game39 This set includes the games and their manual pages.
[ 2.6 MB gzipped, 5.9 MB uncompressed ]
man39 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.
[ 7.0 MB gzipped, 25.4 MB uncompressed ]
misc39 This set includes the system dictionaries (which are
rather large), and the typesettable document set.
[ 2.1 MB gzipped, 7.1 MB uncompressed ]
xbase39 This set includes the base X distribution. This includes
programs, headers and libraries.
[ 11.4 MB gzipped, 32.4 MB uncompressed ]
xetc39 This set includes the X window system configuration files
that reside in /etc. It's the equivalent of etc39 for X.
[ 92.9 KB gzipped, 356.4 KB uncompressed ]
xfont39 This set includes all of the X fonts.
[ 31.6 MB gzipped, 35.8 MB uncompressed ]
xserv39 This set includes all of the X servers.
[ 11.1 MB gzipped, 31.1 MB uncompressed ]
xshare39 This set includes all text files equivalent between
all architectures.
[ 1.9 MB gzipped, 10.4 MB uncompressed ]
OpenBSD System Requirements and Supported Devices:
--------------------------------------------------
OpenBSD/macppc 3.9 runs on iMac, G4 Power Macintosh, and G4 Cube, as well
as PowerBook and iBook machines.
Machines with older firmware: 6xxx, 7xxx, 8xxx, and 9xxx machines are
not supported. PowerMac G3 Beige status is unknown.
OpenBSD/macppc has been tested on iMac Revs A-C as well as on iMac DV(+)
machines, Power Macintosh G4 systems (single and dual processor), as well as
the G4 Cube, B&W G3, LCD iMac, Mac mini, iMac G5, PowerMac G5 and Xserve G5.
For portables, PowerBook G3, PowerBook G4 (12", 15", 17"), iBook, iBook2
and iBook G4 have been tested. Note that power saving features on portables
are very limited, limited power management features are available, suspend/sleep
is not supported. However battery level and status charging/AC
connected/AC disconnected is supported via an APM emulation layer.
Supported devices include:
IDE hard disk controllers
Onboard controllers (wdc_obio)
Onboard ATA100 controllers (kauaiata)
PCI controllers (pciide)
SCSI host adapters
Adaptec AIC-7770, AIC-7850, AIC-7860, AIC-7870, AIC-7880,
AIC-7890, AIC-7891, AIC-7892, AIC-7895, AIC-7896, AIC-7897
and AIC-7899 based host adapters (ahc), including the
Adaptec cards
AHA-274X[W,T]
AHA-284X
AHA-2910, AHA-2915
AHA-2920
AHA-2930[C,U2]
AHA-2940[J,N,U,AU,UW,UW Dual,UW Pro,U2W,U2B]
AHA-2950[U2W,U2B]
AHA-3940[U,AU,UW,AUW,U2W]
AHA-3950U2
AHA-3960
AHA-3985
AHA-4944UW
AHA-19160B
AHA-29160[B,N]
AHA-39160
Symbios Logic (NCR) 53C8xx-based PCI SCSI host adapters
(53c810 and 53c825) (siop)
AMD Am53c974 PCscsi-PCI host adapters including the Tekram
DC-390 (pcscp)
QLogic PCI SCSI controllers (isp)
RAID controllers
Adaptec SCSI RAID (I2O) controllers (ASR-2100S, ASR-3200S,
etc) (iop)
AGP/SVGA/VGA Display Adapters
Primary Open Firmware display only
The following cards will run an accelerated X server:
- ATI Mach64 GP
- ATI Mach64 GV
- ATI Mach64 128 PK
- ATI Mach64 128 VR AGP
- ATI Rage 128 Mobility M3
- ATI Rage Fury AGP4x
- ATI Radeon Mobility M7
- ATI Radeon Mobility 9200 (M9+)
- NVIDIA GeForce4 440 Go 64M
Serial ports
Built-in Zilog 8530-based serial ports (zs)
Internal non-USB modems.
Ethernet adapters
Onboard Older iMac 10-100Mbs (bm) Ethernet
Onboard G4/PowerBook/Newer iMac (gem) Ethernet
3Com 3c9xx EtherLink XL adapters (xl), including:
3Com 3c900/3c900B PCI adapters
3Com 3c905/3c905B/3c905C PCI adapters
3Com 3c980/3c980C server adapters
3Com 3cSOHO adapter
3Com 3c900B-FL and 3c900B-FL/FX fiber optic adapters
3Com 3c555/3c556/3c556B MiniPCI adapters
ADMtek AN986-based USB adapters (aue), including:
3Com 3c460b
Abocom UFE1000
Abocom DSB650TX
Accton USB320-EC
Accton SpeedStream Ethernet
Admtek Pegasus
Admtek Pegasus II
AEI USB Fast Ethernet
Allied Telesyn AT-USB100
ATEN UC-110T
Belkin USB to LAN
Billionton Systems USB100
Billionton Systems USB100EL
Billionton Systems USB100LP
Billionton Systems USBE100
Corega FEther USB-TX
Corega FEther USB-TXS
D-Link DSB-650
D-Link DSB-650TX
D-Link DSB-650TX-PNA
ELCON Systemtechnik Goldpfeil P-LAN
Elecom LD-USB/TX
Elecom LD-USBL/TX
Elsa Microlink USB2Ethernet
GIGABYTE GN-BR402W
Hawking UF100
HP HN210E
I/O DATA USB ETTX
Kingston KNU101TX
Laneed LD-USBL/TX
Linksys USB100TX
Linksys USB100H1
Linksys USB10T
Linksys USB10TA
Linksys USB10TX
Melco Inc. LUA-TX
Melco Inc. LUA2-TX
Microsoft MN110
Mobility EasiDock Ethernet
Netgear FA101
Omnidirectional Control Technology USB TO Ethernet
Siemens SpeedStream USB
Smartbridges smartNIC 2
SMC 2202USB/ETH
SMC 2206USB/ETH
SOHOware NUB100
SOHOware NUB110
Alteon Tigon I/II PCI Gigabit Ethernet boards (ti), including:
3Com 3c985 and 3c985B
Alteon ACEnic V (fiber and copper)
Digital EtherWORKS 1000SX
Farallon PN9000SX
Netgear GA620 and GA620T
SGI Tigon
ASIX Electronics AX88172 USB Ethernet adapters (axe), 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)
JVC MP-PRX1
Linksys USB200M
Netgear FA120
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
Broadcom BCM570x (Tigon3) based PCI adapters (bge), including:
3Com 3c996-T
3Com 3c996-SX
3Com 3c996B-T
Netgear GA302T
SysKonnect SK-9D21
SysKonnect SK-9D41
CATC USB-EL1210A-based USB adapters (cue), including:
Belkin F5U111
CATC Netmate
CATC Netmate II
SmartBridges SmartLink
Davicom DM9601 USB Ethernet adapters (udav), including:
Corega FEther USB-TXC
Digital DC21x4x-based PCI Ethernet adapters (de), including:
Znyx ZX34X
Digital DC21x43 clone-based PCI Ethernet adapters (dc)
HME PCI Fast Ethernet (hme)
HME PCI Quad Fast Ethernet (hme)
Intel 21145-based PCI Ethernet adapters (dc)
Intel i8255x-based (except the i82556) PCI adapters (fxp),
including:
Intel EtherExpress PRO/10+
Intel EtherExpress PRO/100, PRO/100B, and PRO/100+
Intel EtherExpress PRO/100+ "Management Adapter"
Intel EtherExpress PRO/100 Dual Port
Intel PRO/100 VE, PRO/100 VM, and PRO/100 S
Intel i82540, i82541, i82542, i82543, i82544, i82545, i82546
and i82547 based adapters (em), including:
Intel PRO/1000 Gigabit Server Adapter (SX Fiber)
(PWLA8490)
Intel PRO/1000F Gigabit Server Adapter (SX Fiber)
(PWLA8490SX)
Intel PRO/1000T Server Adapter (PWLA8490T)
Intel PRO/1000XT Server Adapter (PWLA8490XT)
Intel PRO/1000XS Server Adapter (SX Fiber) (PWLA8490XF)
Intel PRO/1000T Desktop Adapter (PWLA8390T)
Intel PRO/1000XTL Lo Profile PCI Server (PWLA8490XTL)
Intel PRO/1000MT Desktop Adapter (PWLA8390MT)
Intel PRO/1000MT Server Adapter (PWLA8490MT)
Intel PRO/1000MT Dual Port Server Adapter (PWLA8492MT)
Intel PRO/1000MF Server Adapter (SX Fiber) (PWLA8490MF)
Intel PRO/1000MF Dual Port Server Adapter (SX Fiber)
(PWLA8492MF)
Intel PRO/1000MF Server Adapter (LX Fiber) (PWLA8490LX)
Intel PRO/1000MT Quad PCI-X Adapter (PWLA8494MT)
Kawasaki LSI KL5KUSB101B-based USB adapters (kue), including:
3Com 3c19250
3Com 3c460 HomeConnect
AboCom Systems URE450 Ethernet
ADS Technologies USB-10BT
Aox USB101
Asante USB to Ethernet
ATen DSB-650C
ATen UC10T
Corega USB-T
D-Link DSB-650C
Entrega 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 2102USB
SMC 2104USB
Realtek RTL8150L based USB adapters (url), 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
RealTek 8129/8139-based adapters (rl), including:
Accton MPX 5030/5038
Allied Telesyn AT2550
D-Link DFE530TX+
D-Link DFE538TX
Encore ENL832-TX 10/100 M PCI
Genius GF100TXR
KTX-9130TX 10/100 Fast Ethernet
Longshine LCS-8038TX-R
NDC NE100TX-E
Netronix EA-1210 Net Ether 10/100
Nortel BayStack 21
OvisLink LEF-8129TX, LEF-8139TX
SMC EZ Card 10/100 PCI 1211-TX
Realtek 8169/8169S/8110S based PCI adapters, including:
Buffalo LGY-PCI-GT (8169S)
Corega CG-LAPCIGT (8169S)
D-Link DGE-528T (8169S)
Gigabyte 7N400 Pro2 Integrated Gigabit Ethernet (8110S)
LevelOne GNC-0105T (8169S)
Linksys EG1032v3 (8169S)
Netgear GA511 PC Card (8169)
PLANEX COMMUNICATIONS Inc. GN-1200TC (8169S)
Surecom EP-320G-TX1 (8169S)
US Robotics USR997902 (8169S)
Xterasys XN-152 10/100/1000 NIC (8169)
VIA Networking VT6122 based PCI adapters, including:
ZyXEL GN650-T 64-bit PCI Gigabit Ethernet NIC (ZX1701)
ZyXEL GN670-T 32-bit PCI Gigabit Ethernet NIC (ZX1702)
VIA Rhine/RhineII/RhineIII Ethernet adapters, including:
Addtron AEF-360TX
Hawking PN102TX
D-Link DFE530TX
Wireless Ethernet Adapters
PCMCIA Adapters
Aironet IEEE 802.11FH/b PCMCIA and PCI (an)
WaveLAN IEEE 802.11b PCMCIA (wi)
Atmel AT76C50x based USB IEEE 802.11b adapters
3Com 3CRSHEW696
AboCom BWU613
Accton 2664W
Acer Peripherals AWL300
Acer Peripherals AWL400
Actiontec 802UAT1
Addtron AWU120
Aincomm AWU2000B
Askey Computer Voyager 1010
Askey Computer WLL013 (Intersil Radio)
Askey Computer WLL013 (RFMD Radio)
Belkin F5D6050
Bluetake BW002
Compaq iPAQ h54xx/h55xx Internal WLAN
Conceptronic C11U
Conceptronic WL210
Corega WLAN USB Stick 11
Dick Smith Electronics CHUSB 611G
Dick Smith Electronics WL200U
Dick Smith Electronics WL240U
Dick Smith Electronics XH1153
D-Link DWL-120 rev E
Geowave GW-US11S
Gigabyte GN-WLBM101
Gigaset WLAN
Hewlett-Packard HN210W
Intel AP310 AnyPoint II
I/O DATA USB WN-B11
Lexar 2662W-AR
Linksys WUSB11
Linksys WUSB11 v2.8
MSI WLAN
Netgear MA101
Netgear MA101 rev B
Ovislink AirLive WL-1120USB
OvisLink AirLive WL-1130USB
Planex Communications GW-US11S
Samsung SWL2100W
Siemens WLL013
SMC 2662W-AR
SMC 2662W-V4
Tekram U-300C
Z-Com M4Y-750
Intersil PRISM 2.5/3 based USB IEEE 802.11b adapters
Acer Warplink USB-400
Actiontec HWU01170
AirVast WM168b
Ambit WLAN
Apacer Wireless Steno MB112
ASUS WL-140
Compaq W100
Corega WLUSB-11
Corega WLUSB-11 Key
D-Link DWL-120 (rev F)
D-Link DWL-122
I-O DATA WN-B11/USB
Intel PRO/Wireless 2011B
Intersil Prism 2X
JVC MP-XP7250
Linksys WUSB11 v3.0
Linksys WUSB12
Melco WLI-USB-KB11
Melco WLI-USB-KS11G
Melco WLI-USB-S11
Microsoft MN510
Netgear MA111 (version 1)
Pheenet WL-503IA
Planex GW-US11H
Siemens SpeedStream SS1022
Sitecom WL-022
Syntax USB-400
US Robotics 1120
ViewSonic Airsync
Z-Com XI-725/726
Z-Com XI-735
ZyXEL ZyAIR B-200
Ralink RT2500 based USB 2.0 IEEE 802.11b/g adapters
AMIT WL532U
ASUS WL-167g
Belkin F5D7050
Buffalo WLI-U2-KG54
Buffalo WLI-U2-KG54-AI
Buffalo WLI-U2-KG54-YB
CNet CWD-854
Compex WLU54G
Conceptronic C54RU
D-Link DWL-G122 (b1)
Dynalink WLG25USB
E-Tech WGUS02
Eminent 3035
Gigabyte GN-WBKG
Hercules HWGUSB2-54
KCORP LifeStyle KLS-685
Linksys WUSB54G v4
Linksys WUSB54GP v4
MSI MS-6861
MSI MS-6865
MSI MS-6869
SerComm UB801R
SparkLAN WL-685R
Sphairon UB801R
Surecom EP-9001-g
Tonze UW-6200C
Zaapa ZNWUSB-54
Zinwell ZWX-G261
Zonet ZEW2500P
Realtek RTL8180L based CardBus IEEE 802.11b adapters
Belkin F5D6020 V3
Buffalo WLI-CB-B11
Corega CG-WLCB11V3
D-Link DWL-610
Level-One WPC-0101
Linksys WPC11 v4
Netgear MA521
Ovislink AirLive WL-1120PCM
Planet WL-3553
TRENDnet TEW-226PC
VCTnet PC-11B1
Tape drives
SCSI Tape drives (st)
CD-ROM drives (cd)
SCSI CD-ROM drives
SCSI CD-RW drives
Atapi CD-ROM drives
Atapi DVD-ROM drives
Atapi DVD-RAM drives (read-only)
Atapi DVD-RW drives (read-only?)
Atapi CD-RW drives
Keyboards
ADB (akbd) and USB (ukbd) keyboards
Mice
USB Mice (ums)
ADB trackpads (ams)
Sound Cards
AWACS audio (awacs)
Ensoniq AudioPCI (eap)
Snapper audio found on recent iBook (since May02) and
PowerBook (since Apr02) models (need to verify
iMac (Jan 02) and Power Mac G4 (Sep 02)) (snapper)
USB audio (uaudio)
Radio Receiver Devices
Brooktree 848/849/878/879-based TV tuner (bktr)
Miscellaneous
USB Hubs
USB printers (ulpt)
USB Zip drives (umass)
Brooktree 8[47][89] based frame grabber and TV tuner cards,
including (bktr):
Animation Technologies FlyVideo
AOpen VA1000
Askey/Dynalink Magic TView
ATI TV-Wonder and Wonder/VE
AverMedia cards
Hauppauge Wincast TV and WinTV/PCI
IMS TV Turbo
Intel Smart Video Recorder III
I/O DATA GV-BCTV2/PCI
I/O DATA GV-BCTV3/PCI
KISS TV/FM PCI
Leadtek Winfast TV 2000
Miro PC TV
MMAC Osprey
NEC PK-UG-X017
STB TV PCI Television Tuner
Terratec TerraTVplus
Video Highway XTreme
VideoLogic Captivator PCI
Zoltrix TV and Genie TV/FM
Cryptography Accelerators
Hifn 6500 (lofn)
Hifn 7751/7811/7951/7955/7956/9751 (hifn)
Bluesteelnet 5501/5601 (ubsec)
Broadcom 5801/5802/5805/5820/5821/5822/5823 (ubsec)
SafeNet SafeXcel 1141/1741 (safe)
The following devices are not supported currently:
- built-in Texas Instrument TSB12LV23 firewire (IEEE1394) ports
- built-in USB modems
- built-in CardBus slots non-TI PCI1211
Getting the OpenBSD System onto Useful Media:
---------------------------------------------
Installation is supported from several media types, including:
CD-ROM
FFS partitions (for upgrades only)
HFS partitions (bootloader/kernel only, using another media for d/l)
Tape
FTP
HTTP
The steps necessary to prepare the distribution sets for installation
depend on which method of installation you choose. Some methods
require a bit of setup first that is explained below.
The installation allows installing OpenBSD directly from FTP mirror
sites over the internet, however you must consider the speed and
reliability of your internet connection for this option. It may save
much time and frustration to use ftp get/reget to transfer the
distribution sets to a local server or disk and perform the installation
from there, rather than directly from the internet.
OpenBSD can now be booted from a CD-ROM by holding down the 'c' key
during reboot. If ofwboot and bsd.rd are copied to an HFS partition, it
is possible to boot from those files. Then install the rest of the files
from any of the above sources.
Note: Once an OpenBSD partition exists, it is not possible to load the
kernel (bsd.rd) from an HFS partition on that disk.
Creating an installation tape:
While you won't be able to boot OpenBSD from a tape, you can use
one to provide the installation sets. To do so, you need to make
a tape that contains the distribution set files, each in "tar"
format or in "gzipped tar format". First you will need to
transfer the distribution sets to your local system, using ftp or
by mounting the CD-ROM containing the release. Then you need to
make a tape containing the files.
If you're making the tape on a UN*X-like system, the easiest way
to do so is make a shell script along the following lines, call it
"/tmp/maketape".
#! /bin/sh
TAPE=${TAPE:-/dev/nrst0}
mt -f ${TAPE} rewind
for file in base etc comp game man misc xbase xetc xfont xserv xshare
do
dd if=${file}39.tgz of=${TAPE} obs=8k conv=sync
done
tar cf ${TAPE} bsd
mt -f ${TAPE} offline
# end of script
And then:
cd .../3.9/macppc
sh -x /tmp/maketape
If you're using a system other than OpenBSD or SunOS, the tape
name and other requirements may change. You can override the
default device name (/dev/nrst0) with the TAPE environment
variable. For example, under Solaris, you would probably run:
TAPE=/dev/rmt/0n sh -x /tmp/maketape
Note that, when installing, the tape can be write-protected
(i.e. read-only).
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 "base39" set somewhere in your file system. It
is recommended that you upgrade the other sets, as well.
Preparing your System for OpenBSD Installation:
-----------------------------------------------
To be able to boot the OpenBSD/macppc installation program, you will
need to acquire some limited knowledge of Open Firmware, the low-level
process that controls the microprocessor after hardware initialization
and diagnostics are performed but before control is handed to the
operating system.
To access Open Firmware, you should simultaneously hold down the
Command, Option, O, and F keys immediately upon booting. You will
be presented with information and a ">" prompt that will look something
like this (example taken from a Power Macintosh G4):
Apple PowerMac3,1 2.4f1 BootROM built on 02/18/00 at 09:44:35
Copyright 1994-2000 Apple Computer, Inc.
All Rights Reserved
Welcome to Open Firmware
To continue booting, type "mac-boot" and press return
To shut down, type "shut-down" and press return
ok
0 >
If you are installing OpenBSD/macppc on an Xserve, you will need
to do so in headless mode. This means you must remove the graphics
card and use the serial console. To bring up Open Firmware via
the serial console, hold down the System Identifier button while
pressing the Power button. When the upper LED bank begins lighting
up in sequence (similar to KITT from Knight Rider), repeatedly
press the System Identifier button until the seventh LED from
the right is highlighted on the lower bank. Now hold the
System Identifier button for two seconds. For more details, read:
http://docs.info.apple.com/article.html?artnum=75489
Important Open Firmware command examples:
boot cd:,ofwboot /3.9/macppc/bsd.rd
(boot from an appropriately prepared
OpenBSD CD-ROM in the CD/DVD drive)
boot enet:,ofwboot /bsd.rd
(netboot from a pre-configured bootp/tftp/nfs
server containing the "ofwboot" and "bsd.rd"
files at the root directory of the tftp server)
boot ide1:,ofwboot /bsd
(After installation, boot /bsd from the slave
device on the second ATA bus)
mac-boot (boot into Mac OS)
reset-all (reboot the machine)
shut-down (halt the machine; shutdown)
printenv (print current machine variables)
setenv (set a machine variable)
devalias (list device aliases; useful for locating other
devices in the machine such as hard drives, etc)
As seen above, device aliases typically take the form of "ide", "cd",
etc. To boot to an alternative device, you may substitute them
with entries from this list (example devices taken from a Power
Macintosh G4):
ultra0 = hd = master device, primary ATA bus (factory-installed drive)
ultra1 = slave device, primary ATA bus
ide0 = cd = master device, secondary ATA bus (CD/DVD drive)
ide1 = slave device, secondary ATA bus (Zip drive, if installed)
enet = motherboard Ethernet device
Other Open Firmware command examples:
setenv auto-boot? false
(force the machine to wait at Open Firmware
for user input at next reboot; options are true/false)
setenv boot-device ide:,ofwboot
(force the machine to boot into OpenBSD
automatically at next reboot)
dev / (change to root level of the device tree)
pwd (show current location in the device tree)
ls (show items at current location in the device tree)
words (show methods of items at current location in the device
tree)
.properties (show properties of items at current location in the
device tree)
To reset a Power Macintosh to the factory-configured Open Firmware settings,
simultaneously hold down the Command, Option, P, and R keys immediately upon
booting. Typically the machine will then attempt to load Mac OS, if
available.
Autobooting OpenBSD/macppc
It is possible to automatically boot into OpenBSD (selectably into Mac OS)
by setting up the following:
setenv auto-boot? true
setenv boot-device hd:,ofwboot
[to save the results into NVRAM]
reset-all
These settings assume that the master of the first IDE bus has OpenBSD
installed on it, either in MBR format or in shared mode with ofwboot
copied into the first HFS(+) partition. It is not necessary to specify
'/bsd' on the boot line or in the boot-device variable, since it is the
default.
To boot in Mac OS with this setup (works on most supported machines),
press and hold down the Alt/Option key during reboot, and select which
(Mac OS/Mac OS X) partition to boot in the graphical boot selector
presented. Note that OpenBSD does not currently show up in this boot
selector except for the installation CD-ROM. This works on most machines
this has been tested with, but does not work on a Rev C (333MHz) iMac;
perhaps this feature was added to the Open Firmware ROM after that
machine.
Sharing a disk with Mac OS:
OpenBSD/macppc is capable of booting either from a dedicated disk using
an MBR partitioned disk or sharing a disk with Mac OS.
If the disk is to be shared between Mac OS and OpenBSD, it is necessary
to reformat and install the Mac OS partitions first, using "Drive Setup",
leaving space on the disk as an "Unused" partition.
If the disk was previously partitioned, it is possible to reuse a partition
for OpenBSD, as long as it is not the first partition on the disk.
The bootloader is expected to be found in that first (HFS) partition.
For dedicated disks, macppc port boots off a boot program in
an MSDOS filesystem. This is set up by the install program
and no special setup is required.
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 decide if OpenBSD is to be installed
on the whole disk or share the disk with Mac OS.
For stand-alone (No Mac OS installed) or dedicated disks, the MBR
installation method should be chosen and no additional prep is necessary.
If the disk is to be shared with Mac OS, a partition must be preallocated
by the Mac OS partition editor and Mac OS installed to the proper partition.
This expects that the HFS partition will be the first partition on
the disk, and then the OpenBSD partition will follow.
This may require the disk be reformatted using the "Drive Setup" application
and reinstalled under Mac OS.
You should now be ready to install OpenBSD.
The following is a walk-through of the steps you will take while
getting OpenBSD installed on your hard disk. If any question has a
default answer, it will be displayed in brackets ("[]") after the
question. If you wish to stop the installation, you may hit Control-C
at any time, but if you do, you'll have to begin the installation
process again from scratch. Using Control-Z to suspend the process
may be a better option, or at any prompt enter '!' to get a shell,
from which 'exit' will return you back to that prompt (no refresh
of the prompt though).
At this time, the system can be installed from the supplied
CD-ROM boot image, by network loading the bootloader, or loading
the bootloader and kernel from an HFS partition.
Once the bootloader is installed on the local hard drive, the
system can boot from it. OpenBSD may share a drive with Mac OS
if the process is followed carefully. Currently it is
necessary to use Open Firmware commands to dual boot between
OS's, or multiple drives may be used with each OS owning drive(s).
It is also possible on some newer models to set up the system
to auto boot OpenBSD and if Mac OS is desired, choose it using
the firmware boot selector by holding down the <option> key
during reboot and selecting the Mac OS Disk icon.
(Refer to "Preparing your System for OpenBSD Installation" above
for information on how to access and boot from Open Firmware.)
Once the kernel has loaded, you will 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 partitions. You will also need to know the device
name to tell the install tools what disk to install on. If
you cannot read the messages as they scroll by, do not
worry -- you can get at this information later inside the
install program.
You will next be asked for your terminal type. You should just
hit return to select the default (vt220).
After entering the terminal type you will be asked whether you
wish to do an "(I)nstall" or an "(U)pgrade". Enter 'I' for a
fresh install or 'U' to upgrade an existing installation.
You will be presented with a welcome message and asked if
you really wish to install (or upgrade). Assuming you
answered yes, the install program will then tell you which
disks of that type it can install on, and ask you which it
should use. The name of the disk is typically "sd0" for
SCSI drives.
Reply with the name of your disk.
Next you will have to edit or create a disk label for the disk
OpenBSD is being installed on. If there are any existing
partitions defined (for any operating system), and a disk label
is not found, you will first be given an opportunity to run
fdisk (MBR partitioned disk) or pdisk (HFS partitioned disk)
and create an OpenBSD partition.
If pdisk is being invoked, you will be issued a command prompt
allowing you to modify the partition table. The most common
operation, and the example presented here, deals with the
conversion of an existing partition into one usable by OpenBSD.
Before editing, the partition table may look like the following:
#: type name length base ( size )
1: Apple_partition_map Apple 63 @ 1
2: Apple_Driver43*Macintosh 54 @ 64
3: Apple_Driver43*Macintosh 74 @ 118
4: Apple_Driver_ATA*Macintosh 54 @ 192
5: Apple_Driver_ATA*Macintosh 74 @ 246
6: Apple_FWDriver Macintosh 200 @ 320
7: Apple_Driver_IOKit Macintosh 512 @ 520
8: Apple_Patches Patch Partition 512 @ 1032
9: Apple_HFS untitled 2142310 @ 1544 ( 1.0G)
10: Apple_HFS untitled 2 4120589 @ 2143854 ( 2.0G)
11: Unused untitled 3 6330517 @ 6264443 ( 3.0G)
After editing the table, it should look like:
#: type name length base ( size )
1: Apple_partition_map Apple 63 @ 1
2: Apple_Driver43*Macintosh 54 @ 64
3: Apple_Driver43*Macintosh 74 @ 118
4: Apple_Driver_ATA*Macintosh 54 @ 192
5: Apple_Driver_ATA*Macintosh 74 @ 246
6: Apple_FWDriver Macintosh 200 @ 320
7: Apple_Driver_IOKit Macintosh 512 @ 520
8: Apple_Patches Patch Partition 512 @ 1032
9: Apple_HFS untitled 2142310 @ 1544 ( 1.0G)
10: Apple_HFS untitled 2 4120589 @ 2143854 ( 2.0G)
11: OpenBSD OpenBSD 6330517 @ 6264443 ( 3.0G)
This will likely be different based on the number of partitions
created on the disk by the Apple partition editor.
It is _VERY_ important to not change the start, sizes, or types of
partitions other than the ones that are to be used by OpenBSD,
including the Apple_Driver.* and Apple_partition_map.
---
Command (? for help): p
<output is in the before example above>
Command (? for help): t
Partition number: 11
Existing partition type ``Unused''.
New type of partition: OpenBSD
Command (? for help): p
<output is in the after example above>
---
If fdisk is being invoked, it will start by
displaying the current partitions defined and then allow you
to modify this information, add new partitions, and change
which partition to boot from by default. If you make a mistake,
you will be allowed to repeat this procedure as necessary to
correct this. Note that you should make OpenBSD be the active
partition at least until the install has been completed.
Next the disk label which defines the layout of the OpenBSD
file systems must be set up. The installation script will
invoke an interactive editor allowing you to do this. Note
that partition 'c' inside this disk label should ALWAYS
reflect the entire disk, including any non-OpenBSD portions.
If you are labeling a new disk, you will probably start
out with an 'a' partition that spans the disk. In this
case you should delete 'a' before adding new partitions.
The root file system should be in partition 'a', and swap
is usually in partition 'b'. If you have DOS or Linux
partitions defined on the disk, these will usually show up as
partition 'h', 'i' and so on.
OpenBSD/macppc can share a disk with Mac OS or Mac OS X by using
an HFS partitioned disk. For proper layout, the disk should be
partitioned with Mac OS or Mac OS X first with unused space or a
spare partition where OpenBSD can be installed. No low disk
boundaries exist on macppc. macppc is unable to install the
bootloader into the HFS(+) partition to boot OpenBSD so it is
necessary to copy 'ofwboot' from the installation media into
the first HFS(+) partition using Mac OS or Mac OS X.
If the disk is partitioned using MBR, the bootloader is
automatically installed. However because fdisk is not LBA
knowledgeable it may be necessary to run the 'b' command in
disklabel to allow OpenBSD to use the entire disk.
Note that all OpenBSD partitions in the disk label must have an
offset that makes it start within the OpenBSD part of the disk,
and a size that keeps it inside of that portion of the disk. This
is within the bounds of the 'c' partition.
It is recommended that you create separate partitions for /usr,
/tmp, and /var, and if you have room for it, one for /home. In
doing this, remember to skip 'c', leaving it as type "unused".
For help in the disk label editor, enter '?' or 'M' to view the
manual page (see the info on the ``-E'' flag).
The swap partition (usually 'b') should have a type of "swap", all
other native OpenBSD partitions should have a type of "4.2BSD".
Block and fragment sizes are usually 8192 and 1024 bytes, but can
also be 4096 and 512 or even 16384 and 2048 bytes.
The install program will now label your disk and ask which file
systems should be created on which partitions. It will auto-
matically select the 'a' partition to be the root file system.
Next it will ask for which disk and partition you want a file
system created on. This will be the same as the disk name (e.g.
"wd0") with the letter identifying the partition (e.g. "d")
appended (e.g. "wd0d"). Then it will ask where this partition is
to be mounted, e.g. /usr. This process will be repeated until
you enter "done".
At this point you will be asked to confirm that the file system
information you have entered is correct, and given an opportunity
to change the file system table. Next it will create the new file
systems as specified, OVERWRITING ANY EXISTING DATA. This is the
point of no return.
After all your file systems have been created, the install program
will give you an opportunity to configure the network. The network
configuration you enter (if any) can then be used to do the install
from another system using HTTP or FTP, and will also be the
configuration used by the system after the installation is complete.
If you select to configure the network, the install program will
ask you for the name of your system and the DNS domain name to use.
Note that the host name should be without the domain part, and that
the domain name should NOT include the host name part.
Next the system will give you a list of network interfaces you can
configure. For each network interface you select to configure, it
will ask for the IP address to use, the symbolic host name to use,
the netmask to use, and any interface-specific flags to set. The
interface-specific flags are usually used to determine which media
the network card is to use. Typically no media flags are required
as autodetection normally works, but you will be prompted with a
list of the acceptable media flags, and asked if you want to provide
any. In doubt, do not enter any media flags; or you can refer to
the manual page for your interface for the appropriate flags.
After all network interfaces have been configured, the install pro-
gram will ask for a default route and IP address of the primary
name server to use. You will also be presented with an opportunity
to edit the host table.
At this point you will be allowed to edit the file system table
that will be used for the remainder of the installation and that
will be used by the finished system, following which the new file
systems will be mounted to complete the installation.
After these preparatory steps have been completed, you will be
able to extract the distribution sets onto your system. There
are several install methods supported; FTP, HTTP, tape,
CD-ROM, or a local disk partition.
To install via FTP:
To begin an FTP install you will need the following
pieces of information. Don't be daunted by this list;
the defaults are sufficient for most people.
1) Proxy server URL if you are using a URL-based
FTP proxy (squid, CERN FTP, Apache 1.2 or higher).
You need to define a proxy if you are behind a
firewall that blocks outgoing FTP (assuming you
have a proxy available to use).
2) Do you need to use active mode FTP? By default,
ftp will attempt to use passive mode and fall
back to an active connection if the server does
not support passive mode. You only need to enable
this option if you are connecting to a buggy FTP
daemon that implements passive FTP incorrectly.
Note that you will not be asked about active
FTP if you are using a proxy.
3) The IP address (or hostname if you enabled
DNS earlier in the install) of an FTP server
carrying the OpenBSD 3.9 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/3.9/macppc
is almost always correct.
5) The login and password for the FTP account.
You will only be asked for a password for
non-anonymous FTP.
For instructions on how to complete the installation via
FTP, see the section named "Common URL installations" below.
To install via HTTP:
To begin an HTTP install you will need the following
pieces of information:
1) Proxy server URL if you are using a URL-based
HTTP proxy (squid, CERN FTP, Apache 1.2 or higher).
You need to define a proxy if you are behind a
firewall that blocks outgoing HTTP connections
(assuming you have a proxy available to use).
2) The IP address (or hostname if you enabled
DNS earlier in the install) of an HTTP server
carrying the OpenBSD 3.9 distribution.
If you don't know, just hit return when
asked if you want to see a list of such hosts.
3) The directory holding the distribution sets.
There is no standard location for this;
You should use the directory specified
along with the server in the list of official
HTTP mirror sites that you received in step 3.
For instructions on how to complete the installation via
HTTP, see the section named "Common URL installations" below.
To install from tape:
In order to install from tape, the distribution sets to be
installed must have been written to tape previously, either
in tar format or gzip-compressed tar format.
You will also have to identify the tape device where the
distribution sets are to be extracted from. This will
typically be "nrst0" (no-rewind, raw interface).
Next you will have to specify how many files have to be
skipped on the tape. This number is usually zero.
The install program will not automatically detect whether
an image has been compressed, so it will ask for that
information before starting the extraction.
To install from CD-ROM:
When installing from a CD-ROM, you will be asked which
device holds the distribution sets. This will typically
be "cd0". Next you will be asked which partition on the
CD-ROM the distribution is to be loaded from. This is
normally partition "a".
Next you will have to identify the file system type that
has been used to create the distribution on the CD-ROM,
this can be either FFS or ISO CD9660. The OpenBSD CD-ROM
distribution uses the CD9660 format.
You will also have to provide the relative path to the
directory on the CD-ROM which holds the distribution, for
the macppc this is "3.9/macppc".
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 "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 have been formatted as the
Berkeley 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
a local disk partition, see the next section.
Common file system installations:
The following instructions are common to installations
from mounted disk partitions and CD-ROMs.
A list of available distribution sets will be listed.
You may individually select distribution sets to install
or enter `all' to install all of the sets (which is what
most users will want to do). You may also enter `list'
to get a file list or `done' when you are done selecting
distribution sets. You may also use wildcards in place of
a file name, e.g. `*.tgz' or even `base*|comp*'. It is
also possible to enter an arbitrary filename and have it
treated as a file set.
Once you have selected the file sets you want to install
and entered `done' you will be prompted to verify that
you really do want to extract file sets. Assuming you
acquiesce, the files will begin to extract. If not, you
will be given the option of installing sets via one of
the other install methods.
Common URL installations:
Once you have entered the required information, the
install program will fetch a file list and present
a list of all the distribution sets that were found
in the specified directory. (If no valid sets were found,
you will be notified and given the option of unpacking
any gzipped tar files found or getting a file list if
none were found.)
At this point you may individually select distribution
sets to install or enter `all' to install all of the
sets (which is what most users will want to do). You
may also enter `list' to get a file list or `done' when
you are done selecting distribution sets. You may also
use wildcards in place of a file name, e.g. `*.tgz' or
even `base*|comp*'. It is also possible to enter an
arbitrary filename and have it treated as a file set.
Once you have selected the file sets you want to install
and entered `done' you will be prompted to verify that
you really do want to download and install the files.
Assuming you acquiesce, the files will begin to download
and unpack. If not, you will be given the option of
installing sets via one of the other install methods.
When all the selected distribution sets has been extracted, you
will be allowed to select which time zone your system will be
using, all the device nodes needed by the installed system will
be created for you, and the file systems will be unmounted. For
this to work properly, it is expected that you have installed
at least the "base39", "etc39", and "bsd" distribution sets.
Congratulations, you have successfully installed OpenBSD 3.9. 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 3.9 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 3.9 are currently only supported from the
immediately previous release. The upgrade process will also work with older
releases, but might not execute some migration tasks that would be necessary
for a proper upgrade. The best solution, whenever possible, is to backup
your data and reinstall from scratch.
To upgrade OpenBSD 3.9 from a previous version, start with the general
instructions in the section "Installing OpenBSD".
Boot from the CD-ROM.
When prompted, select the (U)pgrade option rather than the (I)nstall
option at the prompt in the install process.
The upgrade script will ask you for the existing root partition, and
will use the existing filesystems defined in /etc/fstab to install the
new system in. It will also use your existing network parameters.
From then, the upgrade procedure is very close to the installation
procedure described earlier in this document. Note that the upgrade
procedure will not let you pick the ``etc39.tgz'' set, so as to
preserve your files in `/etc' which you are likely to have customized
since a previous installation.
However, it is strongly advised that you unpack the etc39.tgz set in
a temporary directory and merge changes by hand, since all components of
your system may not function correctly until your files in `/etc' are
updated.
Getting source code for your OpenBSD System:
--------------------------------------------
Now that your OpenBSD system is up and running, you probably want to get
access to source code so that you can recompile pieces of the system.
A few methods are provided. If you have an OpenBSD CD-ROM, the source
code is provided. Otherwise, you can get the pieces over the Internet
using anonymous CVS, CTM, CVSync or FTP. For more information, see
http://www.OpenBSD.org/anoncvs.html
http://www.OpenBSD.org/ctm.html
http://www.OpenBSD.org/cvsync.html
http://www.OpenBSD.org/ftp.html
Using online OpenBSD documentation:
-----------------------------------
Documentation is available if you first install the manual pages
distribution set. Traditionally, the UN*X "man pages" (documentation)
are denoted by 'name(section)'. Some examples of this are
intro(1),
man(1),
apropos(1),
passwd(1),
passwd(5) and
afterboot(8).
The section numbers group the topics into several categories, but three
are of primary interest: user commands are in section 1, file formats
are in section 5, and administrative information is in section 8.
The 'man' command is used to view the documentation on a topic, and is
started by entering 'man [section] topic'. The brackets [] around the
section should not be entered, but rather indicate that the section is
optional. If you don't ask for a particular section, the topic with the
least-numbered section name will be displayed. For instance, after
logging in, enter
man passwd
to read the documentation for passwd(1). To view the documentation for
passwd(5), enter
man 5 passwd
instead.
If you are unsure of what man page you are looking for, enter
apropos subject-word
where "subject-word" is your topic of interest; a list of possibly
related man pages will be displayed.
Adding third party software; ``packages'' and ``ports'':
--------------------------------------------------------
As complete as your OpenBSD system is, you may want to add any of several
excellent third party software applications. There are several ways to do
this. You can:
1) Obtain the source code and build the application based
upon whatever installation procedures are provided with the
application.
2) Use the OpenBSD ``ports'' collection to automatically get any
needed source file, apply any required patches, create the
application, and install it for you.
3) Use the OpenBSD ``package'' collection to grab a pre-compiled
and tested version of the application for your hardware.
If you purchased the OpenBSD CD-ROM set you already have several popular
``packages'', and the ``ports'' collection.
Instructions for installing applications from the various sources using
the different installation methods follow.
You should also refer to the packages(7) manual page.
Installing applications from the CD-ROM package collection:
The OpenBSD CD-ROM ships with several applications pre-built
for various hardware architectures. The number of applications
vary according to available disk space. Check the directory
3.9/packages/powerpc 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/3.9/packages/powerpc/<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/3.9/packages/powerpc/
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/3.9/packages/powerpc/emacs-21.3.tgz
Installing applications from the CD-ROM ports collection:
The CD-ROM ``ports'' collection is a set of Makefiles, patches,
and other files used to control the building and installation
of an application from source files.
Creating an application from sources can require a lot of
disk space, sometimes 50 megabytes or more. The first step is
to determine which of your disks has enough room. Once you've
made this determination, read the file PORTS located on the
CD-ROM which contains the ports tree.
To build an application you must:
1) become the superuser (root)
2) have network access, or obtain the actual source files by
some other means.
3) cd to the ports directory containing the port you wish
to build. To build samba, for example, where you'd
previously copied the ports files into the /usr/ports
directory: cd /usr/ports/net/samba
4) make
5) make install
6) make clean
Installing applications from the OpenBSD ports collection:
See http://www.OpenBSD.org/ports.html for current instructions
on obtaining and installing OpenBSD ports.
You should also refer to the ports(7) manual page.
Installing other applications:
If an OpenBSD package or port does not exist for an application
you're pretty much on your own. The first thing to do is ask
<ports@OpenBSD.org> if anyone is working on a port -- there may
be one in progress.
If no such port exists, you might want to tinker with the NetBSD
pkgsrc.
If you can't find an existing port, try to make your own and
feed it back to OpenBSD. That's how our ports collection grows.
Some details can be found at http://www.OpenBSD.org/porting.html
with more help coming from the mailing list, <ports@OpenBSD.org>.
Administrivia:
--------------
There are various mailing lists available via the mailing list
server at <majordomo@OpenBSD.org>. To get help on using the mailing
list server, send mail to that address with an empty body, and it will
reply with instructions. There are also two OpenBSD Usenet newsgroups,
comp.unix.bsd.openbsd.announce for important announcements and
comp.unix.bsd.openbsd.misc for general OpenBSD discussion.
To report bugs, use the 'sendbug' command shipped with OpenBSD,
and fill in as much information about the problem as you can. Good
bug reports include lots of details. Additionally, bug reports can
be sent by mail to:
bugs@OpenBSD.org
Use of 'sendbug' is encouraged, however, because bugs reported with it
are entered into the OpenBSD bugs database, and thus can't slip through
the cracks.
As a favor, please avoid mailing huge documents or files to the
mailing lists. Instead, put the material you would have sent up
for FTP somewhere, then mail the appropriate list about it, or, if
you'd rather not do that, mail the list saying you'll send the data
to those who want it.
For more information about reporting bugs, see
http://www.OpenBSD.org/report.html