INSTALLATION NOTES for OpenBSD/hppa 4.4 What is OpenBSD? ---------------- OpenBSD is a fully functional, multi-platform UN*X-like Operating System based on Berkeley Networking Release 2 (Net/2) and 4.4BSD-Lite. There are several operating systems in this family, but OpenBSD differentiates itself by putting security and correctness first. The OpenBSD team strives to achieve what is called a 'secure by default' status. This means that an OpenBSD user should feel safe that their newly installed machine will not be compromised. This 'secure by default' goal is achieved by taking a proactive stance on security. Since security flaws are essentially mistakes in design or implement- ation, the OpenBSD team puts as much importance on finding and fixing existing design flaws and implementation bugs as it does writing new code. This means that an OpenBSD system will not only be more secure, but it will be more stable. The source code for all critical system components has been checked for remote-access, local-access, denial- of-service, data destruction, and information-gathering problems. In addition to bug fixing, OpenBSD has integrated strong cryptography into the base system. A fully functional IPsec implementation is provided as well as support for common protocols such as SSL and SSH. Network filtering and monitoring tools such as packet filtering, NAT, and bridging are also standard, as well as several routing services, such as BGP and OSPF. For high performance demands, support for hardware cryptography has also been added to the base system. Because security is often seen as a tradeoff with usability, OpenBSD provides as many security options as possible to allow the user to enjoy secure computing without feeling burdened by it. To integrate more smoothly in other environments, OpenBSD 4.4 also provides, on some platforms, several binary emulation subsystems (which includes iBCS2, Linux, OSF/1, SunOS, SVR4, Solaris, and Ultrix compatibility), aiming at making the emulation as accurate as possible so that it is transparent to the user. Because OpenBSD is from Canada, the export of Cryptography pieces (such as OpenSSH, IPsec, and Kerberos) to the world is not restricted. (NOTE: OpenBSD can not be re-exported from the US once it has entered the US. Because of this, take care NOT to get the distribution from an FTP server in the US if you are outside of Canada and the US.) A comprehensive list of the improvements brought by the 4.4 release is available on the web at http://www.OpenBSD.org/44.html. OpenBSD/hppa 4.4 runs on the HP 9000/700 series of workstations, based on 32 bit PA-RISC processors. Most letter-named models are also supported, including many 64 bit PA-RISC 2.0-based models (running in 32 bit mode). Sources of OpenBSD: ------------------- This is a list of currently known FTP servers at the time of the 4.4 release. For a more recent list, please refer to http://www.OpenBSD.org/ftp.html Main server in Canada: ftp://ftp.OpenBSD.org/pub/OpenBSD (Alberta) 2nd level mirrors: ftp://spargel.kd85.com/pub/OpenBSD (Vienna) ftp://openbsd.informatik.uni-erlangen.de/pub/OpenBSD (Erlangen) ftp://ftp.stacken.kth.se/pub/OpenBSD (Stockholm) ftp://ftp5.usa.openbsd.org/pub/OpenBSD (Redwood City, CA) ftp://ftp3.usa.openbsd.org/pub/OpenBSD (Boulder, CO) ftp://rt.fm/pub/OpenBSD (Lake in the Hills, IL) Argentina: ftp://ftp.openbsd.md5.com.ar/pub/OpenBSD (Buenos Aires) Australia: ftp://ftp.it.net.au/mirrors/OpenBSD (Perth) Austria: ftp://playboy.wu-wien.ac.at/pub/OpenBSD (Vienna) Belgium: ftp://ftp.scarlet.be/pub/openbsd (Brussels) ftp://ftp.belnet.be/packages/openbsd (Brussels) Brazil: ftp://ftp.das.ufsc.br/pub/OpenBSD (Florianopolis, Santa Catarina) Bulgaria: ftp://ftp.bg.openbsd.org/pub/OpenBSD (Plovdiv) Canada: ftp://mirror.arcticnetwork.ca/pub/OpenBSD (Calgary) ftp://ftp.ca.openbsd.org/pub/OpenBSD (Edmonton) ftp://gulus.usherbrooke.ca/pub/distro/OpenBSD (Quebec) China: ftp://ftp.freebsdchina.org/pub/OpenBSD (Shanghai) Denmark: ftp://mirrors.dotsrc.org/openbsd (Aalborg) ftp://ftp.dkuug.dk/pub/OpenBSD (Copenhagen) Estonia: ftp://ftp.aso.ee/pub/OpenBSD (Tallinn) Finland: ftp://mirrors.nic.funet.fi/pub/OpenBSD (Espoo) ftp://ftp.jyu.fi/pub/OpenBSD (Jyvaskyla) France: ftp://ftp.arcane-networks.fr/pub/OpenBSD (Paris) ftp://ftp.crans.org/pub/OpenBSD (Paris) ftp://ftp.irisa.fr/pub/OpenBSD (Rennes) Germany: ftp://openbsd.ftp.fu-berlin.de/pub/OpenBSD (Berlin) ftp://ftp.spline.de/pub/OpenBSD (Berlin) ftp://ftp.freenet.de/pub/ftp.openbsd.org/pub/OpenBSD (Duesseldorf) ftp://ftp-stud.fht-esslingen.de/pub/OpenBSD (Esslingen) ftp://mirror.roothell.org/pub/OpenBSD (Nuremberg) ftp://ftp.bytemine.net/pub/OpenBSD (Oldenburg) Greece: ftp://filoktitis.noc.uoa.gr/pub/OpenBSD (Athens) ftp://ftp.physics.auth.gr/pub/mirrors/OpenBSD/OpenBSD (Thessaloniki) ftp://ftp.duth.gr/pub/OpenBSD (Thrace) ftp://ftp.cc.uoc.gr/mirrors/OpenBSD (Heraklion) Hungary: ftp://ftp.fsn.hu/pub/OpenBSD (Budapest) Ireland: ftp://ftp.esat.net/pub/OpenBSD (Dublin) ftp://ftp.heanet.ie/pub/OpenBSD (Dublin) Israel: ftp://mirror.inter.net.il/pub/OpenBSD (Petach Tiqwa) Italy: ftp://ftp.unina.it/pub/OpenBSD (Napoli) Japan: ftp://ftp.jaist.ac.jp/pub/OpenBSD (Ishikawa) ftp://ftp.nara.wide.ad.jp/pub/OpenBSD (Nara) ftp://ftp.jp.openbsd.org/pub/OpenBSD (Tokyo) ftp://ftp.kddlabs.co.jp/OpenBSD (Tokyo) Korea: ftp://ftp.kaist.ac.kr/pub/OpenBSD (Daejeon) Latvia: ftp://ftp.secure.lv/pub/OpenBSD (Riga) ftp://ftp.bsd.lv/pub/OpenBSD (Riga) The Netherlands: ftp://ftp.calyx.nl/pub/OpenBSD (Amsterdam) ftp://ftp.nluug.nl/pub/OpenBSD (Utrecht) ftp://mirror.hostfuss.com/pub/OpenBSD (Amsterdam) Norway: ftp://ftp.inet.no/pub/OpenBSD (Oslo) ftp://ftp.uninett.no/pub/OpenBSD (Oslo) ftp://jane.tihlde.org/pub/OpenBSD (Trondheim) Poland: ftp://ftp.task.gda.pl/pub/OpenBSD (Gdansk) Portugal: ftp://ftp.fmed.uc.pt/pub/OpenBSD (Coimbra) Russia: ftp://ftp.chg.ru/pub/OpenBSD (Chernogolovka-Moscow) ftp://ftp.gamma.ru/pub/OpenBSD (Moscow) Slovenia: ftp://ftp.obsd.si/pub/OpenBSD (Ljubljana) Spain: ftp://ftp.rediris.es/mirror/OpenBSD (Madrid) ftp://ftp.udc.es/pub/OpenBSD (A Coruna) Sweden: ftp://ftp.su.se/pub/OpenBSD (Stockholm) ftp://ftp.btradianz.se/pub/OpenBSD (Stockholm) Switzerland: ftp://mirror.switch.ch/pub/OpenBSD (Zurich) Turkey: ftp://ftp.enderunix.org/pub/OpenBSD (Istanbul) Ukraine: ftp://gaia.colocall.net/pub/OpenBSD (Kiev) United Kingdom: ftp://ftp.public-internet.co.uk/pub/OpenBSD (London) ftp://ftp.mirrorservice.org/pub/OpenBSD (Kent) USA: ftp://mirror.planetunix.net/pub/OpenBSD (Chicago, IL) ftp://osmirrors.cerias.purdue.edu/pub/OpenBSD (West Lafayette, IN) ftp://mirror.iawnet.sandia.gov/pub/OpenBSD (Albuquerque, NM) ftp://ftp.cse.buffalo.edu/pub/OpenBSD (Buffalo, NY) ftp://mirrors.24-7-solutions.net/pub/OpenBSD (New York, NY) ftp://openbsd.mirrors.pair.com (Pittsburgh, PA) ftp://carroll.cac.psu.edu/pub/OpenBSD (PA) ftp://openbsd.mirrors.tds.net/pub/OpenBSD (Madison, WI) Additionally, the file ftp://ftp.OpenBSD.org/pub/OpenBSD/ftplist contains a list which is continually updated. If you wish to become a distribution site for OpenBSD, contact . OpenBSD 4.4 Release Contents: ----------------------------- The OpenBSD 4.4 release is organized in the following way. In the .../4.4 directory, for each of the architectures having an OpenBSD 4.4 binary distribution, there is a sub-directory. The hppa-specific portion of the OpenBSD 4.4 release is found in the "hppa" subdirectory of the distribution. That subdirectory is laid out as follows: .../4.4/hppa/ INSTALL.hppa Installation notes; this file. MD5 Output of the md5(1) program, usable for verification of the correctness of downloaded files. *.tgz hppa binary distribution sets; see below. bsd A stock GENERIC hppa 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. install44.iso The hppa boot and installation CD-ROM image, which contains the base and X sets, so that install or upgrade can be done without network connectivity. cd44.iso A miniroot filesystem image suitable to be used as a bootable CD-ROM image, but will require the base and X sets be found via another media or network; otherwise similar to the bsd.rd image above. lif44.fs A LIF bootable miniroot image, suitable for network boot. xxboot The OpenBSD/hppa LIF boot block. The OpenBSD/hppa binary distribution sets contain the binaries which comprise the OpenBSD 4.4 release for hppa systems. There are eleven binary distribution sets. The binary distribution sets can be found in the "hppa" subdirectory of the OpenBSD 4.4 distribution tree, and are as follows: base44 The OpenBSD/hppa 4.4 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. [ 44.4 MB gzipped, 118.6 MB uncompressed ] comp44 The OpenBSD/hppa Compiler tools. All of the tools relating to C, C++, Objective-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. [ 65.6 MB gzipped, 234.6 MB uncompressed ] etc44 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.) [ 630.1 KB gzipped, 1.9 MB uncompressed ] game44 This set includes the games and their manual pages. [ 2.6 MB gzipped, 5.8 MB uncompressed ] man44 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.3 MB gzipped, 26.6 MB uncompressed ] misc44 This set includes the system dictionaries (which are rather large), and the typesettable document set. [ 2.7 MB gzipped, 9.4 MB uncompressed ] xbase44 This set includes the base X distribution. This includes programs, headers and libraries. [ 11.0 MB gzipped, 30.9 MB uncompressed ] xetc44 This set includes the X window system configuration files that reside in /etc. It's the equivalent of etc44 for X. [ 76.3 KB gzipped, 286.3 KB uncompressed ] xfont44 This set includes all of the X fonts. [ 33.9 MB gzipped, 41.7 MB uncompressed ] xserv44 This set includes all of the X servers. [ 3.6 MB gzipped, 9.2 MB uncompressed ] xshare44 This set includes all text files equivalent between all architectures. [ 2.6 MB gzipped, 13.9 MB uncompressed ] OpenBSD System Requirements and Supported Devices: -------------------------------------------------- OpenBSD/hppa 4.4 runs on the following classes of HP9000 machines: - PA7100-based 715/33, 715/50, 715/75 725/50, 725/75 735/100, 755/100 742i, 745i, 747i - PA7100LC-based 712 715/64, 715/80, 715/100, 715/100XC 725/64, 725/100 743i, 748i Saic Galaxy 1100 - PA7150-based 735/125, 755/125 - PA7200-based J200, J210, J210XC C100, C110 - PA7300LC-based A180, A180C B132L, B132L+, B160L, B180L+, C132L, C160L 744, 745, 748 RDI PrecisionBook - PA8000-based (in 32-bit mode): C160, C180 - PA8200-based (in 32-bit mode): C200, C230, C240, J2240 - PA8500-based (in 32-bit mode): B1000, B2000, C360, C3000, J5000, J7000 - PA8600-based (in 32-bit mode): B2600, C3600, J5600, J6000, J7600 - PA8700-based (in 32-bit mode): C3650, C3700, C3750, J6700, J6750 A minimum of 16MB of RAM is required. Supported devices include: - Ethernet Controllers built-in Intel 82596 (ie) Intel/DEC 21443 "Tulip" clones (dc) Novell NE1000, NE2000 (not bootable) Intel i8255x-based (fxp) (not bootable), 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 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 Broadcom BCM570x (Tigon3) based PCI adapters, including: 3Com 3c996-T 3Com 3c996-SX 3Com 3c996B-T HP ProLiant NC7770 PCI-X Gigabit NIC Netgear GA302T SysKonnect SK-9D21 SysKonnect SK-9D41 Realtek 8129/8139 based PCI Ethernet adapters (rl), including: Accton MPX 5030/5038 Allied Telesyn AT2550 Corega FEther CB-TXD 10/100 Ethernet D-Link DFE530TX+, DFE538TX Encore ENL832-TX-RENT 10/100 M PCI Genius GF100TXR KTX-9130TX 10/100 Fast Ethernet Longshine LCS-8038TX-R NDC NE100TX-E Netgear FA311 v2 Netronix EA-1210 Net Ether 10/100 Nortel BayStack 21 OvisLink LEF-8129TX, LEF-8139TX SMC EZ Card 10/100 PCI 1211-TX TRENDnet TE100-PCBUSR CardBus SysKonnect and Marvell based adapters (not bootable), including: SysKonnect SK-9821 (1000baseT) SysKonnect SK-9822 (dual 1000baseT) SysKonnect SK-9841 (1000baseLX) SysKonnect SK-9842 (dual 1000baseLX) SysKonnect SK-9843 (1000baseSX) SysKonnect SK-9844 (dual 1000baseSX) SysKonnect SK-9521 v2.0 (1000baseT 32-bit) SysKonnect SK-9821 v2.0 (1000baseT) SysKonnect SK-9843 v2.0 (1000baseSX) 3Com 3c940 (1000baseT) D-Link DGE-530T (1000baseT) Linksys EG1032v2 (1000baseT) Linksys EG1064v2 (1000baseT) SMC 9452TX (1000baseT) - SCSI controllers built-in 53C700 SCSI (oosiop) built-in 53C710 SCSI (osiop) 53C720/53C8xx-based SCSI (siop) 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) (not bootable), including: 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 - SGC/GSC graphics Artist (as found on 712) (sti) CRX-8, CRX-24, HCRX-8, HCRX-24 (sti) - RS-232 devices on-board NS16550 or similar serial ports (com) - Parallel ports on-board parallel port (lpt) - Audio devices Harmony CS4215/AD1849 LASI audio (harmony) - Input devices PS/2 keyboard (pckbd) and mouse (pms) HIL keyboard (hilkbd), mouse and tablets (hilms) - Wireless Ethernet Adapters Aironet Communications 4500/4800 IEEE 802.11FH/b PCMCIA adapters Aironet 4500/4800 Cisco 340/350 Atmel AT76C50x IEEE 802.11b USB 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) Atmel AT76C503 (Intersil Radio) Atmel AT76C503 (RFMD Radio) Atmel AT76C505 (RFMD Radio) Atmel AT76C505 (RFMD 2958 Radio) Atmel AT76C505A (RFMD 2958 Radio) Atmel AT76C505AS (RFMD 2958 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 802.11b Linksys WUSB11 802.11b v2.8 MSI WLAN Netgear MA101 Netgear MA101 rev B OQO model 01 WiFi Ovislink AirLive WL-1120USB OvisLink AirLive WL-1130USB Planex Communications GW-US11S Samsung SWL2100W Siemens WLL013 SMC EZ Connect 11Mbps (SMC2662w) SMC EZ Connect 11Mbps v2 (SMC2662wV2) Tekram U-300C TRENDnet TEW-229UB W-Buddie WN210 Z-Com M4Y-750 Ralink Technology IEEE 802.11b/g USB 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 Nintendo Wi-Fi USB Connector Nova Tech NV-902W OvisLink Evo-W54USB SerComm UB801R SparkLAN WL-685R Sphairon UB801R Surecom EP-9001-g rev 3A Sweex LC100060 Tonze UW-6200C Zaapa ZNWUSB-54 Zinwell ZPlus-G250 Zinwell ZWX-G261 Zonet ZEW2500 Ralink Technology USB IEEE 802.11a/b/g USB adapters 3Com Aolynk WUB320g Abocom WUG2700 Airlink101 AWLL5025 ASUS WL-167g ver 2 Atlantis Land A02-UP1-W54 Belkin F5D7050 ver 3 Belkin F5D9050 ver 3 Buffalo WLI-U2-SG54HP Buffalo WLI-U2-G54HP CNet CWD-854 ver F Conceptronic C54RU ver 2 Corega CG-WLUSB2GL Corega CG-WLUSB2GO Corega CG-WLUSB2GPX D-Link DWL-G122 rev C1 D-Link WUA-1340 Digitus DN-7003GR Edimax EW-7318USG Gigabyte GN-WB01GS Gigabyte GN-WI05GS Hawking HWUG1 Hawking HWU54DM Hercules HWGUSB2-54-LB Hercules HWGUSB2-54V2-AP LevelOne WNC-0301USB v3 Linksys WUSB54G rev C Linksys WUSB54GR Planex GW-US54HP Planex GW-US54Mini2 Planex GW-USMM Senao NUB-3701 Sitecom WL-113 ver 2 Sitecom WL-172 Sweex LW053 TP-LINK TL-WN321G WaveLAN/IEEE, PRISM 2-3, and Spectrum24 IEEE 802.11b Compact Flash adapters (will be detected as PCMCIA adapters) AmbiCom WL1100C-CF ASUS SpaceLink WL-110 Belkin F5D6060 (version 1 only) Buffalo AirStation D-Link DCF-660W ELSA XI800 Linksys WCF12 Netgear MA701 Pretec Compact WLAN OC-WLBXX-A Senao NL-2511CF WaveLAN/IEEE, PRISM 2-3, and Spectrum24 IEEE 802.11b PCMCIA adapters 3Com AirConnect 3CRWE737A Actiontec HWC01170 Adaptec AWN-8030 Addtron AWP-100 Agere ORiNOCO ARtem Onair ASUS SpaceLink WL-100 Belkin F5D6020 (version 1 only) Buffalo AirStation Cabletron RoamAbout Compaq Agency NC5004 Contec FLEXLAN/FX-DS110-PCC Corega PCC-11 Corega PCCA-11 Corega PCCB-11 D-Link DWL-650 (rev A1-J3 only) ELSA XI300 ELSA XI325 ELSA XI325H EMTAC A2424i Ericsson Wireless LAN CARD C11 Gemtek WL-311 Hawking Technology WE110P I-O DATA WN-B11/PCM Intel PRO/Wireless 2011 Intersil Prism II Linksys Instant Wireless WPC11 Linksys Instant Wireless WPC11 2.5 Linksys Instant Wireless WPC11 3.0 Lucent WaveLAN Microsoft MN520 NANOSPEED ROOT-RZ2000 NEC CMZ-RT-WP Netgear MA401 Netgear MA401RA Nokia C020 Wireless LAN Nokia C110/C111 Wireless LAN NTT-ME 11Mbps Wireless LAN Planex GW-NS11H Proxim Harmony Proxim RangeLAN-DS Samsung MagicLAN SWL-2000N Siemens SpeedStream SS1021 SMC 2632 EZ Connect Symbol Spectrum24 TDK LAK-CD011WL US Robotics 2410 US Robotics 2445 WaveLAN/IEEE, PRISM 2-3, and Spectrum24 IEEE 802.11b USB 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 only) 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 - PC Cards (PCMCIA and CardBus) ATA cards, including: ATA/IDE card drives ATA/IDE CD-ROM adapters CF/ATA flash cards and disk drives Ethernet adapters, including: NE2000-based, including: Accton EN2212, EN2216 Allied Telesis LA-PCM AmbiCom AMB8002T Arowana FE Belkin F5D5020 Billionton Systems LNT-10TN CNet NE2000 Compex Linkport ENET-B Corega PCC-T, PCC-TD, EtherII PCC-T, Corega FastEther PCC-T, FastEther PCC-TX Corega FastEther PCC-TXD, FastEther PCC-TXF D-Link DE-650, DE-660, DE-660+, DFE-670TXD Dayna CommuniCard E Digital DEPCM-XX Dual NE2000 Edimax NE2000 Genius ME 3000II SE Grey Cell GCS2000 Gold II GVC NIC-2000p, NP0335 Hawking PN650TX I-O DATA PCLA, PCLA/TE IC-Card Kingston KNE-PC2 Linksys PCMPC100, EC2T Combo, EthernetCard Linksys Combo EthernetCard, Trust Combo EthernetCard Linksys Etherfast 10/100 MACNICA ME1 for JEIDA Melco LPC3-TX National Semiconductor InfoMover NDC Instant-Link Netgear FA410TX, FA410TXC, FA411 Network Everywhere NP10T New Media LiveWire 10/100 Planet SmartCom 2000 Planex FNW-3600-T, FNW-3700-T Premax PE-200 RPTI EP-400, EP-401 Seiko Epson EN10B SMC EZCard, 8041 Socket Communications LP-CF, LP-E SVEC PN650TX, ComboCard, LANCard Synergy S21810 Tamarack NE2000 Telecom Device TCD-HPC100 Wisecom T210CT, iPort Xircom CFE-10 - Universal Serial Bus (USB) Devices USB Generic Human Interface Devices (catch-all) USB Hubs USB Keyboards USB Mass Storage devices, i.e., USB floppy drives and USB memory stick controllers USB Mice - Miscellaneous devices: battery-backed real time clock ``soft'' power button as available on some models (power) LCD display available on some models (lcd) If your hardware is not listed above, there is currently no support for it in this release. Getting the OpenBSD System onto Useful Media: --------------------------------------------- Installation is supported from several media types, including: CD-ROM FFS partitions (for upgrades only) 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. Creating an (optionally bootable) installation tape: To install OpenBSD from a tape, 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 if test $# -lt 1 then dd of=${TAPE} if=lif44.fs obs=2k conv=sync fi for file in base etc comp game man misc xbase xetc xfont xserv xshare do dd if=${file}44.tgz of=${TAPE} obs=8k conv=sync done tar cf ${TAPE} bsd mt -f ${TAPE} offline # end of script And then: cd .../4.4/hppa sh -x /tmp/maketape Note that, by default, this script creates a bootable tape. If you only want to fetch the OpenBSD files from tape, but want to boot from another device, you can save time and space creating the tape this way: cd .../4.4/hppa sh -x /tmp/maketape noboot 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 "base44" set somewhere in your file system. It is recommended that you upgrade the other sets, as well. Preparing your System for OpenBSD Installation: ----------------------------------------------- The hppa computers do not generally need any specific preparation. You might want to check that the console ``path'' in the PDC firmware points to the device you plan to use, and change it if necessary. Most hppa machines will allow to select console path from the BOOT_ADMIN> prompt. To reach this prompt, abort the autoboot process and if a menu appears, enter ``a'' to select the "Boot Administration mode." To select the first serial port as console, type: BOOT_ADMIN> path console rs232_a.9600.8.none or to select graphics as console: BOOT_ADMIN> path console graphics BOOT_ADMIN> path keyboard hil or BOOT_ADMIN> path console graphics BOOT_ADMIN> path keyboard ps2 depending upon your keyboard type. On a few models, such as the 9000/712, the PDC firmware will not allow the console path to be changed. In this case, it is possible to change it from the OpenBSD boot loader. After booting OpenBSD in interactive mode (for example, if booting over the network, by entering ``boot lan isl''), enter the following at the ``boot>'' prompt: boot> machine console rs232.9600.8.none WARNING! Make sure to type the console path correctly or the 9000/712 can become unusable, and will require a special ``dagger'' board to be revived. After changing the console path, the machine has to be power cycled for the changes to take effect. In most cases the primary boot device path is already set to the right value. If not, it is advised to run: BOOT_ADMIN> search to display the list of all bootable devices before choosing one with: BOOT_ADMIN> path primary SCSI.TARGET.LUN Substitute FWSCSI or SESCSI for SCSI if it is displayed as such in the path list obtained from ``seacch'', and use the TARGET and LUN values matching the device intended as the boot device. Please refer to the boot(8) manual page for more information on PDC settings and boot commands. 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. Bootstrapping the installation ramdisk kernel is supported from either network, tape or CD-ROM. Booting from Tape or CD-ROM installation media: You can burn a bootable CD-ROM and boot from it or you can prepare an installation tape as described in the "Creating an installation tape" section earlier. To boot from SCSI CD-ROM, simply insert the CD into the drive before power up, then during the computer's self-test cycle, press the space bar. Subsequently at the PROM prompt issue a command: BOOT_ADMIN> search to initiate a search for all bootable devices available. This procedure may take a few minutes and should you have configured network boot services present may find those too. A sample output might be: Path Number Device Path Device Type ----------- ----------------- ----------- P0 SESCSI.2.0 TOSHIBA CD-ROM XM-6201TA P1 LAN.10.0.0.5.3.254 lucifier P2 FWSCSI.5.0 IBM DDRS-34560WS P3 FWSCSI.0.0 SEAGATE ST318436LW P4 SESCSI.6.0 HP HP35480A To boot from your CD-ROM type: BOOT_ADMIN> boot p0 To boot from your tape type: BOOT_ADMIN> boot p4 Booting from Network: In order to bootstrap via the network, you must provide a second system to act as a boot server. It is convenient if this is a second OpenBSD machine as the necessary services are already installed, although source code for such programs as dhcpd can be found in OpenBSD's source tree, and should be reasonably portable to other UN*X-like operating systems. More information on diskless booting can be found in the OpenBSD diskless(8) manual page. Your hppa expects to be able to download a so-called LIF (``Logical Interchange Format'') image, containing both the boot code and the kernel, via the HP rboot protocol, for older firmware, or via the bootp protocol, for more recent firmware. Old firmware operation Models such as 7[035]5, 715/33/50/75, 725/50/75 have an older version of PDC. There are two levels of interactive commands in this version. The first level is a short menu: b) Boot from specified device s) Search for bootable device a) Enter Boot Administration mode x) Exit and continue boot sequence Select from menu: In this case, you will need to setup rbootd on the server. Start by creating an /etc/rbootd.conf file on the bootserver. The format of this file is the ethernet address followed by the LIF filename. Here is an example: 08:00:09:70:c4:11 lif44.fs Then start rbootd (or configure /etc/rc.conf to always start rbootd). Once rbootd is running, the server name will then appear on the hppa as part of the possible boot choices in a boot device search (``s'' command). Modern firmware operation More recent machines mostly those based on the 7100LC, 7200 and 7300LC CPU types have a different PDC version. There is only one interactive mode, with a BOOT_ADMIN> prompt, which provides both boot settings and commands. In this case, you will need to set up dhcpd on the server, which can serve bootp protocol requests. Start by editing the /etc/dhcpd.conf on the bootserver, and declare an information block. Here is an example: subnet 10.0.0.0 netmask 255.0.0.0 { host boron { filename "lif44.fs"; hardware ethernet 08:00:09:70:c4:11; fixed-address 10.42.42.42; } } Do not forget to enable dhcpd. You will also need to enable tftpd, for the hppa to download the miniroot (bf entry) from the server in the /tftpboot (td entry) directory. Common operation You are now ready to bootstrap the miniroot. On your hppa, escape to a prompt and boot from the network by entering ``boot lan isl''. On old PDC firmware, you will need to enter administration mode first. Installing using the netboot procedure: 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 from the installation media as described above. It will take a while to load the miniroot image, especially from a slow network connection or a CD-ROM, 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 media is bad, your diskless setup is incorrect, or you may have a hardware or configuration problem. Once the kernel has loaded, you will be presented with the OpenBSD kernel boot messages. You will want to read them to determine your disks name and geometry. Its name will be something like "sd0". You will also need to know the device name to tell the install tools what disk to install on. If you cannot read the messages as they scroll by, do not worry -- you can get at this information later inside the install program. You will next be asked for your terminal type. If you are installing from a non-serial console, the default of "vt220" is correct. If you are installing from a serial console you should choose the terminal type from amongst those listed. (If your terminal type is xterm, just use 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. Reply with the name of your disk. Next the disk label which defines the layout of the OpenBSD file systems must be set up. The installation script will invoke an interactive editor allowing you to do this. Note that partition 'c' inside this disk label should ALWAYS reflect the entire disk, including any non-OpenBSD portions. If you are labeling a new disk, you will probably start out with an 'a' partition that spans the disk. In this case you should delete 'a' before adding new partitions. The root file system should be in partition 'a', and swap is usually in partition 'b'. It is recommended that you create separate partitions for /usr, /tmp, and /var, and if you have room for it, one for /home. In doing this, remember to skip 'c', leaving it as type "unused". For help in the disk label editor, enter '?' or 'M' to view the manual page (see the info on the ``-E'' flag). Since the target disk will become the boot disk for your new OpenBSD/hppa installation, the disklabel program will restrict the available disk area to keep the first cylinder, which will contain the bootblock, safe from being overwritten. If you don't plan to install a bootblock on this disk, you can reclaim this space with the 'b' command. The swap partition (usually 'b') should have a type of "swap", all other native OpenBSD partitions should have a type of "4.2BSD". The install program will now label your disk and ask which file systems should be created on which partitions. It will auto- matically select the 'a' partition to be the root file system. Next it will ask for which disk and partition you want a file system created on. This will be the same as the disk name (e.g. "sd0") with the letter identifying the partition (e.g. "d") appended (e.g. "sd0d"). Then it will ask where this partition is to be mounted, e.g. /usr. This process will be repeated until you enter "done". At this point you will be asked to confirm that the file system information you have entered is correct, and given an opportunity to change the file system table. Next it will create the new file systems as specified, OVERWRITING ANY EXISTING DATA. This is the point of no return. After all your file systems have been created, the install program will prompt you for the system hostname, and 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. Note that the system hostname should be without the domain part. 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. If you select to configure the network, the install program 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. If the IP address should be obtained from a DHCP server, simply enter ``dhcp'' when asked for the IP address. 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 the DNS domain name to use, as well as the IP address of the primary name server to use. Finally, you will be asked for the IP address of the default route. You will also be presented with an opportunity to edit the host table. At this point you will be asked for the initial root password of the system, twice. Although the install program will only check that the two passwords match, you should make sure to use a strong password. As a minimum, the password should be at least six characters long and a mixture of both lower and uppercase letters, numbers and punctuation characters. 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. Note that installation from floppies is not currently supported. To install via FTP: To begin an FTP install you will need the following pieces of information. Don't be daunted by this list; the defaults are sufficient for most people. 1) Proxy server URL if you are using a URL-based FTP proxy (squid, CERN FTP, Apache 1.2 or higher). You need to define a proxy if you are behind a firewall that blocks outgoing FTP (assuming you have a proxy available to use). 2) Do you need to use active mode FTP? By default, ftp will attempt to use passive mode and fall back to an active connection if the server does not support passive mode. You only need to enable this option if you are connecting to a buggy FTP daemon that implements passive FTP incorrectly. Note that you will not be asked about active FTP if you are using a proxy. 3) The IP address (or hostname if you enabled DNS earlier in the install) of an FTP server carrying the OpenBSD 4.4 distribution. If you don't know, answer ``y'' when asked if you want to see a list of such hosts. 4) The FTP directory holding the distribution sets. The default value of pub/OpenBSD/4.4/hppa is almost always correct. 5) The login and password for the FTP account. You will only be asked for a password for non-anonymous FTP. For instructions on how to complete the installation via FTP, see the section named "Common URL installations" below. To install via HTTP: To begin an HTTP install you will need the following pieces of information: 1) Proxy server URL if you are using a URL-based HTTP proxy (squid, CERN FTP, Apache 1.2 or higher). You need to define a proxy if you are behind a firewall that blocks outgoing HTTP connections (assuming you have a proxy available to use). 2) The IP address (or hostname if you enabled DNS earlier in the install) of an HTTP server carrying the OpenBSD 4.4 distribution. If you don't know, answer ``y'' when asked if you want to see a list of such hosts. 3) The directory holding the distribution sets. There is no standard location for this; You should use the directory specified along with the server in the list of official HTTP mirror sites that you received in step 3. For instructions on how to complete the installation via HTTP, see the section named "Common URL installations" below. To install from tape: In order to install from tape, the distribution sets to be installed must have been written to tape previously, either in tar format or gzip-compressed tar format. You will also have to identify the tape device where the distribution sets are to be extracted from. This will typically be "nrst0" (no-rewind, raw interface). Next you will have to specify how many files have to be skipped on the tape. This number is usually zero. The install program will not automatically detect whether an image has been compressed, so it will ask for that information before starting the extraction. To install from CD-ROM: When installing from a CD-ROM, you will be asked which device holds the distribution sets. This will typically be "cd0". Next you will be asked which partition on the CD-ROM the distribution is to be loaded from. This is normally partition "a". Next you will have to identify the file system type that has been used to create the distribution on the CD-ROM, this can be either FFS or ISO CD9660. The OpenBSD CD-ROM distribution uses the CD9660 format. You will also have to provide the relative path to the directory on the CD-ROM which holds the distribution, for the hppa this is "4.4/hppa". For instructions on how to complete the installation from the CD-ROM distribution, see the section named "Common file system installations" below. To install from an NFS mounted directory: When installing from an NFS-mounted directory, you must have completed network configuration above, and also set up the exported file system on the NFS server in advance. First you must identify the IP address of the NFS server to load the distribution from, and the file system the server expects you to mount. The install program will also ask whether or not TCP should be used for transport (the default is UDP). Note that TCP only works with newer NFS servers. You will also have to provide the relative path to the directory on the file system where the distribution sets are located. Note that this path should not be prefixed with a '/'. For instructions on how to complete the installation from the CD-ROM distribution, see the section named "Common file system installations" below. 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 only install from partitions that have been formatted as the Berkeley fast file system (ffs). 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 have been extracted, you will be asked whether you want to start shhd(8) by default, as well as your ntp server (ntpd(8) will not be started by default if you don't provide a server). The last thing you'll need to configure is the time zone your system will be using. For this work properly, it is expected that you have installed at least the "base44", "etc44", and "bsd" distribution sets. The installer program will the proceed to create all the device nodes needed by the installed system, and will unmount the file systems. Congratulations, you have successfully installed OpenBSD 4.4. When you reboot into OpenBSD, you should log in as "root" at the login prompt. You should create yourself an account and protect it and the "root" account with good passwords. The install program leaves root an initial mail message. We recommend you read it, as it contains answers to basic questions you might have about OpenBSD, such as configuring your system, installing packages, getting more information about OpenBSD, sending in your dmesg output and more. To do this, run mail and then just enter "more 1" to get the first message. You quit mail by entering "q". Some of the files in the OpenBSD 4.4 distribution might need to be tailored for your site. We recommend you run: man afterboot which will tell you about a bunch of the files needing to be reviewed. If you are unfamiliar with UN*X-like system administration, it's recommended that you buy a book that discusses it. Upgrading a previously-installed OpenBSD System: ------------------------------------------------ Warning! Upgrades to OpenBSD 4.4 are currently only supported from the immediately previous release. The upgrade process will also work with older releases, but might not execute some migration tasks that would be necessary for a proper upgrade. The best solution, whenever possible, is to backup your data and reinstall from scratch. To upgrade OpenBSD 4.4 from a previous version, start with the general instructions in the section "Installing OpenBSD". Warning! If you intend to upgrade by booting bsd.rd from the existing OpenBSD system disk, it will be necessary to update your boot blocks first. To do this, replace your existing boot blocks with the xxboot file provided in the OpenBSD/hppa 44 distribution: # cat xxboot > /usr/mdec/xxboot # /sbin/disklabel -B /dev/rsd0c (assuming your system disk is sd0). Do NOT use `cp' to copy the boot blocks, as there are several hard links to /usr/mdec/xxboot which need to be preserved for this operation to succeed. Boot from the LIF image ``lif44.fs'', or a RAMDISK kernel ``bsd.rd''. 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 ``etc44.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 etc44.tgz set in a temporary directory and merge changes by hand, since all components of your system may not function correctly until your files in `/etc' are updated. Getting source code for your OpenBSD System: -------------------------------------------- Now that your OpenBSD system is up and running, you probably want to get access to source code so that you can recompile pieces of the system. A few methods are provided. If you have an OpenBSD CD-ROM, the source code is provided. Otherwise, you can get the pieces over the Internet using anonymous CVS, CTM, CVSync or FTP. For more information, see http://www.OpenBSD.org/anoncvs.html http://www.OpenBSD.org/ctm.html http://www.OpenBSD.org/cvsync.html http://www.OpenBSD.org/ftp.html Using online OpenBSD documentation: ----------------------------------- Documentation is available if you first install the manual pages distribution set. Traditionally, the UN*X "man pages" (documentation) are denoted by 'name(section)'. Some examples of this are intro(1), man(1), apropos(1), passwd(1), passwd(5) and afterboot(8). The section numbers group the topics into several categories, but three are of primary interest: user commands are in section 1, file formats are in section 5, and administrative information is in section 8. The 'man' command is used to view the documentation on a topic, and is started by entering 'man [section] topic'. The brackets [] around the section should not be entered, but rather indicate that the section is optional. If you don't ask for a particular section, the topic with the least-numbered section name will be displayed. For instance, after logging in, enter man passwd to read the documentation for passwd(1). To view the documentation for passwd(5), enter man 5 passwd instead. If you are unsure of what man page you are looking for, enter apropos subject-word where "subject-word" is your topic of interest; a list of possibly related man pages will be displayed. Adding third party software; ``packages'' and ``ports'': -------------------------------------------------------- As complete as your OpenBSD system is, you may want to add any of several excellent third party software applications. There are several ways to do this. You can: 1) Obtain the source code and build the application based upon whatever installation procedures are provided with the application. 2) Use the OpenBSD ``ports'' collection to automatically get any needed source file, apply any required patches, create the application, and install it for you. 3) Use the OpenBSD ``package'' collection to grab a pre-compiled and tested version of the application for your hardware. If you purchased the OpenBSD CD-ROM set you already have several popular ``packages'', and the ``ports'' collection. Instructions for installing applications from the various sources using the different installation methods follow. You should also refer to the packages(7) manual page. Installing applications from the CD-ROM package collection: The OpenBSD CD-ROM ships with several applications pre-built for various hardware architectures. The number of applications vary according to available disk space. Check the directory 4.4/packages/hppa 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/4.4/packages/hppa/ # # umount /cdrom Package names are usually the application name and version with .tgz appended, e.g. emacs-21.3.tgz Installing applications from the ftp.OpenBSD.org package collection: All available packages for your architecture have been placed on ftp.OpenBSD.org in the directory pub/OpenBSD/4.4/packages/hppa/ 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/4.4/packages/hppa/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 if anyone is working on a port -- there may be one in progress. If no such port exists, you might want to look at the FreeBSD ports or NetBSD pkgsrc for inspiration. If you can't find an existing port, try to make your own and feed it back to OpenBSD. That's how our ports collection grows. Some details can be found at http://www.OpenBSD.org/porting.html with more help coming from the mailing list, . 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. More information about the various OpenBSD mailing list and proper netiquette is available at http://www.OpenBSD.org/mail.html To report bugs, use the 'sendbug' command shipped with OpenBSD, and fill in as much information about the problem as you can. Good bug reports include lots of details. Additionally, bug reports can be sent by mail to: bugs@OpenBSD.org 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