INSTALLATION NOTES for OpenBSD/i386 2.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 ipf, ipnat, and bridging are also standard. 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 2.9 also provides 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. Many new user programs and device drivers have been added in OpenBSD 2.9, as well, bringing it closer to our goal of supplying a complete and modern UN*X-like environment. Tools like perl and an improved ksh are standard, as are numerous other useful tools. Because OpenBSD is from Canada, the export of Cryptography pieces (such as SSH, IPSEC, and KerberosIV) 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.) For the i386, OpenBSD 2.9 brings greater stability and security. As a side effect of the full security audit, many userland programs have been significantly cleaned up and debugged. Sources of OpenBSD: ------------------- This is a list of currently known ftp servers: Argentina: ftp://ftp.openbsd.org.ar/pub/OpenBSD Australia: ftp://ftp.aba.net.au/pub/OpenBSD == ftp://ftp.au.openbsd.org/pub/OpenBSD ftp://ftp.it.net.au/mirrors/OpenBSD ftp://ftp.planetmirror.com/pub/OpenBSD ftp://ftp.wiretapped.net/pub/OpenBSD ftp://mirror.aarnet.edu.au/pub/OpenBSD Austria: ftp://gd.tuwien.ac.at/opsys/OpenBSD Belgium: ftp://openbsd.rug.ac.be/pub/OpenBSD Canada: ftp://openbsd.sunsite.ualberta.ca/pub/OpenBSD == ftp://ftp.openbsd.org/pub/OpenBSD ftp://ftp.ca.openbsd.org/pub/OpenBSD ftp://ftp1.ca.openbsd.org/pub/OpenBSD China (Hong Kong): ftp://ftp.shellhung.org/pub/OpenBSD France: ftp://ftp.lip6.fr/pub/OpenBSD == ftp://ftp.fr.openbsd.org/pub/OpenBSD ftp://ftp.grolier.fr/pub/OpenBSD == ftp://ftp2.fr.openbsd.org/pub/OpenBSD ftp://ftp.bsdfr.org/pub/OpenBSD == ftp://ftp3.fr.openbsd.org/pub/OpenBSD Germany: ftp://ftp.fu-berlin.de/unix/OpenBSD == ftp://ftp.de.openbsd.org/unix/OpenBSD ftp://ftp.leo.org/pub/OpenBSD == ftp://ftp2.de.openbsd.org/unix/OpenBSD ftp://ftp.fh-wolfenbuettel.de/pub/os/openbsd ftp://ftp.freenet.de/pub/ftp.openbsd.org/pub/OpenBSD ftp://ftp.gigabell.net/pub/OpenBSD Greece: ftp://filoktitis.noc.uoa.gr/pub/OpenBSD ftp://ftp.duth.gr/pub/OpenBSD Hungary: ftp://ftp.fsn.hu/pub/OpenBSD Ireland: ftp://ftp.esat.net/pub/OpenBSD Italy: ftp://ftp.volftp.mondadori.com/mirror/openbsd Japan: ftp://ftp.dti.ad.jp/pub/OpenBSD == ftp://ftp.jp.openbsd.org/OpenBSD ftp://ftp2.jp.openbsd.org/OpenBSD ftp://ftp.kddlabs.co.jp/OpenBSD ftp://ftp.netlab.is.tsukuba.ac.jp/pub/os/OpenBSD ftp://mirror.nucba.ac.jp/mirror/OpenBSD The Netherlands: ftp://ftp.calyx.nl/pub/OpenBSD ftp://ftp.nl.uu.net/pub/OpenBSD ftp://ftp.nluug.nl/pub/OpenBSD New Zealand: ftp://mirror.qsi.net.nz/pub/OpenBSD == ftp://ftp.nz.openbsd.org/pub/OpenBSD Norway: ftp://ftp.inet.no/pub/OpenBSD ftp://sunsite.uio.no/pub/OpenBSD Romania: ftp://quasar.uvt.ro/pub/OpenBSD Russia: ftp://ftp.chg.ru/pub/OpenBSD ftp://ftp.radio-msu.net/pub/OpenBSD ftp://vell.nsc.ru/pub/OpenBSD Saudi Arabia: ftp://ftp.isu.net.sa/pub/mirrors/ftp.openbsd.org/pub/OpenBSD South Korea: ftp://ftp.snu.ac.kr/pub/BSD/OpenBSD Spain: ftp://ftp.rediris.es/mirror/OpenBSD Sweden: ftp://ftp.stacken.kth.se/pub/OpenBSD == ftp://ftp.se.openbsd.org/pub/OpenBSD ftp://ftp1.se.openbsd.org/pub/OpenBSD ftp://ftp.luth.se/pub/OpenBSD ftp://ftp.sunet.se/pub/OpenBSD Switzerland: ftp://sunsite.cnlab-switch.ch/pub/OpenBSD Taiwan: ftp://openbsd.csie.nctu.edu.tw/pub/OpenBSD Thailand: ftp://ftp.riubon.ac.th/pub/OpenBSD == ftp://ftp.th.openbsd.org/pub/OpenBSD ftp://ftp.kmitl.ac.th/pub/OpenBSD United Kingdom: ftp://ftp.knowledge.com/pub/mirrors/OpenBSD ftp://ftp.plig.org/pub/OpenBSD ftp://sunsite.org.uk/Mirrors/ftp.openbsd.org/pub/OpenBSD USA: ftp://openbsd.cs.colorado.edu/pub/OpenBSD == ftp://ftp.usa.openbsd.org/pub/OpenBSD ftp://ftp3.usa.openbsd.org/pub/OpenBSD ftp://ftp6.usa.openbsd.org/pub/OpenBSD ftp://ftp.eecs.umich.edu/pub/OpenBSD == ftp://ftp1.usa.openbsd.org/pub/OpenBSD ftp://ftp4.usa.openbsd.org/pub/OpenBSD ftp://ftp.cerias.purdue.edu/pub/os/OpenBSD == ftp://ftp7.usa.openbsd.org/pub/os/OpenBSD ftp://archive.progeny.com/OpenBSD ftp://carroll.cac.psu.edu/pub/OpenBSD ftp://download.sourceforge.net/pub/mirrors/OpenBSD ftp://ftp.geto.net/OpenBSD ftp://ftp.op.net/pub/OpenBSD ftp://ftp.src.uchicago.edu/pub/OpenBSD ftp://ftp.tux.org/bsd/openbsd ftp://ftp.twoguys.org/pub/OpenBSD ftp://gandalf.neark.org/pub/distributions/OpenBSD ftp://mirror.csit.fsu.edu/pub/OpenBSD ftp://mirrors.rcn.net/pub/OpenBSD ftp://rt.fm/pub/OpenBSD As well, the file ftp://ftp.openbsd.org/pub/OpenBSD/2.9/ftplist contains a list which is continually updated. If you wish to become a distribution site for OpenBSD, contact miod@openbsd.org. OpenBSD 2.9 Release Contents: ----------------------------- The OpenBSD 2.9 release is organized in the following way. In the .../2.9 directory, for each of the architectures having an OpenBSD 2.9 binary distribution, there is a sub-directory. The i386-specific portion of the OpenBSD 2.9 release is found in the "i386" subdirectory of the distribution. That subdirectory is laid out as follows: .../2.9/i386/ INSTALL.i386 Installation notes; this file. CKSUM Output of the cksum(1) and md5(1) programs MD5 usable for verification of the correctness of downloaded files. floppy29.fs The standard i386 boot and installation floppy; see below. floppyB29.fs The i386 boot and installation floppy; this one features all the drivers not available in floppy29.fs, such as SCSI, RAID, gigabit ethernet, and such; see below. floppyC29.fs The i386 boot and installation floppy; this one features most of the cardbus and pcmcia drivers; see below. cdrom29.fs The i386 boot and installation 2.88mb floppy image that contains almost all OpenBSD drivers; see below. *.tgz i386 binary distribution sets; see below. bsd A stock GENERIC i386 kernel which will be installed on your system during the install. As well you may be interested in .../2.9/tools/ miscellaneous i386 installation utilities like rawrite.exe, ntrw.exe, gzip.exe, and pfdisk.exe; see installation section, below. In summary, there is one i386 floppy image called "floppy29.fs" (which you can copy to a floppy using rawrite.exe or `dd'; as described later in this document). This is a bootable install floppy which can be used both to install and to upgrade OpenBSD to the current version. It is also useful for maintenance and disaster recovery. In addition, the "tools/" directory contains some utilities that might be useful for the installation. Bootable installation/upgrade floppy: This disk contains a file system, is bootable, and has enough utilities on board to prepare your hard disk drive for OpenBSD and to install the OpenBSD distribution. It also holds the utilities needed in order to upgrade a system to the current version of OpenBSD. The OpenBSD/i386 binary distribution sets contain the binaries which comprise the OpenBSD 2.9 release for i386 systems. There are ten binary distribution sets. The binary distribution sets can be found in the "i386" subdirectory of the OpenBSD 2.9 distribution tree, and are as follows: base29 The OpenBSD/i386 2.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. [ 17.4M gzipped, 49.2M uncompressed ] comp29 The OpenBSD/i386 Compiler tools. All of the tools relating to C, C++, and FORTRAN (yes, there are two!) 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. [ 11.2M gzipped, 34.7M uncompressed ] etc29 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.) [ 161.5K gzipped, 730.0K uncompressed ] game29 This set includes the games and their manual pages. [ 2.6M gzipped, 6.2M uncompressed ] man29 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. [ 3.5M gzipped, 13.2M uncompressed ] misc29 This set includes the system dictionaries (which are rather large), the typesettable document set, and man pages for other architectures which happen to be installed from the source tree by default. [ 1.6M gzipped, 5.4M uncompressed ] xbase29 This set includes the base X distribution. This includes programs, headers, libraries, configuration files. [ 5.3M gzipped, 13.9M uncompressed ] xshare29 This set includes all text files equivalent between all architectures. [ 1.4M gzipped, 8.3M uncompressed ] xfont29 This set includes all of the X fonts. [ 5.9M gzipped, 7.1M uncompressed ] xserv29 This set includes all of the X servers. [ 14.8M gzipped, 35.2M uncompressed ] xlink29 This set includes the X server link kit. OpenBSD System Requirements and Supported Devices: -------------------------------------------------- OpenBSD/i386 2.9 works across a broad range of standard PC's and clones, with a wide variety of processors and I/O bus architectures. It can be expected to install and run with minimal difficulties on most current products. The cases where problems may be encountered are typically older proprietary PC's, Laptops or specialized server boxes that rely on a custom BIOS to paper over implementation differences. OpenBSD does not currently support multiple processors (SMP), but will run using one processor on a multi-processor system board. The minimal configuration to install the system is 6M or 8M of RAM and perhaps 60M of disk space. A custom kernel might be able to run with only 4MB, though we do not know of anyone running with a system quite this minimal today. To install the entire system requires much more disk space, and to run X or compile the system, more RAM is recommended. (8M of RAM will actually allow you to run X and/or compile but it won't be speedy. Note that until you have around 16M of RAM, getting more RAM is more important than getting a faster CPU.) Supported hardware include: Processors All CPU chips compatible with the Intel 80386 (i386) architecture: 386/486 (SX/DX/DX2/DX4) Intel Pentium/Pentium-MMX Intel Pentium Pro/II/III/Celeron/Xeon Intel Pentium IV AMD 6x86 AMD K5/K6/K6-2/K6-3 AMD Athlon/Duron Cyrix MediaGX/M1/M2 VIA Cyrix III Rise mP6 IDT WinChip NexGen 586 Transmeta TMS3200, TMS5400, TMS5600 Everything that is a clone of the 386 or up should work fine. The only CPU that is known to work poorly (due to flawed motherboards designs) is the Cyrix 386DLC. Buses All standard ISA, EISA, VLB, and PCI bus based machines, including: Intel 450GX/KX based machines Intel 450NX based machines ServerWorks chipset-based machines (We just had to mention those last three, since they are the hardest to support)) Both 16-bit PCMCIA Cards and newer 32-bit CardBus support Universal Serial Bus (USB) The MCA bus found in various IBM PS/2 machines is not supported. Bus Interfaces Standard PCI-PCI bridges, including PCI expansion backplanes YENTA-compatible PCI-CardBus bridges Entropy Sources Interrupt latency collection from many devices INtel 82802 random number generator found on i810, i815, i820, i840, i850 and i860 based systems. Disk Controllers Floppy controllers. ISA MFM, ESDI, IDE, and RLL hard disk controllers. PCI IDE Controllers Acer Labs M5229 Advanced Micro Devices 756, 766 CMD Tech PCI0640, PCI0643, PCI0646, PCI0648, and PCI0649 Contaq Microsytems/Cypress CY82C693 HighPoint HPT366, HPT370 Intel PIIX, PIIX3, and PIIX4 Intel 82801 (ICH/ICH0/ICH2) OPTi 82C568, 82D568, and 82C621 Promise PDC20246, PDC20262, PDC20265/7 Silicon Integrated Systems 5513 (5597/5598) VIA Technologies VT82C586[A], VT82C596, VT82C686 (Other PCI IDE-compliant controllers should work, but those not listed above may not be capable of DMA modes) SCSI Host Adapters Adaptec AHA-1540, AHA-154xA, AHA-154xB, AHA-1542C, AHA-1542CF, AHA-1542CP, AHA-1640 Adaptec AHA-174x Adaptec AIC-6260 and AIC-6360 based boards, including: the Adaptec AHA-152x and the SoundBlaster SCSI host adapter. (Note that you cannot boot from these boards if they do not have a boot ROM; only the AHA-152x and motherboards using this chip are likely to be bootable, consequently.) Adaptec AIC-7770-based boards, including the Adaptec AHA-274x and AHA-284x families) Adaptec AHA-[23]94x[W] cards and some on-board PCI designs using the AIC7870 and AIC7880 chips. Adaptec AHA-[23]94xU[2W] cards and some on-board PCI designs using the AIC789[01], AIC7895, AIC789[67] chips Adaptec AIC-780[29] chips and products like the AHA-29160 based upon it which do 160MB/sec SCSI. AdvanSys 'U', 'UW', 'U2W' and 'U160' PCI SCSI controllers including the ABP940U[AW], ASB3940U[AW]-00, ASB3940U2W-00 and ASB3950U160 AMD Am53c974 PCscsi-PCI SCSI controllers, including: Tekram DC-390 Buslogic BT-54x (Adaptec AHA-154x clones) BusLogic 445, 74x, 9xx (But not the new "FlashPoint" series of BusLogic SCSI adapters) Initio INIC-940 and INIC-950 based PCI SCSI host adapters, including the Initio INI-9090U and Initio INI-9100U/UW, and the Iwill 2935UW QLogic PCI SCSI controllers Seagate/Future Domain ISA SCSI adapter cards, including: ST01/02 Future Domain TMC-885 Future Domain TMC-950 Symbios Logic (NCR) 53C8xx, 53C1010, and 53C1510D-based PCI SCSI host adapters (including generic/no name cards, old ASUS cards, the DTC-3130 series, Diamond Fireport series, etc.) Tekram DC-300B and DC-320E (Adaptec AHA-154x clones) Ultrastor 14f, 24f, and 34f WD-7000 SCSI host adapters RAID and Cache Controllers 3ware Escalade 3W-5x00, 3W-6x00 Adaptec FSA-based RAID controllers, including: Adaptec AAC-2622, AAC-364, AAC-3642 Dell PERC 2/Si, PERC 2/QC, PERC 3/Si, PERC 3/Di, PERC 3/QC HP NetRAID-4M American Megatrends Inc. MegaRAID controllers Compaq Smart ARRAY PCI/EISA adapters, including: Compaq Integrated Array Compaq IAES Compaq IDA, IDA-2 Compaq RAID LC2 Compaq Smart Array 221, 3100ES, 3200, 4200, 4250ES, 431 Compaq SMART, SMART-2/E, SMART-2/P, SMART-2DH, SMART-2SL DPT SmartCache and SmartRaid III/IV PCI/EISA adapters ICP-Vortex GDT 6XXXR[DNPS] series CD-ROM and DVD-ROM Drives Mitsumi CD-ROM drives [*] [+] [Note: The Mitsumi driver device probe is known to cause trouble with several devices!] Most SCSI CD-ROM, CD-R, CD-RW, and DVD drives Most ATAPI CD-ROM, CD-R, CD-RW, and DVD drives Tape Drives Most SCSI tape drives Most SCSI tape changers QIC-02 and QIC-36 format (Archive- and Wangtek- MDA, CGA, VGA, SVGA, and HGC Display Adapters. (Note that not all of the display adapters OpenBSD/i386 can work with are supported by X. See the XFree86 FAQ for more information.) Serial Ports 8250/16450-based ports 16550-based ports ST16660-base ports XR16850-based ports (only in the pccom driver) AST-style 4-port serial boards [*] BOCA 8-port serial cards [*] Cyclades Cyclom-{4, 8, 16}Y serial boards [*] IBM PC-RT 4-port serial boards [*] Parallel Ports Any standard parallel port Communication Controllers Universal Serial Bus host controllers, including: USB Universal Host Controller USB Open Host Controller PCI `universal' communication cards, providing serial and parallel ports, including: Dolphin Peripherals 4014 (dual parallel) and 4035 (dual serial) SIIG Cyber 2P1S (dual parallel, single serial) and 2S1P (dual serial, single parallel) SIIG Cyber 4S (quad serial) SIIG Cyber I/O (single parallel, single serial) SIIG Cyber Parallel, Parallel Dual, Serial, Serial Dual VScom PCI-800 (8 port serial, probably OEM) AT&T/Lucent Venus Modem (found on IBM 33L4618 card, Actiontec 56K, and others) US Robotics 3CP5609 PCI (modem) Lava Computers 2SP-PCI (parallel port) Lava Computers 2SP-PCI and Quattro-PCI (dual serial) NEC PK-UG-X008 (serial) NEC PK-UG-X001 K56flex PCI (modem) Koutech IOFLEX-2S (dual serial) Ethernet Adapters 3Com 3c501 3Com 3c503 3Com 3c505 [*] 3Com 3c507 3Com 3c509, 3c579, and 3c59x 3Com 3c515 [*] [+] 3Com 3c9xx Etherlink XL adapters, including: 3Com 3c900/3c900B PCI adapters 3Com 3c905/3c905B/3c905C PCI adapters 3Com 3c980/3c980C server adapters 3Com 3cSOHO apapter 3Com 3c900B-FL and 3c900B-FL/FX fiber optic adapters 3Com 3c555/3c556/3c556B MiniPCI adapters Dell on-board 3c920 Dell Precision on-board 3c905B Dell OptiPlex GX1 on-board 3c918 Dell Latitude laptop docking station embedded 3c905 3Com 3c990 3XP Typhoon/Sidewinder PCI adapters, including: 3C990-TX-95 3C990-TX-97 3C990-TX-SVR95 3C990-TX-SVR97 Adaptec "Starfire" AIC-6915 based PCI adapters, including: Adaptec Single32 ANA-69011 Adaptec Single64 ANA-62011 and ANA-62020 Adaptec Duo64 ANA-62022 Adaptec Quartet64 ANA-62044 ADMtek AL981 ("Comet") and AN983 ("Centaur-P") based PCI adapters, including: Accton EN2242 MiniPCI Linksys LNE100TX v4.x Mototech ME316 ADMtek AN986-based USB adapters, including: Billionton Systems USB100 Corega FEther USB-TX D-Link DSB-650TX LinkSys USB100TX Melco Inc. LU-ATX SMC 2202USB Kingston KNU101TX AMD LANCE and PCnet-based ISA Ethernet adapters, including: Novell NE1500T Novell NE2100 Kingston 21xx AMD PCnet-based PCI Ethernet adapters, including: BOCALANcard/PCI AT&T StarLAN 10, EN100, and StarLAN Fiber ASIX 88140A/88141 PCI Ethernet adapters, including: CNet Pro110B Alfa Inc. GFC2204 CATC USB-EL1210A-based USB adapters, including: CATC Netmate and Netmate II Belkin F5U011/F5U111 Davicom DM9100, DM9102, and DM9102A based PCI adapters, including: Jaton XpressNet Digital DC21x4x-based PCI Ethernet adapters, including: Older SMC PCI EtherPower 10, 10/100 (models 8432, 9332, and 9334) Older LinkSys 10, 10/100 (newer models are supported by other drivers) Znyx ZX3xx Cogent EM100FX and EM440TX Digital PCI DE435, EISA DE425, DE450, DE500 Asante Intel EtherExpress 16 Intel EtherExpross PRO/10 ISA Intel i8255x-based (except the i82556) PCI adapters, 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 Kawasaki LSI KL5KUSB101B-based USB adapters, including: 3Com 3c19250 3Com 3c460 HomeConnect ADS Technologies USB-10T Aox USB101 ATen UC10T Corega USB-T D-Link DSB-650 Entegra NET-USB-E45 Kawasaki USB101 LinkSys USB10T Netger EA101 Peracom USB SMC 2102/2104USB I/O Data USB-ET/T Lite-On PNIC/PNIC-II-based adapters, including: Kingston KNE110TX LinkSys LNE100TX Matrox Networks FastNIC 10/100 Netgear FA310TX Macronix 98713/713A/715/715A/725/727/732-based adapters, including: Accton EN1217 Addtron AEF-320TX/AEF-330TX CNet PRO120A/PRO120B Complex RL-100TX NDC Communications SOHOware SFA110A SVEC PN102-TX Fast Ethernet card National Semiconductor DP83815-based PCI adapters, including: Netgear FA311/FA312 Novell NE1000, NE2000 RealTek 8129, RealTek 8139 Ethernet adapters, including: Accton MPX 5030/5038 Allied Telesyn AT2550 D-Link DFE530+TX, 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 SiS 900 and SiS 7016-based PCI adapters, including: Mototech ME313 NetSurf NS-KFE30D SMC/WD 8003, 8013, and the SMC "Elite16" ISA boards SMC/WD 8216 (the SMC "Elite16 Ultra" ISA boards) [X SEE BELOW] SMC EtherEZ PNP SMC EtherPower II (EPIC 10/100) Sundance ST201-based PCI adapters, including: D-Link DFE-550TX Texas Instruments ThunderLAN PCI Ethernet adapters, including: Compaq Netelligent PCI Adapters Compaq NetFlex 3/P Compaq Deskpro integrated adapter Compaq Prosignia integrated adapter Olicom OC2135, OC2183, OC2325, OC2326 Racore 8165 and 8148 TI ThunderLAN adapters VIA Rhine/RhineII Ethernet adapters, including: Addtron AEF-360TX Hawking PN102TX D-Link DFE530TX Winbond W89C840F Ethernet adapters, including: Trendware TE100-PCIE Compex RL100-ATX 10/100baseTX Xircom 16-bit PCMCIA adapters, including: Xircom CE3 Xircom Realport Wireless Ethernet Adapters Aironet 802.11DS PCMCIA and PCI RayLink Aviator 2.4/Pro 802.11FH PCMCIA WaveLAN IEEE 802.11DS Addtron AWP-100 802.11DS PCMCIA Gigabit Ethernet Adapters Alteon Tigon I/II PCI Gigabit Ethernet boards 3Com 3c985 and 3c985B Alteon ACEnic V (fiber and copper) Digital EtherWORKS 1000SX Farallon PN9000SX Netgear GA620 and GA620T SGI Tigon Intel i82452-based adapters, including: Intel Pro/1000 Gigabit Server adapter SysKonnect SK-9841/9842/9843/9844 Gigabit Ethernet adapters ATM Adapters Efficient Networks EN-155 and Adaptec ANA-590X ATM interfaces FDDI Adapters Digital DEFEA EISA and PCI FDDI adapters Wan Adapters Lan Media Corporation SSI (T1)/HSSI/DS1/DS3 WAN interfaces Cryptography Accelerators Broadcom Bluesteelnet uBsec 5501, 5601, 5805 Hi/Fn 7751-based boards, including: GTGI PowerCrypt Encryption Accelerator NETSEC 7751 HiFn reference board Invertex AEON PC Cards (PCMCIA and Carbus) ATA cards, including: ATA/IDE card drives ATA/IDE CD-ROM adapters CF/ATA flash cards and disk drives Ethernet adapters, including: 3Com EtherLink and EtherLink XL-based LAN PC cards, including: 3Com 3c556, 3c562 3Com 3c574TX, 3c[CX]FE574BT 3Com 3c589, 3c589[BCDE] 3Com 3c575TX, 3c[CX]FE575[BC]T CardBus 3Com 3c[CX]FEM656, 3c[CX]656[BC] CardBus Intel/DEC 21443 "Tulip" clones, including: ADMtex AN985 Centaur-C CardBus IBM EtherJet 10/100 CardBus SMC EZ CardBus 10/100 Xircom X3201 CardBus adapters, including RealPort models Intel i8255x-based, including: Intel PRO/100 CardBus II NE2000-based, including: Accton EN2216 AmbiCom AMB8002T D-Link DE-650, DE-660 Genius ME 3000II SE Hawking PN650TX IC-Card Kingston KNE-PC2 Linksys PCMPC100, EC2T Combo NDC Instant-Link Netgear FA410TX Network Everywhere NP10T New Media LiveWire 10/100 SMC 91Cxx-based, including: Megahertz XJEM1144, CC10BT SMC EtherEZ 8020BT Xircom, including: Xircom CreditCard CE2 PCMCIA controllers, including: Intel i82365 and compatibles SCSI host adapters, including: Adaptec SlimSCSI APA-14[56]0 Serial ports, including: Most modems, digital cellular modems, and serial cards should work Wireless Ethernet adapters: See above 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 Pointing Devices "Logitech"-style bus mice [*] [+] "Microsoft"-style bus mice [*] [+] "PS/2"-style mice [*] [+] Serial mice (uses serial port driver) compatible) tape drives [*] [+] Sound Devices C-Media CMI8[37]38 [*] [+] Cirrus Logic CrystalClear CS4280, CS4281 [*] [+] Ensoniq AudioPCI [*] [+] ESS Tech ES188[78], ES888 [*] [+] ESS Solo-1 PCI AudioDrive [*] [+] ESS Maestro 1, 2 and 2E and clones, NOT Maestro 3 [*] [+] Forte Media FM801 audio [*] [+] Gravis Ultrasound and Ultrasound Max [*] [+] Intel i810/i820 and 440MX AC'97 [*] [+] NeoMagic 256AV/ZX [*] [+] SoundBlaster ISA cards and 100% compatibles [*] [+] SoundBlaster PCI128 [*] [+] VIA VT82C686A SouthBridge integrated AC'97 audio [*] [+] Yamaha OPL3-SA3 [*] [+] Yamaha DS-XG [*] [+] [The following drivers are not extensively tested:] Personal Sound System [*] [+] ProAudio Spectrum [*] [+] S3 SonicVibes [*] [+] Windows Sound System [*] [+] Miscellaneous Devices APM power management, Brooktree 8[47][89] based frame grabber and TV tuner cards, including: [*] [+] Hauppage Wincast TV STB TV PCI Television Tuner Miro PC TV Intel Smart Video Recorder III IMS TV Turbo AVer Media TV/FM Many kinds of ISA Plug-and-Play cards Nearly all SB-style audio cards Nearly all joystick ports Nearly all Yamaha-style audio cards Nearly all NE2000-style Ethernet cards Nearly all SMC-style Ethernet cards Most serial port or modem cards 3c509 cards in PnP mode NE2100 Etherent cards Drivers for hardware marked with "[*]" are NOT included on the distribution floppies. Except as noted above, all other drivers are present on install floppy. Also, at the present time, the distributed kernels support only one SCSI host adapter per machine. OpenBSD normally allows more, though, so if you have more than one, you can use all of them by compiling a custom kernel once OpenBSD is installed. Support for devices marked with "[+]" IS included in the "generic" kernels, although it is not in the kernel on the installation floppy. Hardware the we do NOT currently support, but get many questions about: The "Micro Channel" MCA bus used in many IBM PS/2 models NCR 5380-based and 53400-based SCSI host adapters QIC-40 and QIC-80 tape drives (these are the tape drives that connect to the floppy disk controller) Multiprocessor motherboards (though they will run fine using one processor only) Sony and Panasonic proprietary CD-ROM interfaces Parallel-port ZIP drives (SCSI and ATAPI ZIP drives work fine) Intel i82556 (EtherExpress PRO/100A) and i82596 (EtherExpress PRO/10 PCI) Ethernet adapters Hewlett-Packard PC-LAN+ (HP27xxx) Ethernet adapters SoundBlaster Live! (EMU10k1) sound devices Aureal Vortex sound cards Winmodems Infrared devices, such as commonly found on laptops Firewire Mylex and Intel RAID controllers PCMCIA: Memory cards Most multifunction cards We are planning future support for many of these devices. To be detected by the distributed kernels, some devices must be configured with specific settings. Here's their list: Device Name Port IRQ DRQ Misc ------ ---- ---- --- --- ---- Serial ports pccom0 0x3f8 4 [8250/16450/16550/clones] pccom1 0x2f8 3 [8250/16450/16550/clones] pccom2 0x3e8 5 [8250/16450/16550/clones] ast0 0x1a0 5 [AST 4-port serial card] cy0 12 iomem 0xd4000 [Cyclom serial card] Parallel ports lpt0 0x378 7 [interrupt-driven or polling] lpt1 0x278 [polling only] lpt2 0x3bc [polling only] MFM/ESDI/IDE/RLL hard disk controllers wdc0 0x1f0 14 [supports two disks or atapi] wdc1 0x170 15 [supports two disks or atapi] Floppy controller fdc0 0x3f0 6 2 [supports two disks] AHA-154x, AHA-174x (in compatibility mode), or BT-54x SCSI host adapters aha0 0x330 any any aha1 0x334 any any BT445, BT74x, or BT9xx SCSI host adapters bt0 0x330 any any bt1 0x334 any any Ultrastor 14f, 24f (if it works), or 34f SCSI host adapters uha0 0x330 any any uha1 0x334 any any AHA-152x, AIC-6260- or AIC-6360-based SCSI host adapters aic0 0x340 11 any Seagate ST0[12], Future Domain TMC-8xx based SCSI controllers sea0 5 iomem 0xc8000 WD7000 and TMC-7000 SCSI host adapters wds0 0x350 15 6 wds1 0x358 11 5 SCSI disks sd0 first SCSI disk (by SCSI id) sd1 second SCSI disk (by SCSI id) sd2 third SCSI disk (by SCSI id) sd3 fourth SCSI disk (by SCSI id) SCSI tapes st0 first SCSI tape (by SCSI id) st1 second SCSI tape (by SCSI id) SCSI CD-ROMs cd0 first SCSI CD-ROM (by SCSI id) cd1 second SCSI CD-ROM (by SCSI id) SMC/WD 8003, 8013, Elite16, and Elite16 Ultra Ethernet boards we0 0x280 9 iomem 0xd0000 we1 0x300 10 iomem 0xcc000 Novell NE1000, or NE2000 Ethernet boards ne0 0x240 9 iomem 0xd8000 ne1 0x300 10 ne2 0x280 9 3COM 3c501 Ethernet boards el0 0x300 9 3COM 3c503 Ethernet boards ec0 0x250 9 iomem 0xd8000 3COM 3c505/Etherlink+ Ethernet boards eg0 0x310 5 AT&T StarLAN 10, EN100, or StarLAN Fiber, or 3COM 3c507 Ethernet boards ie0 0x360 7 iomem 0xd0000 EtherExpress boards ie1 0x300 10 IsoLan, NE2100, and DEPCA le0 0x360 15 6 Intel EtherExpress PRO/10 ex0 0x320 5 PCI ethernet boards need to have an interrupt, either assigned in your PCI BIOS, or autoconfigured. Hardware not listed in the above table doesn't need any specific configuration. SPECIAL CARE FOR SMC ULTRA ELITE -------------------------------- Note for SMC Elite Ultra ethernet card users: The Elite Ultra is very sensitive to how its I/O port is treated. Mistreating it can cause a number of effects -- everything from the card not responding when the kernel probes, or the soft configuration being corrupted or wiped completely. By default, the kernel ships with device we1 configured for the 'default' Elite Ultra locations, comprising of port 0x300, irq 10, and memory location 0xcc000. This matches a hard coded jumper on the board as well a common soft config setting. Unfortunately, the kernel's autoconfiguration process (specifically, some of the devices it probes for) cause conflicts with the SMC Elite Ultra, and very often cause it to lose its configuration and fail its own probe. If this happens, you must boot the computer into DOS, and run the EzSetup program from SMC (if you do not have a copy on the floppy accompanying your board, the complete URL to download the program is ftp://ftp.smc.com/pub/nics/ethernet/elite_ultra/gez122.exe). This program will allow you to reconfigure and recover a card that has lost its configuration with a minimum of hassle. In order to avoid blowing away the card, one *must* use the run-time kernel configuration system when booting the Install kernel. This is done by giving the -c flag to the initial boot request. Following the loading of the kernel, the user is presented with a UKC> prompt. At this prompt, a variety of commands may be issued, but the relevant one to getting the SMC Elite Ultra running is 'disable'. The wt0, el0, and ie1 devices all need to be disabled. This is done by typing 'disable' followed by the name of the device, i.e., 'disable wt0', and pressing return. If, for some reason, your Elite Ultra is not configured at the 'default' location the kernel is expecting it, you may also use the 'change' command in the UKC system to modify where the kernel will look for it. Typing 'change we1' will allow you to modify those settings. Note that running the card at an i/o port of anything other then 0x300 at this point is not recommended, and is beyond the scope of this document-- by doing so you risk other device probes wreaking the havoc we are trying to avoid. When all three extra devices are disabled and any changes made, the 'quit' command will exit the UKC. The kernel should then boot, and find your Elite Ultra on device we1. SPECIAL CARE FOR PCI BIOS As all BIOS implementations and subsystems this one has bugs too. Sometimes specifications are unclear about interfaces and/or data validation. These all cause our driver for PCI BIOS to misbehave in more or less fatal ways, such as panics on pcibios0 configuration or pci device attachments, or unconfigured pci devices due to irq and/or I/O address misconfiguration. Fast workaround Boot by giving the -c flag to the initial boot request. Following the loading of the kernel, the user is presented with a UKC> Then type the following commands: UKC> change bios0 165 bios0 at mainbus0 bus -1 flags 0x0 change [n] y bus [-1] ? flags [0] ? 3 165 bios0 changed 165 bios0 at mainbus0 bus -1 flags 0x3 UKC> quit This will disable the pcibios0 attachment. Sometimes, especially when hangs occur on particular pci device attachments, moving pci cards into a different slot helps. Fixing for good Try to gather dmesg output from the failing configuration, for example by using serial console (see boot(8)) and send it to mickey@openbsd.org along with descriptions of your hardware setup. Dig in the code and fix problems. Getting the OpenBSD System onto Useful Media: --------------------------------------------- Installation is supported from several media types, including: DOS partitions FFS partitions EXT2 partitions Tape Remote NFS partition FTP HTTP No matter which installation medium you choose, you'll need to have a floppy disk (1.44Mb required). If you are using a UN*X-like system to write the floppy image to disk, you should use the "dd" command to copy the file system image (floppy29.fs) directly to the raw floppy disks. It is suggested that you read the dd(1) manual page or ask your system administrator to determine the correct set of arguments to use; it will be slightly different from system to system, and a comprehensive list of the possibilities is beyond the scope of this document. If you are using DOS to write the floppy image to disk, you should use the "rawrite" utility, provided in the "2.9/tools" directory of the OpenBSD distribution. It will write the file system image (floppy29.fs) to a disk. If you are using NT to write the floppy image to disk, you should use the "ntrw" utility, provided in the "2.9/tools" directory of the OpenBSD distribution, instead Note that when installing, the floppy can be write-protected (i.e. read-only). Obviously, the steps necessary to prepare the distribution sets for installation or upgrade depend on which installation medium you choose. The steps for the various media types are outlined below. To install or upgrade OpenBSD using a tape, you need to do the following: To install OpenBSD from a tape, you need to make a tape that contains the distribution set files, in "tar" format. If you're making the tape on a UN*X-like system, the easiest way to do so is probably something like: tar cf where "" is the name of the tape device that describes the tape drive you're using (possibly /dev/rst0, or something similar, but it will vary from system to system. (If you can't figure it out, ask your system administrator.) In the above example, "" are the distribution sets' directories, for the distribution sets you wish to place on the tape. For instance, to put the "base29", "etc29", and "bsd" distributions on tape (in order to do the absolute minimum installation to a new disk), you would do the following: cd .../2.9 # the top of the tree cd i386/ tar cf base29 etc29 bsd (Note that you still need to fill in "" in the example.) Once you have the files on the tape, you can proceed to the next step in the installation or upgrade process. If you're installing OpenBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading. To install or upgrade OpenBSD using a remote partition, mounted via NFS, you must do the following: NOTE: This method of installation is recommended only for those already familiar with using BSD network configuration and management commands. If you aren't, this documentation should help, but is not intended to be all-encompassing. Place the OpenBSD distribution sets you wish to install into a directory on an NFS server, and make that directory mountable by the machine on which you are installing or upgrading OpenBSD. This will probably require modifying the /etc/exports file on the NFS server and resetting its mount daemon (mountd). (Both of these actions will probably require superuser privileges on the server.) You need to know the numeric IP address of the NFS server, and, if the server is not on a network directly connected to the machine on which you're installing or upgrading OpenBSD, you need to know the numeric IP address of the router closest to the OpenBSD machine. Finally, you need to know the numeric IP address of the OpenBSD machine itself. Once the NFS server is set up properly and you have the information mentioned above, you can proceed to the next step in the installation or upgrade process. If you're installing OpenBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading. If you are upgrading OpenBSD, you also have the option of installing OpenBSD by putting the new distribution sets somewhere in your existing file system, and using them from there. To do that, you must do the following: Place the distribution sets you wish to upgrade somewhere in your current file system tree. At a bare minimum, you must upgrade the "base" binary distribution, and so must put the "base29" set somewhere in your file system. If you wish, you can do the other sets, as well, but you should NOT upgrade the "etc" distribution; the "etc" distribution contains system configuration files that you should review and update by hand. Once you have done this, you can proceed to the next step in the upgrade process, actually upgrading your system. Preparing your System for OpenBSD Installation: ----------------------------------------------- NOTE: If you wish to install OpenBSD on your whole disk, i.e. you do not want DOS or any other operating system to reside on your hard disk, you can skip this section and go on to the section that describes installation, below. If you're upgrading your system from a previous release of OpenBSD, you should have proceeded directly to the section about upgrading; you need none of the information presented here. First and foremost, before beginning the installation process, MAKE SURE YOU HAVE A RELIABLE BACKUP of any data on your hard disk that you wish to keep. Repartitioning your hard disk is an excellent way to destroy important data. Second, if you are using a disk controller which supports disk geometry translation, be sure to use the same parameters for OpenBSD as for DOS or the other operating systems installed on your disk. If you do not, it will be much harder to make OpenBSD properly coexist with them. Utilities exist which will print out the disk geometry which DOS sees; some versions of DOS "fdisk" also do this. If you have an "EIDE" hard disk, DOS and OpenBSD probably won't see the same geometry, and you must be careful to find out the DOS geometry and tell OpenBSD about it during the installation. Third (but related to the second point above), if you are using a hard disk with more sectors than DOS or your controller's BIOS supports without some kind of software translation utility or other kludge, you MUST BE SURE that all partitions which you want to boot from must start and end below cylinder 1024 by the BIOS's idea of the disk, and that all DOS partitions MUST EXIST ENTIRELY BELOW cylinder 1024, or you will either not be able to boot OpenBSD, not be able to boot DOS, or you may experience data loss or filesystem corruption. Be sure you aren't using geometry translation that you don't know about, but that the DOS "fdisk" program does! Fourth, use the other operating system's "fdisk" program or partition editor to create at least one of the partitions to be used for that operating system. If that operating system is already set up to use the entire disk, you will have to back it up, remove and recreate a smaller partition for it, and then restore the data from that partition. You do not have to create an OpenBSD partition at this time, the OpenBSD install- ation will give you an opportunity to create the partition needed for OpenBSD. Finally, do whatever is necessary to restore order to the partition you took space away from. If it was a DOS partition, you probably will need to use "format" to create a new file system on it, and then restore your important files from your backups. Other operating systems will have different needs; most will need to reformat the partition, and if it was their "main" partition, will probably need to be reinstalled. Once you've backed all your data up, there is a tool called fips 2.0 that can shrink your DOS/Windows/Windows95 partition to make room for OpenBSD. It is included in the i386 tools area of this distribution as a convenience. It is strongly advised that you read its documentation and understand the consequences of your actions before using it. In some cases, defragmenting your disk and running fips may be much faster than reinstalling your DOS partition from the backup. Your hard disk is now prepared to have OpenBSD installed on it, and you should proceed with the installation instructions. Installing the OpenBSD System: ------------------------------ Installing OpenBSD is a relatively complex process, but if you have this document in hand and are careful to read and remember the information which is presented to you by the install program, it shouldn't be too much trouble. Before you begin, you should know the geometry of your hard disk, i.e. the sector size (note that sector sizes other than 512 bytes are not currently supported), the number of sectors per track, the number of tracks per cylinder (also known as the number of heads), and the number of cylinders on the disk. The OpenBSD kernel will try to discover these parameters on its own, and if it can it will print them at boot time. If possible, you should use the parameters it prints. (You might not be able to because you're sharing your disk with another operating system, or because your disk is old enough that the kernel can't figure out its geometry.) If OpenBSD will be sharing the disk with DOS or another operating system, you should have already completed the section of these notes that instructed you on how to prepare your hard disk. You should know the size of the OpenBSD area of the disk and its offset from the beginning of the disk. You will need this information when setting up your OpenBSD partitions. If your BIOS uses translated geometry, you should use this geometry for the remainder of the install. This is only necessary if you are sharing the disk with other operating systems that use the translated geometry. You should now be ready to install OpenBSD. 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). Boot your machine using the floppy29.fs floppy. When presented with the boot prompt hit return. If the boot prompt does not appear in a reasonable amount of time, you either have a bad boot floppy or a hardware problem. Try writing the floppy29.fs floppy image to a different disk, and using that. If that doesn't work, try booting after disabling your CPU's internal and external caches (if any). If it still doesn't work, OpenBSD probably can't be run on your hardware. This can probably be considered a bug, so you might want to report it. If you do, please include as many details about your system configuration as you can. It will take a while to load the kernel from the floppy, most likely more than a minute. If some action doesn't eventually happen, or the spinning cursor has stopped and nothing further has happened, either your boot floppy is bad or you are having hardware problems, and should proceed as outlined above. 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. While booting, you will probably see several warnings. You should be warned that no swap space is present. Do not be alarmed, these are completely normal. When you reach the prompt asking you for a shell name, just hit return. Now you will be asked whether you wish to do an "install" or an "upgrade". 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, you will be asked which terminal type to use. You should just hit return to select the default (pcvt25). The install program will then tell you which disks of that type it can install on, and ask you which it should use. The name of the disk is typically "wd0" for IDE/RLL/ESDI/ST506 drives or "sd0" for SCSI drives. Reply with the name of your disk. Next you will have to edit or create a 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 and create an OpenBSD partition. If fdisk is being invoked on your behalf, it will start by displaying the current partitions defined and then allow you to modify this information, add new partitions and change which partition to boot from by default. If you make a mistake, you will be allowed to repeat this procedure as necessary to correct this. Note that you should make OpenBSD be the active partition at least until the install has been completed. Next the disk label which defines the layout of the OpenBSD file systems must be set up. The installation script will invoke an 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. 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". Create your next partition as 'd' and continue from there with any additional partitions. If you have DOS or Linux partitions defined on the disk, these will usually show up as partition 'h', 'i', and so on. When you are finished with disklabel you will be prompted for the mount points for the partitions in the current label. For help in the disk label editor, enter '?' or 'M' to view the manual page (see the info on the ``-E'' flag). Note that all OpenBSD partitions in the disk label must have an offset that makes it start within the OpenBSD part of the disk, and a size that keeps it inside of that portion of the disk. This is within the bounds of the 'c' partition if the disk is not being shared with other operating systems, and within the OpenBSD fdisk partition if the disk is being shared. The swap partition (usually 'b') should have a type of "swap", all other native OpenBSD partitions should have a type of "4.2BSD". Block and fragment sizes are usually 8192 and 1024 bytes, but can also be 4096 and 512 or even 16384 and 2048 bytes. The install program will now label your disk and ask which file systems should be created on which partitions. It will auto- matically select the 'a' partition to be the root file system. Next it will ask for which disk and partition you want a file system created on. This will be the same as the disk name (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 NFS, HTTP or FTP, and will also be the configuration used by the system after the installation is complete. If you select to configure the network, the install program will ask you for a name of your system and the DNS domain name to use. Note that the host name should be without the domain part, and that the domain name should NOT include the host name part. Next the system will give you a list of network interfaces you can configure. For each network interface you select to configure, it will ask for the IP address to use, the symbolic host name to use, the netmask to use and any interface-specific flags to set. The interface-specific flags are usually used to determine which media the network card is to use. The flags usually carry the following meaning: -link0 -link1 Use BNC (coaxial) port [default] link0 -link1 Use AUI port link0 link1 Use UTP (twisted pair) port After all network interfaces 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, NFS or a local disk partition. To install from a tape, the distrib- ution sets must have been written to tape prior to running the installation program, either as tar images or as gzipped tar images. Note that installation from floppies is not currently supported. To install via FTP: To begin an FTP install you will need the following pieces of information. Don't be daunted by this list; the defaults are sufficient for most people. 1) Proxy server URL if you are using a URL-based ftp proxy (squid, CERN ftp, Apache 1.2 or higher). You need to define a proxy if you are behind a firewall that blocks outgoing ftp (assuming you have a proxy available to use). 2) Do you need to use active mode ftp? By default, ftp will attempt to use passive mode and fall back to an active connection if the server does not support passive mode. You only need to enable this option if you are connecting to a buggy ftp daemon that implements passive ftp incorrectly. Note that you will not be asked about active ftp if you are using a proxy. 3) The IP address (or hostname if you enabled DNS earlier in the install) of an ftp server carrying the OpenBSD 2.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/2.9/i386 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). 3) The IP address (or hostname if you enabled DNS earlier in the install) of an http server carrying the OpenBSD 2.9 distribution. If you don't know, just hit return when asked if you want to see a list of such hosts. 4) The directory holding the distribution sets. There is no standard location for this; You should use the directory specified along with the server in the list of official http mirror sites that you received in step 3. For instructions on how to complete the installation via http, see the section named "Common URL installations" below. To install from tape: In order to install from tape, the distribution sets to be installed must have been written to tape previously, either in tar format or gzip-compressed tar format. You will also have to identify the tape device where the distribution sets are to be extracted from. This will typically be "nrst0" (no-rewind, raw interface). Next you will have to provide the file number of the set that is to be extracted. Note that the file number starts at 1, which is the first file written to the tape, unless you have created a bootable tape, in which case the file number starts at 3. The install program will not automatically detect whether an image has been compressed, so it will ask for that information before starting the extraction. To install from CD-ROM: When installing from a CD-ROM, you will be asked which device holds the distribution sets. This will typically be either "cd0" or "acd0". Next you will be asked which partition on the CD-ROM the distribution is to be loaded from. This is normally partition "a". Next you will have to identify the file system type that has been used to create the distribution on the CD-ROM, this can be either FFS or ISO CD9660. The OpenBSD CD distribution uses the CD9660 format. You will also have to provide the relative path to the directory on the CD which holds the distribution, for the i386 this is "2.9/i386". For instructions on how to complete the installation from the CD-ROM distribution, see the section named "Common file system installations" below. To install from a NFS mounted directory: When installing from a NFS-mounted directory, you must have completed network configuration above, and also set up the exported file system on the NFS server in advance. First you must identify the IP address of the NFS server to load the distribution from, and the file system the server expects you to mount. The install program will also ask whether or not TCP should be used for transport (the default is UDP). Note that TCP only works with newer NFS servers. You will also have to provide the relative path to the directory on the file system where the distribution sets are located. Note that this path should not be prefixed with a '/'. For instructions on how to complete the installation from the CD-ROM distribution, see the section named "Common file system installations" below. To install from a local disk partition: When installing from a local disk partition, you will first have to identify which disk holds the distribution sets. This is normally "wdN" or "sdN" where N is a number 0 through 9. Next you will have to identify the partition within that disk that holds the distribution, this is a single letter between 'a' and 'p'. You will also have to identify the type of file system residing in the partition identified. Currently, you can install from partitions that has been formatted as 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 the a local disk partition, see the next section. Common file system installations: The following instructions are common to installations from local disk partitions, NFS mounted directories and CD-ROMs. A list of available distribution sets will be listed. 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 "base29", "etc29", and "bsd" distribution sets. Congratulations, you have successfully installed OpenBSD 2.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. You should have got a mail from the install program we recommend you to read, it contains answers to basic questions you might have about OpenBSD (like setting up your system, installing packages, getting more information about OpenBSD, sending in your dmesg output and more). This you can do by running mail and then just enter "1" to get the first message. You quit mail by entering "q". Some of the files in the OpenBSD 2.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: ------------------------------------------------ NOTE! If you are going to do the upgrade manually, you MUST use the "-r" flag when invoking disklabel(8). You MUST also change the partition table such that partition 'c' encompasses the entire drive, and not only the OpenBSD partition. Finally, partition 'd' is no longer special and can be used for any purpose whatsoever. Also, OpenBSD now uses partition ID 0xA6 (166 decimal), but will continue to work with 0xA5 for compatibility reasons. However, if you change the partition ID to 0xA6, you will be able to share the disk with 386BSD, FreeBSD or NetBSD. Note that the latter three can NOT easily share the disk with each other. To do the upgrade, you must have the floppy29.fs floppy image on a disk. You must also have at least the "base29" and "bsd" binary distribution set available, so that you can upgrade with it, using one of the upgrade methods described above. Finally, you must have sufficient disk space available to install the new binaries. Since the old binaries are being overwritten in place, you only need space for the new binaries, which weren't previously on the system. If you have a few megabytes free on each of your root and /usr partitions, you should have enough space. Since upgrading involves replacing the boot blocks on your OpenBSD partition, the kernel, and most of the system binaries, it has the potential to cause data loss. You are strongly advised to BACK UP ANY IMPORTANT DATA ON YOUR DISK, whether on the OpenBSD partition or on another operating system's partition, before beginning the upgrade process. To upgrade your system, follow the following instructions: Boot your machine using of the floppy29.fs floppy. When presented with the boot prompt (the "boot>" prompt), hit return. While booting, you will probably see several warnings. You should be warned that no swap space is present. Do not be alarmed, these are completely normal. When you reach the prompt asking you for a shell name, just hit return. You will be presented with a welcome message and a prompt. If you are upgrading from a pre-OpenBSD 1.0 release, you should upgrade your file systems manually now, using "fsck -c 2". Read the fsck(8) manual page for more details. Now you will be asked whether you wish to do an "install" or an "upgrade". Enter 'u' to upgrade your existing installation. You will be presented with some information about the upgrade process and a warning message, and will be asked if you wish to proceed with the upgrade process. If you answer negatively, the upgrade process will stop, and your disk will not be modified. If you answer affirmatively, the upgrade process will begin, and your disk will be modified. You may hit Control-C to stop the upgrade process at any time. However, if you hit it at an inopportune moment, your system may be left in an inconsistent (and possibly unusable) state. You will be asked which terminal type to use, you should just hit return to select the default (pcvt25). The upgrade program will then tell you which disks of that type it can upgrade, and ask you which it should use. The name of the disk is typically "wd0" for IDE/RLL/ESDI/ST506 drives or "sd0" for SCSI drives. Reply with the name of your disk. The upgrade program will then ask you for the partition which contains the root file system and proceed with checking it. It will then mount your root file system on /mnt. After all your root file system has been mounted, the upgrade program will ask you if you want to enable the network. If you answer affirmatively, the configuration stored on the root file system will be used. After this you will be given the opportunity to escape to the command shell to do any additional network configuration. This may include adding or altering routes, if needed. At the next point you can edit the fstab, which is used for the upgrade process. You may need to resolve dependencies in the order in which the file systems are mounted. All partitions will be checked and mounted under /mnt. In other words, your root partition will be mounted on /mnt, your /usr partition on /mnt/usr, etc. You will be asked if the upgrade sets are already on the mounted file systems. If you answer with yes, you can type in the path where the sets are stored. The upgrade then continues with the procedure described in the paragraph "Common file system installations" in the install section of this document. If you don't already have the OpenBSD distribution sets on your disk, look at the installation section of this document for information on how to go on. Your options are to install via FTP, via HTTP, via nfs, from tape, from CD-ROM or, again, from local disk. But remember to not install the "etc29" distribution file! Your system has now been upgraded to OpenBSD 2.9. After rebooting your machine is a complete OpenBSD 2.9 system. However, that doesn't mean that you're finished with the upgrade process. There are several things that you should do, or might have to do, to insure that the system works properly. First, you will probably want to get the etc29 distribution, extract it to a temporary location, and compare its contents with those in your /etc/ directory. You will probably want to replace some of your system configuration files, or incorporate some of the changes in the new versions into yours. Second, you will probably want to update the set of device nodes you have in /dev. If you've changed the contents of /dev by hand, you will need to be careful about this. A "MAKEDEV all" was already run during the upgrade procedure, so you will have to take care about those devices, that are not remade by "MAKEDEV all". Third, you must deal with certain changes in the formats of some of the configuration files. The most notable change is that the "options" given to many of the file systems in /etc/fstab or by hand have changed, and some of the file systems have changed names. *IMPORTANT*: ANY INSTANCES OF "ufs" IN /etc/fstab ARE CHANGED TO "ffs" BY THE UPGRADE PROGRAM. To find out what the new options are, it's suggested that you read the manual page for the file systems' mount commands, for example mount_nfs(8) for NFS. (Note that the information for mounts of type "ffs", i.e. Fast File Systems, are contained in the mount(8) man page.) Finally, you will want to delete old binaries that were part of the version of OpenBSD that you upgraded from and have since been removed from the OpenBSD distribution. If you are upgrading from a pre-1.0 OpenBSD, you might also want to recompile any locally-built binaries, to take advantage of the shared libraries. (Note that any new binaries that you build will be dynamically linked, and therefore take advantage of the shared libraries, by default. For information on how to make statically linked binaries, see the cc(1) and ld(1) manual pages.) Getting source code for your OpenBSD System: -------------------------------------------- Now that your OpenBSD system is up and running, you probably want to get access to source code so that you can recompile pieces of the system. A few methods are provided. If you have an OpenBSD CD, the source code is provided. Otherwise, you can get the pieces over the Internet using ANONCVS, CTM or FTP. For more information, see http://www.openbsd.org/anoncvs.html http://www.openbsd.org/ctm.html http://www.openbsd.org/ftp.html Using online OpenBSD documentation: ----------------------------------- Documentation is available if you first install the manual distribution set. Traditionally, the UN*X "man pages" (documentation) are denoted by 'name(section)'. Some examples of this are intro(1), man(1), apropos(1), passwd(1), and passwd(5). The section numbers group the topics into several categories, but three are of primary interest: user commands are in section 1, file formats are in section 5, and administrative information is in section 8. The 'man' command is used to view the documentation on a topic, and is started by entering 'man [section] topic'. The brackets [] around the section should not be entered, but rather indicate that the section is optional. If you don't ask for a particular section, the topic with the least-numbered section name will be displayed. For instance, after logging in, enter man passwd to read the documentation for passwd(1). To view the documentation for passwd(5), enter man 5 passwd instead. If you are unsure of what man page you are looking for, enter apropos subject-word where "subject-word" is your topic of interest; a list of possibly related man pages will be displayed. 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 you already have several popular ``packages'', and the ``ports'' collection. Instructions for installing applications from the various sources using the different installation methods follow. If emacs is to be installed it should be installed first as it creates the ``info'' directory file that may be modified by other applications. 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 2.9/packages/i386 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: # mkdir -p /cdrom # mount /dev/cd0a /cdrom # pkg_add /cdrom/2.9/packages/i386/ # # umount /cdrom Package names are usually the application name and version with .tgz appended, e.g. emacs-20.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/2.9/packages/i386/ 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: # pkg_add ftp://ftp.openbsd.org/pub/OpenBSD/2.9/packages/i386/emacs-20.3.tgz Packages available include (at least): ImageMagick-4.2.0.tgz m4-1.4.tgz Xaw3d-1.3.tgz mm-2.7.tgz aalib-1.2.tgz mpeg_lib-1.2.1.tgz afm-1.0.tgz mpeg_play-2.4.tgz autoconf-2.13.tgz netpbm-19940301.tgz bash-2.03.tgz netpipes-4.1.1-export.tgz bison-1.25.tgz nmh-1.0.tgz bzip2-0.9.0c.tgz pgp-2.6.3-intl.tgz compface-1.0.tgz pgp-2.6.3-usa.tgz cucipop-1.31.tgz pine-4.10.tgz dejagnu-1.3.tgz png-1.0.3.tgz egcs-1.1.2.tgz psutils-1.17-a4.tgz emacs-20.3.tgz psutils-1.17-letter.tgz enscript-1.6.1.tgz screen-3.7.6.tgz ethereal-0.5.1.tgz sharutils-4.2.tgz expect-5.28.tgz sniffit-0.3.5.tgz fetchmail-4.7.9.tgz freetype-1.2.tgz gettext-0.10.35.tgz tar-1.12.tgz ghostscript-5.10.tgz tcl-8.0.5.tgz gimp-1.1.4.tgz tcsh-6.08.00.tgz glib-1.2.1.tgz teTeX-0.4.tgz glimpse-4.1.tgz tiff-3.4.tgz gmake-3.77.tgz tk-8.0.5.tgz gnuplot-3.7.tgz transfig-3.2.1.tgz gtk+-1.2.1.tgz unzip-5.40.tgz gv-3.5.8.tgz viewfax-2.3.tgz id-utils-3.2.tgz wget-1.5.3.tgz idled-1.16.tgz xcolors-1.3.tgz iozone-2.01.tgz xfig-3.2.2.tgz ircii-2.8.2-epic3.004.tgz xntp3-5.93e-export.tgz ispell-3.1.20.tgz xpaint-2.5.5.tgz jove-4.16.tgz xpdf-0.80.tgz jpeg-6b.tgz xphoon-91.9.18.tgz lesstif-0.88.0.tgz xspread-2.1.tgz libslang-1.2.2.tgz xv-3.10a.tgz Note: these packages may not exist for all architectures; other packages may be added. Some packages are only available via ftp. 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 README.ports on CD-ROM 2 to see how to copy or mount the ports directory. 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 luck there you may try the FreeBSD ports or NetBSD package collection. If you are on an i386 based machine it is quite possible that the FreeBSD port, if one exists, will work for you. 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 . 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.