INSTALLATION NOTES for OpenBSD/sparc64 3.7 What is OpenBSD? ---------------- OpenBSD is a fully functional, multi-platform UN*X-like Operating System based on Berkeley Networking Release 2 (Net/2) and 4.4BSD-Lite. There are several operating systems in this family, but OpenBSD differentiates itself by putting security and correctness first. The OpenBSD team strives to achieve what is called a 'secure by default' status. This means that an OpenBSD user should feel safe that their newly installed machine will not be compromised. This 'secure by default' goal is achieved by taking a proactive stance on security. Since security flaws are essentially mistakes in design or implement- ation, the OpenBSD team puts as much importance on finding and fixing existing design flaws and implementation bugs as it does writing new code. This means that an OpenBSD system will not only be more secure, but it will be more stable. The source code for all critical system components has been checked for remote-access, local-access, denial- of-service, data destruction, and information-gathering problems. In addition to bug fixing, OpenBSD has integrated strong cryptography into the base system. A fully functional IPsec implementation is provided as well as support for common protocols such as SSL and SSH. Network filtering and monitoring tools such as packet filtering, NAT, and bridging are also standard, as well as several routing services, such as BGP and OSPF. For high performance demands, support for hardware cryptography has also been added to the base system. Because security is often seen as a tradeoff with usability, OpenBSD provides as many security options as possible to allow the user to enjoy secure computing without feeling burdened by it. To integrate more smoothly in other environments, OpenBSD 3.7 also provides, on some platforms, several binary emulation subsystems (which includes iBCS2, Linux, OSF/1, SunOS, SVR4, Solaris, and Ultrix compatibility), aiming at making the emulation as accurate as possible so that it is transparent to the user. Because OpenBSD is from Canada, the export of Cryptography pieces (such as OpenSSH, IPsec, and Kerberos) to the world is not restricted. (NOTE: OpenBSD can not be re-exported from the US once it has entered the US. Because of this, take care NOT to get the distribution from an FTP server in the US if you are outside of Canada and the US.) A comprehensive list of the improvements brought by the 3.7 release is available on the web at http://www.OpenBSD.org/37.html. OpenBSD/sparc64 runs on 64 bit UltraSPARC-based machines, including most of Sun Microsystems workstations and their clones. Sources of OpenBSD: ------------------- This is a list of currently known FTP servers at the time of the 3.7 release. For a more recent list, please refer to http://www.OpenBSD.org/ftp.html Main server in Canada: ftp://ftp.OpenBSD.org/pub/OpenBSD (Alberta) Argentina: ftp://ftp.openbsd.md5.com.ar/pub/OpenBSD (Buenos Aires) Australia: ftp://mirror.aarnet.edu.au/pub/OpenBSD (Canberra, .au only) ftp://ftp.it.net.au/mirrors/OpenBSD (Perth) ftp://ftp.planetmirror.com/pub/OpenBSD (Sydney) ftp://mirror.pacific.net.au/OpenBSD (Sydney) ftp://openbsd.wiretapped.net/pub/OpenBSD (Sydney) Austria: ftp://gd.tuwien.ac.at/opsys/OpenBSD (Vienna) ftp://playboy.wu-wien.ac.at/pub/OpenBSD (Vienna) Belgium: ftp://ftp.scarlet.be/pub/openbsd ftp://ftp.belnet.be/packages/openbsd (Brussels) ftp://openbsd.rug.ac.be/pub/OpenBSD (Ghent) Brazil: ftp://ftp.openbsd.org.br/pub/OpenBSD (Curitiba) ftp://ftp.das.ufsc.br/pub/OpenBSD (Santa Catarina) Bulgaria: ftp://ftp.bg.openbsd.org/pub/OpenBSD (Plovdiv) Canada: ftp://ftp.ca.openbsd.org/pub/OpenBSD (Edmonton) China: ftp://ftp.shellhung.org/pub/OpenBSD (Hong Kong) Czech Republic: ftp://ftp.openbsd.cz/pub/OpenBSD (Prague) Denmark: ftp://sunsite.dk/mirrors/openbsd (Aalborg) Finland: ftp://ftp.fi.debian.org/pub/OpenBSD ftp://ftp.jyu.fi/pub/OpenBSD (Jyvaskyla) France: ftp://ftp.ac-creteil.fr/OpenBSD ftp://ftp.bsdfr.org/pub/OpenBSD (Paris) ftp://ftp.club-internet.fr/pub/OpenBSD (Paris) ftp://ftp.fr.openbsd.org/pub/OpenBSD (Paris) Germany: ftp://ftp.de.openbsd.org/unix/OpenBSD (Berlin) ftp://ftp.tu-clausthal.de/pub/OpenBSD (Clausthal) ftp://ftp.freenet.de/pub/ftp.openbsd.org/pub/OpenBSD (Duesseldorf) ftp://openbsd.informatik.uni-erlangen.de/pub/OpenBSD (Erlangen) ftp://ftp-stud.fht-esslingen.de/pub/OpenBSD (Esslingen) ftp://pandemonium.tiscali.de/pub/OpenBSD (Frankfurt) ftp://openbsd.bay13.net/pub/OpenBSD (Hamburg) ftp://ftp.leo.org/pub/OpenBSD (Muenchen) ftp://ftp.uni-stuttgart.de/pub/OpenBSD (Stuttgart) ftp://ftp.fh-wolfenbuettel.de/pub/os/openbsd (Wolfenbuettel) 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) Hungary: ftp://ftp.fsn.hu/pub/OpenBSD Ireland: ftp://ftp.esat.net/pub/OpenBSD (Dublin) Italy: ftp://ftp.openbsd.it/pub/Unix/OpenBSD (Napoli) ftp://na.mirror.garr.it/mirrors/OpenBSD (Napoli) Japan: ftp://ftp.netlab.is.tsukuba.ac.jp/pub/os/OpenBSD (Ibaraki) ftp://ftp.iij.ad.jp/pub/OpenBSD (Tokyo) ftp://ftp.jp.openbsd.org/pub/OpenBSD (Tokyo) ftp://ftp.kddlabs.co.jp/OpenBSD (Tokyo) Latvia: ftp://ftp.bsd.lv/pub/OpenBSD Lithuania: ftp://ftp.openbsd.lt/pub/OpenBSD The Netherlands: ftp://ftp.nl.uu.net/pub/OpenBSD (Amsterdam) ftp://ftp.calyx.nl/pub/OpenBSD (Amsterdam) ftp://ftp.nluug.nl/pub/OpenBSD (Utrecht) Norway: ftp://ftp.inet.no/pub/OpenBSD (Oslo) ftp://ftp.uninett.no/pub/OpenBSD (Oslo) Poland: ftp://sunsite.icm.edu.pl/pub/OpenBSD ftp://ftp.man.szczecin.pl/pub/BSD/OpenBSD Portugal: ftp://ftp.fmed.uc.pt/pub/OpenBSD Romania: ftp://ftp.physics.uvt.ro/pub/OpenBSD (Timisoara) Russia: ftp://ftp.chg.ru/pub/OpenBSD (Chernogolovka-Moscow) ftp://ftp.gamma.ru/pub/OpenBSD (Moscow) ftp://ftp.radio-msu.net/pub/OpenBSD (Moscow) Saudi Arabia: ftp://ftp.isu.net.sa/pub/mirrors/ftp.openbsd.org/pub/OpenBSD Spain: ftp://ftp.rediris.es/mirror/OpenBSD (Madrid) Sweden: ftp://ftp.stacken.kth.se/pub/OpenBSD (Stockholm) ftp://ftp.sunet.se/pub/OpenBSD (Uppsala) Switzerland: ftp://ftp.solnet.ch/mirror/OpenBSD ftp://ftp.dragonbsd.swiss-anime.ch/pub/OpenBSD (Bern) ftp://sunsite.cnlab-switch.ch/pub/OpenBSD (Zurich) Taiwan: ftp://openbsd.csie.nctu.edu.tw/pub/OpenBSD ftp://openbsd.nsysu.edu.tw/pub/OpenBSD ftp://ftp.tku.edu.tw/pub/OpenBSD (TamSui) Turkey: ftp://ftp.linux.org.tr/pub/OpenBSD Ukraine: ftp://ftp.openbsd.org.ua/pub/OpenBSD (Kiev) United Kingdom: ftp://ftp.plig.org/pub/OpenBSD (London) USA: ftp://ftp5.usa.openbsd.org/pub/OpenBSD (Redwood City, CA) ftp://ftp3.usa.openbsd.org/pub/OpenBSD (Boulder, CO) ftp.lug.udel.edu/pub/OpenBSD (Newark, DE) ftp://reflection.ncsa.uiuc.edu/pub/OpenBSD (Champaign, IL) ftp://mirror.sg.depaul.edu/pub/OpenBSD (Chicago, IL) ftp://rt.fm/pub/OpenBSD (Lake in the Hills, IL) ftp://ftp.groupbsd.org/pub/OpenBSD (Hillsborough, NC) ftp://ftp.cse.buffalo.edu/pub/OpenBSD (Buffalo, NY) ftp://ftp.crimelabs.net/pub/OpenBSD (New York, NY) ftp://openbsd.mirrors.pair.com (Pittsburgh, PA) ftp://carroll.cac.psu.edu/pub/OpenBSD (State College, PA) ftp://mirrors.rcn.net/pub/OpenBSD (Fairfax, VA) ftp://openbsd.secsup.org/pub/openbsd (Fairfax, VA) ftp://ftp.tux.org/bsd/openbsd (Springfield, VA) ftp://mirror.cs.wisc.edu/pub/mirrors/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 3.7 Release Contents: ----------------------------- The OpenBSD 3.7 release is organized in the following way. In the .../3.7 directory, for each of the architectures having an OpenBSD 3.7 binary distribution, there is a sub-directory. The sparc64-specific portion of the OpenBSD 3.7 release is found in the "sparc64" subdirectory of the distribution. That subdirectory is laid out as follows: .../3.7/sparc64/ INSTALL.sparc64 Installation notes; this file. CKSUM, MD5 Output of the cksum(1) and md5(1) programs, usable for verification of the correctness of downloaded files. miniroot37.fs A miniroot filesystem image to be used if you for some reason can't or don't want to use the ramdisk installation method. It can be copied to the swap partition of an existing OpenBSD, Solaris, NetBSD, or Linux installation to allow installing or upgrading to OpenBSD 3.7. floppy37.fs The standard sparc64 boot and installation floppy; see below. This floppy image will boot on SBus-based sparc64 models, such as: - Ultra 1/1E - Ultra 2 *.tgz sparc64 binary distribution sets; see below. bsd A stock GENERIC sparc64 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. cd37.iso A miniroot filesystem image suitable to be used as a bootable CD-ROM image; otherwise similar to the bsd.rd image above. installboot The OpenBSD/sparc64 boot loader installation program. bootblk The OpenBSD/sparc64 boot block. ofwboot The OpenBSD/sparc64 secondary boot loader. ofwboot.net The OpenBSD/sparc64 network boot loader. Please note that there are multiple bootable images and kernels, intended to allow installing OpenBSD/sparc64 in a variety of situations without requiring a pre-existing working operating system. The kernel and boot images are provided for net booting installations. Bootable installation/upgrade floppy image: The single floppy image can be copied to a floppy using rawrite.exe, ntrw.exe, or `dd', as described later in this document. The floppy image 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. The OpenBSD/sparc64 binary distribution sets contain the binaries which comprise the OpenBSD 3.7 release for sparc64 systems. There are eleven binary distribution sets. The binary distribution sets can be found in the "sparc64" subdirectory of the OpenBSD 3.7 distribution tree, and are as follows: base37 The OpenBSD/sparc64 3.7 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. [ 35.7 MB gzipped, 108.5 MB uncompressed ] comp37 The OpenBSD/sparc64 Compiler tools. All of the tools relating to C, C++, and fortran are supported. This set includes the system include files (/usr/include), the linker, the compiler tool chain, and the various system libraries (except the shared libraries, which are included as part of the base set). This set also includes the manual pages for all of the utilities it contains, as well as the system call and library manual pages. [ 24.6 MB gzipped, 88.3 MB uncompressed ] etc37 This distribution set contains the system configuration files that reside in /etc and in several other places. This set MUST be installed if you are installing the system from scratch, but should NOT be used if you are upgrading. (If you are upgrading, it's recommended that you get a copy of this set and CAREFULLY upgrade your configuration files by hand; see the section named "Upgrading a previously-installed OpenBSD System" below.) [ 1.6 MB gzipped, 6.2 MB uncompressed ] game37 This set includes the games and their manual pages. [ 2.6 MB gzipped, 6.0 MB uncompressed ] man37 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. [ 6.8 MB gzipped, 24.6 MB uncompressed ] misc37 This set includes the system dictionaries (which are rather large), and the typesettable document set. [ 2.1 MB gzipped, 7.0 MB uncompressed ] xbase37 This set includes the base X distribution. This includes programs, headers and libraries. [ 10.1 MB gzipped, 32.1 MB uncompressed ] xetc37 This set includes the X window system configuration files that reside in /etc. It's the equivalent of etc37 for X. [ 0.4 MB gzipped, 2.2 MB uncompressed ] xfont37 This set includes all of the X fonts. [ 31.9 MB gzipped, 35.7 MB uncompressed ] xserv37 This set includes all of the X servers. [ 7.0 MB gzipped, 20.2 MB uncompressed ] xshare37 This set includes all text files equivalent between all architectures. [ 1.8 MB gzipped, 9.5 MB uncompressed ] OpenBSD System Requirements and Supported Devices: -------------------------------------------------- OpenBSD/sparc64 3.7 runs on the following classes of machines: - SBUS based workstations: Ultra 1 Ultra 1E (Creator) Ultra 2 - PCI based workstations: Sun Blade 100/150 Sun Fire V100 Sun Fire V120 Enterprise 150 Enterprise 220R Enterprise 250 Enterprise 420R Enterprise 450 Enterprise 4500/5500 Netra T1 100/105 Netra T 1100 Netra T 1120/1125 Netra T 1400/1405 Netra X1 Ultra 5 Ultra 10 Ultra 30 Ultra 60 Ultra 80 Netra T1 AC200/DC200 SPARCengineUltra AX SPARCengineUltra AXe SPARCengineUltra AXi - CompactPCI boards: SPARCengine CP1500 - faithful clones of the above Sun systems, including: Momentum Leopard-V If your machine is not listed above, it is very likely that OpenBSD/sparc64 does not work on it (yet). The minimal configuration requires 32MB of RAM and ~160MB of disk space. To install the entire system requires much more disk space, and to run X or compile the system, more RAM is recommended. Supported devices include: SCSI Host Adapters: SBus NCR53c9x adapters (esp) SBus 10/100Mbit SunSwift Ethernet+SCSI cards, aka HME + FAS366 cards (esp) SBus QLogic adapters (isp) PCI NCR53c8xx adapters (siop) PCI IDE Controllers: (pciide) Acer Labs M5229 Command Technologies PCI0646, PCI0680 National Semiconductor PC87415 Promise PDC20262, PDC20267, PDC20268 Other PCI IDE controllers may work, but have not been tested CD-ROM and DVD-ROM Drives Most SCSI CD-ROM, CD-R, CD-RW, DVD and DVD-RW drives Most ATAPI CD-ROM, CD-R, CD-RW, DVD and DVD-RW drives Ethernet Adapters: onboard AMD Lance Ethernet (le) SBus AMD Lance Ethernet cards (le) SBus 10/100MBit Sun FastEthernet 1.0 cards (qec/be) SBus Quad 10MBit Sun QuadEthernet cards (qec/qe) onboard SBus/PCI HME Ethernet cards (hme) SBus 10/100Mbit Ethernet cards (hme) SBus 10/100Mbit SunSwift Ethernet+SCSI cards (hme) SBus Quad 10/100MBit Quad Fast Ethernet cards (hme, qfe) PCI Fast Ethernet (hme) PCI Quad Fast Ethernet (hme) PCI GEM Ethernet (gem) PCI Davicom DM9102 Ethernet (dc) PCI Intel 21145-based adapters (dc) PCI Intel i8255x-based (except the i82556) adapters (fxp) PCI 3Com 3c9xx EtherLink XL adapters (xl) Intel i82540, i82541, i82542, i82543, i82544, i82545, i82546 and i82547 based adapters, including: Intel PRO/1000 Gigabit Server Adapter (SX Fiber) (PWLA8490) Intel PRO/1000F Gigabit Server Adapter (SX Fiber) (PWLA8490SX) Intel PRO/1000T Server Adapter (PWLA8490T) Intel PRO/1000XT Server Adapter (PWLA8490XT) Intel PRO/1000XS Server Adapter (SX Fiber) (PWLA8490XF) Intel PRO/1000T Desktop Adapter (PWLA8390T) Intel PRO/1000XTL Lo Profile PCI Server (PWLA8490XTL) Intel PRO/1000MT Desktop Adapter (PWLA8390MT) Intel PRO/1000MT Server Adapter (PWLA8490MT) Intel PRO/1000MT Dual Port Server Adapter (PWLA8492MT) Intel PRO/1000MF Server Adapter (SX Fiber) (PWLA8490MF) Intel PRO/1000MF Dual Port Server Adapter (SX Fiber) (PWLA8492MF) Intel PRO/1000MF Server Adapter (LX Fiber) (PWLA8490LX) Intel PRO/1000MT Quad PCI-X Adapter (PWLA8494MT) PCI RealTek 8129, RealTek 8139 Ethernet adapters, including: Accton MPX 5030/5038 Allied Telesyn AT2550 D-Link DFE530TX+, 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 ADMtek AN986-based USB adapters, including: Abocom UFE1000 Abocom DSB650TX Accton USB320-EC Accton SpeedStream Ethernet Admtek Pegasus, Pegasus II Billionton Systems USB100 Corega FEther USB-TX D-Link DSB-650, 650TX, 650TX-PNA Elecom LD-USB Elsa Microlink USB2Ethernet I/O Data USB ETTX Kingston KNU101TX LinkSys USB100TX, USB100H1 and USB10TA Melco Inc. LUA-TX Siemens SpeedStream USB SmartBridges smartNIC 2 SMC 2202USB SMC EZ Connect USB SOHOware NUB100 ASIX Electronics AX88172 USB Ethernet adapters, including: ATEN UC210T Billionton Systems USB2AR Buffalo(MELCO) LUA-U2-KTX Corega FEther USB2-TX D-Link DUB-E100 Hawking UF200 Intellinet USB 2.0 to Ethernet (rev A) JVC MP-PRX1 LinkSys USB200M Netgear FA120 Sitecom LN-029 SnapPort USB 2.0 LAN Adapter ST Lab USB 2.0 Fast Ethernet Surecom EP-1427X-2 System TALKS SGC-X2UL TRENDnet TU2-ET100 CATC USB-EL1210A-based USB adapters, including: CATC Netmate and Netmate II Belkin F5U011/F5U111 Davicom DM9601 based USB adapters, including: Corega FEther USB-TXC Kawasaki LSI KL5KUSB101B-based USB adapters, including: 3Com 3c19250 3Com 3c460 HomeConnect AboCom Systems URE450 Ethernet ADS Technologies USB-10T Aox USB101 Asante USB to Ethernet ATen DSB-650C ATen UC10T Corega USB-T D-Link DSB-650C Entegra NET-USB-E45 I/O Data USB-ET/T Jaton USB XpressNet Kawasaki USB101 Kingston Ethernet LinkSys USB10T Mobility Ethernet Netgear EA101 Peracom USB Portgear Ethernet Portsmith Express Ethernet Psion Dacom Gold Port Ethernet Shark Pocket Adapter Silicom U2E SMC 2102/2104USB RealTek RTL8150L based USB adapters, including: Abocom RTL8151 GreenHouse GH-USB100B GreenHouse GH-USB100B with HomePNA Linksys USB100M Longshine LCS-8138TX Melco Inc. LUA-KTX Micronet SP128AR SMC 2208USB/ETH TrendNet TU-ET100C Zt USB10/100 Wireless Ethernet Adapters Atmel AT76C50x based USB IEEE 802.11b adapters 3Com 3CRSHEW696 AboCom BWU613 Accton 2664W Acer Peripherals AWL300 Acer Peripherals AWL400 Actiontec 802UAT1 Addtron AWU120 Aincomm AWU2000B Askey Computer Voyager 1010 Askey Computer WLL013 (Intersil Radio) Askey Computer WLL013 (RFMD Radio) Belkin F5D6050 Bluetake BW002 Compaq iPAQ h54xx/h55xx Internal WLAN Conceptronic C11U Conceptronic WL210 Corega WLAN USB Stick 11 Dick Smith Electronics CHUSB 611G Dick Smith Electronics WL200U Dick Smith Electronics WL240U Dick Smith Electronics XH1153 D-Link DWL-120 rev E Geowave GW-US11S Gigabyte GN-WLBM101 Gigaset WLAN Hewlett-Packard HN210W Intel AP310 AnyPoint II I/O DATA USB WN-B11 Lexar 2662W-AR Linksys WUSB11 Linksys WUSB11 v2.8 MSI WLAN Netgear MA101 Netgear MA101 rev B Ovislink AirLive WL-1120USB OvisLink AirLive WL-1130USB Planex Communications GW-US11S Samsung SWL2100W Siemens WLL013 SMC 2662W-AR SMC 2662W-V4 Tekram U-300C Z-Com M4Y-750 Intersil PRISM-2-3 based IEEE 802.11b Compact Flash adapters (will be detected as PCMCIA adapters) Buffalo AirStation D-Link DCF-660W ELSA XI800 Linksys WCF12 Netgear MA701 Intersil PRISM 2-3, Lucent Hermes and Symbol Spectrum 24 based PCMCIA IEEE 802.11b adapters 3Com AirConnect 3CRWE737A ACTIONTEC HWC01170 Addtron AWP-100 Agere Orinoco ARtem Onair BUFFALO AirStation Cabletron RoamAbout Compaq Agency NC5004 Contec FLEXLAN/FX-DS110-PCC Corega PCC-11 Corega PCCA-11 Corega PCCB-11 Corega CGWLPCIA11 D-Link DWL-650 revisions A1-J3 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 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 Wireless LAN Proxim Harmony Proxim RangeLAN-DS Samsung MagicLAN SWL-2000N SMC 2632 EZ Connect Symbol Spectrum24 TDK LAK-CD011WL US Robotics 2410 US Robotics 2445 Intersil PRISM 2-3 and Symbol Spectrum24 based PCI IEEE 802.11b adapters [A] [B] 3Com AirConnect 3CRWE777A Belkin F5D6000 PCI (a rebadged WL11000P) Corega CGWLPCIA11 Eumitcom WL11000P D-Link DWL-520 revisions A and B Global Sun Technology GL24110P (untested) Global Sun Technology GL24110P02 Intersil Mini-PCI LinkSys WDT11 (a rebadged GL24110P02) NDC/Sohoware NCP130 Netgear MA301 Netgear MA311 US Robotics 2415 (rebadged WL11000P) Nortel E-mobility 211818-A Symbol LA4123 Intersil PRISM 2.5/3 based USB IEEE 802.11b adapters Acer Warplink USB-400 Actiontec HWU01170 AirVast WM168b Ambit WLAN Apacer Wireless Steno MB112 ASUS WL-140 Compaq W100 Corega WLUSB-11 Corega WLUSB-11 Key D-Link DWL-120 (rev F) D-Link DWL-122 I-O DATA WN-B11/USB Intel PRO/Wireless 2011B Intersil Prism 2X JVC MP-XP7250 Linksys WUSB11 v3.0 Linksys WUSB12 Melco WLI-USB-KB11 Melco WLI-USB-KS11G Melco WLI-USB-S11 Microsoft MN510 Netgear MA111 (version 1) Pheenet WL-503IA Planex GW-US11H Siemens SpeedStream SS1022 Sitecom WL-022 Syntax USB-400 US Robotics 1120 Z-Com XI-725/726 Z-Com XI-735 ZyXEL ZyAIR B-200 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 [*] Serial ports: onboard SBUS Zilog 8530 (zs) onboard EBUS Infineon (Siemens) 82532 (sab) onboard 16550 compatibles (com) SBus MAGMA cards including: 4Sp, 8Sp, 12Sp, 16Sp, LC2+1Sp, 2+1Sp, 4+1Sp, 8+2Sp, and 2+1HS Sp SBus Serial Parallel Interface (spif) Aurora SBus sio2 Serial Interface (asio) PCI `universal' communication cards, providing serial and parallel ports, including: Dolphin Peripherals 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 Serial, Serial Dual VScom PCI 800 (8 port serial) VScom PCI 100H (1 port serial) VScom PCI 110H (1 port serial and 1 port parallel) VScom PCI 200H (2 port serial) VScom PCI 210H (2 port serial and 1 port parallel) VScom PCI 400H (4 port serial) VScom PCI 410H (4 port serial and 1 port parallel) VScom PCI 800H (8 port serial) VScom PCI 100L (1 port serial) VScom PCI 200L (2 port serial) VScom PCI 210L (2 port serial and 1 port parallel) VScom PCI 400L (4 port serial) VScom PCI 800L (8 port serial) AT&T/Lucent Venus Modem (found on IBM 33L4618 card, Actiontec 56K, and others) US Robotics 3CP5609 PCI (modem) 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) Syba Tech Ltd. PCI-4S2P-550-ECP (4 port serial, 2 port parallel) Moxa Technologies Co., Ltd. PCI I/O Card 4S (4 port serial) Moxa Technologies Co., Ltd. C104H/PCI (4 port serial) NetMos 2S1P (2 port serial and 1 port parallel) Boca Research Turbo Serial 654 PCI (4 port serial) Boca Research Turbo Serial 658 PCI (8 port serial) SUNIX 402x (1 port serial) SUNIX 403x (2 port serial) SUNIX 405x (4 port serial) SUNIX 406x (8 port serial) SUNIX 407x (2 port serial and 1 port parallel) SUNIX 408x (2 port serial and 2 port parallel) SUNIX 409x (4 port serial and 2 port parallel) Sound devices: onboard SBus CS4321 (audiocs) onboard EBus/PCI CS4231 (audioce) Trident 4DWAVE-DX/NX, SiS 7018, ALi M5451 (autri) Ensoniq AudioPCI (eap) ESS Solo-1 PCI AudioDrive (eso) Cryptography accelerators: Hifn 6500 (lofn) Hifn 7751/7811/7951/7955/7956/9751 (hifn) Bluesteelnet 5501/5601 (ubsec) Broadcom 5801/5802/5805/5820/5821/5822/5823 (ubsec) Keyboard and mice: Type 4, 5 and 6 keyboards on Zilog serial ports (zskbd) Type 4, 5 and 6 keyboards on NS16550 serial ports (comkbd) Type 6 keyboards on USB (ukbd) PS/2 AT keyboards (pckbd) Sun mice on Zilog serial ports (zstty) Sun mice on NS16550 serial ports (com) USB mice (ums) PS/2 mice (pms or pmsi) Framebuffers: SBUS framebuffers: bwtwo - monochrome, unaccelerated cgthree - 8 bit color, unaccelerated cgsix - 8 bit color, accelerated (GX, GX+, TGX, TGX+) cgtwelve - 24 bit color, 1 bit overlay, accelerated (but the driver does not support hardware acceleration) Fujitsu AG-10e (agten) - 24-bit color, accelerated (currently only supported in 8-bit unaccelerated mode) Parallax XVideo and PowerVideo (tvtwo) - 24-bit color, accelerated (but the driver does not support hardware acceleration) RasterFlex series (rfx) - 8/24-bit color, accelerated (currently only supported in 8-bit unaccelerated mode) Southland Media Systems MGX and MGXPlus (mgx) - 24-bit color, accelerated (currently only supported in 8-bit unaccelerated mode) Vigra VS10, VS11 and VS12 framebuffers (8-bit color, selectable VGA-compatible modes and connector) ZX (aka Leo) - 8/24-bit color, overlay planes, double-buffered, 3-D acceleration PCI video boards: ATI Rage (vgafb), includes the on-board PGX (8 bit color, unaccelerated) and PGX24 (24 bit color, accelerated) framebuffers UPA Creator/Creator3D/Elite3D (24 bit color, accelerated) PC Cards (PCMCIA): PCMCIA Controllers: SBus PCMCIA bridge (stp) Wireless Ethernet adapters: See above. Radio Receiver Devices D-Link DSB-R100 USB radio Miscellaneous devices: EBus beeper (beeper) performance counters/system controller (uperf) FireHose controller (fhc) Central controller (central) Clock board (clkbrd) SBus Expansion Subsystem (SUNW,xbox) (xbox) (currently restricted to non-DMA devices) onboard floppy drive on SBus systems (such as Ultra 1 and Ultra 2) Hardware that we do NOT currently support, but get many questions about: Multiprocessor machines. Floppy drive on non-SBus systems. SBUS and PCI cards other than those listed above. Getting the OpenBSD System onto Useful Media: --------------------------------------------- Installation is supported from several media types, including: CD-ROM (NOT supported if booting from floppy) FFS partitions (for upgrades only) Tape FTP HTTP If you have the OpenBSD CD-ROM distribution (and a CD-ROM drive), you may be able to boot from it, or from the supplied bootable CD-ROM mini image. If you can boot from the CD-ROM, you are home free and can proceed to the installation steps. If not, you will need to do some setup work to prepare a bootable image, either a floppy, hard drive, or compatible net boot server. In addition to the bootable image, you also need to consider how to access the binary distribution sets to actually install the system. Although you can access the distribution sets directly from the CD-ROM or from one of the FTP mirrors over the internet, you may wish to transfer the sets to a local FTP server, or copy them to a partition on the target system's disk. Creating a bootable floppy disk using DOS/Windows: First you need to get access to the OpenBSD bootable floppy images. If you can access the distribution from the CD-ROM under DOS, you will find the bootable disks in the 3.7/sparc64 directory. Otherwise, you will have to download them from one of the OpenBSD FTP or HTTP mirror sites, using an FTP client or a web browser. In either case, take care to do "binary" transfers, since these are images files and any DOS cr/lf translations or control/z EOF interpretations will result in corrupted transfers. You will also need to go to the "tools" directory and grab a copy of the rawrite.exe utility and its documentation. This program is needed to correctly copy the bootable filesystem image to the floppy, since it's an image of a unix partition containing an ffs filesystem, not an MSDOS format diskette. Once you have installed rawrite.exe, just run it and specify the name of the bootable image, such as "floppy37.fs" and the name of the floppy drive, such as "a:". Be sure to use good quality HD (1.44MB) floppies, formatted on the system you're using. The image copy and boot process is not especially tolerant of read errors. Note that if you are using NT, 2000, or XP to write the images to disk, you will need to use ntrw.exe instead. It is also available in the "tools" directory. Grab it and run in with the correct arguments like this "ntrw :" Note that, when installing, the boot floppy can be write-protected (i.e. read-only). Creating a bootable floppy disk using SunOS, Solaris or other Un*x-like system: First, you will need obtain a local copy of the bootable filesystem image as described above. If possible use the cksum(1) or md5(1) commands to verify the checksums of the images vs. the values in the CKSUM or MD5 files on the mirror site. Next, use the dd(1) utility to copy the file to the floppy drive. The command would likely be, under SunOS: dd if=floppy37.fs of=/dev/rfd0c bs=36b and, under Solaris: dd if=floppy37.fs of=/dev/rdiskette0 bs=36b unless the volume management daemon, vold(1M), is running, in which case the following command is preferable: dd if=floppy37.fs of=/vol/dev/rdiskette0 bs=36b If you are using another operating system, you may have to adapt this to conform to local naming conventions for the floppy and options suitable for copying to a "raw" floppy image. The key issue is that the device name used for the floppy *must* be one that refers to the correct block device, not a partition or compatibility mode, and the copy command needs to be compatible with the requirement that writes to a raw device must be in multiples of 512-byte blocks. The variations are endless and beyond the scope of this document. If you're doing this on the system you intend to boot the floppy on, copying the floppy back to a file and doing a compare or checksum is a good way to verify that the floppy is readable and free of read/write errors. Note that, when installing, the boot floppy can be write-protected (i.e. read-only). Creating a bootable hard disk using SunOS, Solaris or other Un*x-like system: If you don't have a floppy drive you can copy the mini-root "miniroot37.fs" onto the hard disk you intend to boot on. Traditionally, the way to do this is to use dd(1) to place the bootable filesystem image in the "swap" partition of the disk (while running in single user mode), and then booting from that partition. Using the "b" partition allows you to boot without overwriting any useful parts of the disk; you can also use another partition, but don't used the "a" or "c" partition without understanding the disk label issues described below under "incompatible systems". This requires that you be running SunOS, Solaris, OpenBSD, or NetBSD, which have a compatible view of SunOS disk labels and partitions. Use the dd(1) utility to copy the file to the hard drive. The command would likely be, under SunOS: dd if=miniroot37.fs of=/dev/rsd0b bs=64b and under Solaris: dd if=miniroot37.fs of=/dev/rdsk/c0t0d0s1 bs=64b The blocksize is arbitrary as long as it's a multiple of 512-bytes and within the maximum supported by the driver, i.e. bs=126b may not work for all cases. Again, device/partition names may vary, depending on the OS involved. If you are preparing the hard drive on an incompatible system or don't care about the hard disk contents, you can also install the bootable image starting at the beginning of the disk. This lets you prepare a bootable hard-drive even if don't have a working operating system on your machine, but it is important to understand that the bootable image installed this way includes a "disk label" which can wipe out any pre-existing disklabels or partitioning for the drive. If you're starting with a virgin disk and trying to do this under SunOS, use format(8) and newfs(8) to set up the partitions and mark the intended partition as an normal partition type. If you're using OpenBSD, perhaps on another architecture, OpenBSD will create a "fictitious label" that will let you access the whole disk. Creating a network bootable setup using SunOS or other Un*x-like system: The details of setting up a network bootable environment vary considerably, depending on the network's host. Extract the OpenBSD diskless(8) man page from the man37.tgz distribution set or see the copy on the OpenBSD web page. You will also need to reference the relevant man pages or administrators guide for the host system. Basically, you will need to set up reverse-arp (rarpd) and boot parameter (rpc.bootparamd) information and make the OpenBSD bootblock, kernel/miniroot partition, and a swap file available as required by the netboot setup. 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. The variety of options listed may seem confusing, but situations vary widely in terms of what peripherals and what sort of network arrangements a user has, the intent is to provide some way that will be practical. Creating an installation tape: While you won't be able to boot OpenBSD from a tape, you can use one to provide the installation sets. To do so, you need to make a tape that contains the distribution set files, each in "tar" format or in "gzipped tar format". First you will need to transfer the distribution sets to your local system, using ftp or by mounting the CD-ROM containing the release. Then you need to make a tape containing the files. If you're making the tape on a UN*X-like system, the easiest way to do so is make a shell script along the following lines, call it "/tmp/maketape". #! /bin/sh TAPE=${TAPE:-/dev/nrst0} mt -f ${TAPE} rewind for file in base etc comp game man misc xbase xetc xfont xserv xshare do dd if=${file}37.tgz of=${TAPE} obs=8k conv=sync done tar cf ${TAPE} bsd mt -f ${TAPE} offline # end of script And then: cd .../3.7/sparc64 sh -x /tmp/maketape If you're using a system other than OpenBSD or SunOS, the tape name and other requirements may change. You can override the default device name (/dev/nrst0) with the TAPE environment variable. For example, under Solaris, you would probably run: TAPE=/dev/rmt/0n sh -x /tmp/maketape Note that, when installing, the tape can be write-protected (i.e. read-only). If you are upgrading OpenBSD, you also have the option of installing OpenBSD by putting the new distribution sets somewhere in your existing file system, and using them from there. To do that, do the following: Place the distribution sets you wish to upgrade somewhere in your current file system tree. At a bare minimum, you must upgrade the "base" binary distribution, and so must put the "base37" set somewhere in your file system. It is recommended that you upgrade the other sets, as well. Preparing your System for OpenBSD Installation: ----------------------------------------------- If your UltraSPARC machine is somewhat old, it might need a firmware update before it can be used under OpenBSD. You are advised to try to install OpenBSD first; if it can't boot or fails mysteriously, you might need to update your firmware. To do so, check the ``Updating your firmware'' section later in this document. Your OpenBOOT ROM may need some setup. You cannot use the security modes of the OpenBOOT ROM. Make sure that the ROM security modes are disabled: ok setenv security-mode none Please note that while OpenBSD and Solaris have a reasonable degree of compatibility between disk labels and filesystems there are some problems to watch out for during initial installation or when trying to maintain both OpenBSD and Solaris environments on the same system. If the OpenBSD fsck(8) utility is used on a Solaris filesystem, it will set OpenBSD "clean flags" and BSD4.4 summary fields in the superblock. Solaris does *not* like this and you will have to do a "fsck -b 32" under Solaris to access an alternate superblock to repair the filesystem. You should always specify Solaris filesystems with a "pass number" of 0 in their /etc/fstab entry to prevent this, and preferably mount them "RO". If Solaris fsck is used on an OpenBSD filesystem in the default OpenBSD (4.4BSD) format, it will first complain about the superblock and then about missing . and .. entries. Do *not* try to "correct" these problems, as attempting to do so will completely trash the filesystem. You should avoid using soft updates (option softdep in /etc/fstab) on your shared filesystems. Although untested, it is likely that Solaris would be confused by a filesystem with soft update flags enabled. The OpenBSD "Sun Compatible" disklabel has been extended to support 16 partitions, which may be compatible with Solaris, but the Solaris format(1M) utility only sees the first 8 partitions and may "lose" information about the extended partitions. Use Solaris format(1M) only with *extreme* caution on drives that contain OpenBSD partitions. OpenBSD and Sun bootblocks are similar in concept, though implemented differently. The OpenBSD bootblocks are architecture independent and also understand the extended disk labels with 16 partitions. You can use Solaris bootblocks, but remember that OpenBSD bootblocks must be installed with OpenBSD installboot and Solaris bootblocks with Solaris installboot. Most of the new Ultras shipped by Sun with a preinstalled Solaris have an initial specific factory setup of the boot ROM, in order to start up Solaris WebStart at the first boot; the boot-device variable is set to disk:f. Make sure you reset the boot device to its default value: ok set-default boot-device will work for most systems. This can be adapted if you've multiple systems installed and know what you're doing. To disable automatic boot use the following command: ok setenv auto-boot? false and then to enable it later use: ok setenv auto-boot? true or on an installed system use the eeprom(8) commmand: # eeprom 'auto-boot?=true' Updating your firmware: ----------------------- If OpenBSD does not boot or install properly on your machine, it might need a firmware update. Updating your firmware is a dangerous operation which may damage your hardware. Be sure to carefully follow these instructions and, if in doubt, please don't do this. You will need to have a working operating system installed on your machine, in order to perform the update. If this is not the case, you might be able to boot the flash updater software via network, but this has not been tested and is not supported by Sun. The firmware update is delivered as a specific patch, depending on your machine: Machine Patch number Blade 100/150 111179 Enterprise 220R 106455 Enterprise 250 106503 Enterprise 450 106122 Netra X1 111952 Ultra 1 104881 Ultra 1E 104288 Ultra 2 104169 Ultra 5/10 106121 Ultra 30 105930 Ultra 60 106455 Get the patch installation notes from SunSolve, as ftp://sunsolve.sun.com/pub/patches/104169.readme (replace 104169 with the correct patch number). Check the Patch-ID# line in this readme file to get the patch filename, for example 104169-08. The patch filename will then be either ftp://sunsolve.sun.com/pub/patches/104169-08.tar.Z or ftp://sunsolve.sun.com/pub/patches/104169-08.zip Follow the patch installation notes very carefully. You will need to open your machine in order to apply this patch. 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.) There are several ways to install OpenBSD onto a disk. The easiest way in terms of preliminary setup is to use the OpenBSD installation CD-ROM, or the installation floppy. If your machine is hooked up to a network, try and find a server to arrange for a diskless setup. This is a convenient way to install on a machine whose disk does not currently hold a usable operating system. This is difficult to get set up correctly the first time, but easy to use afterwards. (See ``Installing using a diskless setup'' below.) It is also possible to install OpenBSD "manually" from a running Solaris system, using the system tools, as well as gunzip; see ``Installing from Solaris'' below. Booting from the Installation Media: Prior to attempting an installation, you should make sure that everything of value on the target system has been backed up. While installing OpenBSD does not necessarily wipe out all the partitions on the hard disk, errors during the install process can have unforeseen consequences and you will probably render the system unbootable if you start, but do not complete the installation. Having the installation media for the prior installation, be it a Solaris or OpenBSD CD-ROM or OpenBSD install diskettes, is good insurance if you want to be able to "go back" for some reason. After taking care of all that, bring your system down gracefully using the shutdown(8) and/or halt(8) commands. This will get you to the monitor prompt. Booting from Floppy Disk installation media: ok boot floppy bsd This will cause the kernel contained in the floppy to be booted. Please note that PCI systems are not able to boot from floppy; also, Ultra 1, 1E, and 2 systems might need a firmware update to be able to boot from floppy; refer to the ``Updating your firmware'' section earlier in this document for details. Booting From CD-ROM installation media: ok boot cdrom If the boot is successful, you will get a loader version message, executable sizes, and then the kernel copyright and device probe messages. Boot failure modes are typically a lot of CD-ROM drive activity, but no messages or complaints about magic numbers, checksums or formats. Booting from disk: Boot the miniroot by typing the appropriate command at the PROM: ok boot disk:b bsd If you've loaded the miniroot onto some other disk than the default drive 0, modify the boot specifier accordingly, keeping in mind the partition naming a=0, b=1... ok boot disk1:b bsd # example - scsi target 1 or # second ide drive During the boot, the kernel might not be able to determine by itself which device it has been booted from. In this case, it will ask you for the root and swap devices. Answer the device and partition you booted from as the root partition (likely sd0b or wd0b); you might want to rely on the boot messages to find the correct device name (see below). When the kernel asks you for the swap device, just validate the suggested device name; since the installation procedure does not use swap, it doesn't matter. Installing using a diskless setup: First, you must set up a diskless client configuration on a server. If you are using an OpenBSD system as the boot-server, have a look at the diskless(8) manual page for guidelines on how to proceed with this. If the server runs another operating system, you'll have to consult documentation that came with it (on SunOS systems, add_client(8) and the Sun System/Networks administrators guide constitute a good start; on Solaris systems, share(1M) is a good starting point as well). Boot your workstation from the server by entering the appropriate `boot' command at the monitor prompt: ok boot net bsd.rd Installing using the Floppy, CD-ROM, miniroot or 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 kernel especially from a floppy or slow network connection, 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 isn't correct, 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 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 might get this kind of warning: "No counter-timer -- using %tick at 179MHz as system clock." Unless the frequency displayed does not match your CPU speed, this is nothing to worry about. You will next be asked for your terminal type. If you are installing from a keyboard/monitor console, the default of "sun" 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 vt100.) After entering the terminal type you will be asked whether you wish to do an "(I)nstall" or an "(U)pgrade". Enter 'I' for a fresh install or 'U' to upgrade an existing installation. You will be presented with a welcome message and asked if you really wish to install (or upgrade). Assuming you answered yes, the install program will then tell you which disks of that type it can install on, and ask you which it should use. The name of the disk is typically "sd0" for SCSI drives. Reply with the name of your disk. Next 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). 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. "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 give you an opportunity to configure the network. The network configuration you enter (if any) can then be used to do the install from another system using HTTP or FTP, and will also be the configuration used by the system after the installation is complete. If you select to configure the network, the install program will ask you for the name of your system and the DNS domain name to use. Note that the host name should be without the domain part, and that the domain name should NOT include the host name part. Next the system will give you a list of network interfaces you can configure. For each network interface you select to configure, it will ask for the IP address to use, the symbolic host name to use, the netmask to use, and any interface-specific flags to set. The interface-specific flags are usually used to determine which media the network card is to use. Typically no media flags are required as autodetection normally works, but you will be prompted with a list of the acceptable media flags, and asked if you want to provide any. In doubt, do not enter any media flags; or you can refer to the manual page for your interface for the appropriate flags. After all network interfaces have been configured, the install pro- gram will ask for a default route and IP address of the primary name server to use. You will also be presented with an opportunity to edit the host table. At this point you will be allowed to edit the file system table that will be used for the remainder of the installation and that will be used by the finished system, following which the new file systems will be mounted to complete the installation. After these preparatory steps have been completed, you will be able to extract the distribution sets onto your system. There are several install methods supported; FTP, HTTP, tape, CD-ROM, or a local disk partition. 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 3.7 distribution. If you don't know, just hit return when asked if you want to see a list of such hosts. 4) The FTP directory holding the distribution sets. The default value of pub/OpenBSD/3.7/sparc64 is almost always correct. 5) The login and password for the FTP account. You will only be asked for a password for non-anonymous FTP. For instructions on how to complete the installation via FTP, see the section named "Common URL installations" below. To install via HTTP: To begin an HTTP install you will need the following pieces of information: 1) Proxy server URL if you are using a URL-based HTTP proxy (squid, CERN FTP, Apache 1.2 or higher). You need to define a proxy if you are behind a firewall that blocks outgoing HTTP connections (assuming you have a proxy available to use). 2) The IP address (or hostname if you enabled DNS earlier in the install) of an HTTP server carrying the OpenBSD 3.7 distribution. If you don't know, just hit return when asked if you want to see a list of such hosts. 3) The directory holding the distribution sets. There is no standard location for this; You should use the directory specified along with the server in the list of official HTTP mirror sites that you received in step 3. For instructions on how to complete the installation via HTTP, see the section named "Common URL installations" below. To install from tape: In order to install from tape, the distribution sets to be installed must have been written to tape previously, either in tar format or gzip-compressed tar format. You will also have to identify the tape device where the distribution sets are to be extracted from. This will typically be "nrst0" (no-rewind, raw interface). Next you will have to provide the file number of the set that is to be extracted. Note that the file number starts at 1, which is the first file written to the tape. The install program will not automatically detect whether an image has been compressed, so it will ask for that information before starting the extraction. To install from CD-ROM: When installing from a CD-ROM, you will be asked which device holds the distribution sets. This will typically be "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 sparc64 this is "3.7/sparc64". 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 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 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 "base37", "etc37", and "bsd" distribution sets. After completing an installation: Now try a reboot. (If needed, swap your SCSI IDs first). The UltraSPARC OpenFirmware will normally load the kernel from the device and filename as instructed by the ``boot-device'' and ``boot-file'' variables. If the ``boot-file'' variable is empty, the OpenBSD bootloader will look for a kernel named ``bsd'', unless a different filename has been specified in the boot command. To reset this variable to its default, empty, value, type the following: ok set-default boot-file Congratulations, you have successfully installed OpenBSD 3.7. 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 "more 1" to get the first message. You quit mail by entering "q". Some of the files in the OpenBSD 3.7 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. If you will be running your OpenBSD system from a serial console, you may need to edit /etc/ttys and change the terminal type, and getty method from "sun" and "suncons" to "vt100" and "std.9600" or something similar. Also when running from a serial console, you may wish to adjust the eeprom settings for input-device, output-device, screen-#columns, and screen-#rows as appropriate. In order to use 'tip' on OpenBSD/sparc64, you'll need to edit /etc/ttys and add "local" to the end of the tty configuration line, and run 'ttyflags -a' to put your changes into effect. Installing from Solaris: You need a machine running under Solaris to install OpenBSD. You will also need at least the following pieces: - the *.tgz files you want to install (as a minimum, base37.tgz and etc37.tgz) - gunzip (GNU gzip) Solaris binary - the OpenBSD boot blocks (bootblk and ofwboot) - an OpenBSD kernel All these pieces, except gunzip, are supplied in the OpenBSD/sparc64 distribution. You need to format and partition the disk using Solaris (since OpenBSD/sparc64 uses Sun compatible disk labels). Give yourself adequate partition sizes. Here is an example layout: solaris# prtvtoc -s /dev/rdsk/c0t1d0s2 * First Sector Last * Partition Tag Flags Sector Count Sector Mount Directory 0 2 00 0 80000 79999 / 1 3 01 80000 256000 335999 2 5 00 0 4165271 4165270 3 7 00 336000 100000 435999 /tmp 4 7 00 436000 100000 535999 /var 5 7 00 536000 400000 935999 /var/tmp 6 4 00 936000 3229271 4165270 /usr Use Solaris to newfs the partitions which will have filesystems on them. (OpenBSD's filesystem format is almost identical to Solaris.) solaris# newfs /dev/rdsk/c0t1d0s0 [... lots of output] Repeat for any other partition (in this example, /dev/rdsk/c0t1d0s3, /dev/rdsk/c0t1d0s4, /dev/rdsk/c0t1d0s5 and /dev/rdsk/c0t1d0s6). NOTE: If you are able to, there is a performance benefit from newfs'ing using OpenBSD. If you newfs using the OpenBSD newfs command, be sure to use the -O flag for your / partition, so that newfs will use the 4.3BSD filesystem format, rather than the new 4.4BSD filesystem format. If you forget, you will not be able to boot -- the Solaris boot blocks do not understand the extended 4.4BSD filesystem format. Mount those partitions in a tree formation, under /mnt; ie: solaris# df -k Filesystem kbytes used avail capacity Mounted on [...] /dev/dsk/c0t1d0s0 38427 0 38427 0% /mnt /dev/dsk/c0t1d0s3 48249 0 48249 0% /mnt/tmp /dev/dsk/c0t1d0s4 48249 0 48249 0% /mnt/var /dev/dsk/c0t1d0s5 193536 0 193536 0% /mnt/var/tmp /dev/dsk/c0t1d0s6 1564024 0 1564024 0% /mnt/usr Place the boot blocks in /mnt (your new root partition), and use the Solaris command "installboot" to make it work. The installboot man page says to do something like this: solaris# cp bootblk ofwboot /mnt solaris# sync; sync solaris# /usr/sbin/installboot /mnt/bootblk /dev/rdsk/c0t1d0s0 You can now extract the provided "*.tgz" files onto your disk. solaris# ls -FC base37.tgz etc37.tgz misc37.tgz xserv37.tgz bsd game37.tgz xbase37.tgz xshare37.tgz comp37.tgz man37.tgz xfont37.tgz solaris# gunzip < base37.tgz | (cd /mnt; tar xvpf -) [...] for each set And finally copy the OpenBSD kernel onto your disk. solaris# cp bsd /mnt/bsd The GNU gunzip program is not distributed as part of Solaris, but may be present in your /usr/local/bin. If not, you will need to obtain it from a GNU archive and install before proceeding. After the files have been extracted, set up /mnt/etc/fstab to match your actual disk layout. (Minus the "/mnt" component of each path, of course :-) Now proceed to reboot the machine and the customize your installation. Net Boot or Diskless Setup Information: The set up is similar to the diskless setup, but not identical, because the Sun setup assumes that the bootblocks load a kernel image, which then uses NFS to access the exported root partition, while the OpenBSD bootblocks use internal NFS routines to load the kernel image directly from the exported root partition. Please understand that no one gets this right the first try, since there is a lot of setup and all the host daemons must be running and configured correctly. If you have problems, extract the diskless(8) manpage, find someone who's been through it before and use the host syslog and tcpdump(8) to get visibility of what's happening (or not). Your UltraSPARC expects to be able to download a second stage bootstrap program via TFTP after having acquired its IP address through RevARP when instructed to boot "over the net". It will look for a filename composed of the machine's IP address. For example, a machine which has been assigned IP address 130.115.144.11 will make a TFTP request for `8273900B'. Normally, this file is a symbolic link to an appropriate second-stage boot program, which should be located in a place where the TFTP daemon can find it (remember, many TFTP daemons run in a chroot'ed environment). You can find the boot program in `/usr/mdec/boot' in the OpenBSD/sparc64 distribution. After the boot program has been loaded into memory and given control by the PROM, it starts locating the machine's remote root directory through the BOOTPARAM protocol. First a BOOTPARAM WHOAMI request is broadcast on the local net. The answer to this request (if it comes in) contains the client's name. This name is used in the next step, a BOOTPARAM GETFILE request -- sent to the server that responded to the WHOAMI request -- requesting the name and address of the machine that will serve the client's root directory, as well as the path of the client's root on that server. Finally, this information (if it comes in) is used to issue a REMOTE MOUNT request to the client's root filesystem server, asking for an NFS file handle corresponding to the root filesystem. If successful, the boot program starts reading from the remote root filesystem in search of the kernel which is then read into memory. You will want export the miniroot37.fs filesystem to the client. You can dd this filesystem image to some spare partition, mount and export that partition, or use tar to copy the contents to a more convenient spot. Alternatively you can build a bootable partition from the distribution sets as follows: Unpack `base37.tgz' and `etc37.tgz' on the server in the root directory for your target machine. If you elect to use a separately NFS-mounted filesystem for `/usr' with your diskless setup, make sure the "./usr" base files in base37.tgz end up in the correct location. One way to do this is to temporarily use a loopback mount on the server, re-routing /usr to your server's exported OpenBSD "/usr" directory. Also put the kernel and the install/upgrade scripts into the root directory. A few configuration files need to be edited: /etc/hosts Add the IP addresses of both server and client. /etc/myname This files contains the client's hostname; use the same name as in /etc/hosts. /etc/fstab Enter the entries for the remotely mounted filesystems. For example: server:/export/root/client / nfs rw 0 0 server:/export/exec/sparc64.OpenBSD /usr nfs rw 0 0 Now you must populate the `/dev' directory for your client. If the server does not run OpenBSD you might save the MAKEDEV output: eo=echo ksh MAKEDEV all > all.sh and then tailor it for your server operating system before running it. Note that MAKEDEV is written specifically for ksh, and may not work on any other Bourne shell. There will be error messages about unknown users and groups. These errors are inconsequential for the purpose of installing OpenBSD. However, you may want to correct them if you plan to use the diskless setup regularly. In that case, you may re-run MAKEDEV on your OpenBSD machine once it has booted. Upgrading a previously-installed OpenBSD System: ------------------------------------------------ Warning! Upgrades to OpenBSD 3.7 are currently only supported from the immediately previous release. The upgrade process will also work with older releases, but might not execute some migration tasks that would be necessary for a proper upgrade. The best solution, whenever possible, is to backup your data and reinstall from scratch. To upgrade OpenBSD 3.7 from a previous version, start with the general instructions in the section "Installing OpenBSD". Boot from CD-ROM, the miniroot, or the installation floppy. 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 ``etc37.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 etc37.tgz set in a temporary directory and merge changes by hand, since all components of your system may not function correctly until your files in `/etc' are updated. Getting source code for your OpenBSD System: -------------------------------------------- Now that your OpenBSD system is up and running, you probably want to get access to source code so that you can recompile pieces of the system. A few methods are provided. If you have an OpenBSD CD-ROM, the source code is provided. Otherwise, you can get the pieces over the Internet using anonymous CVS, CTM, CVSync or FTP. For more information, see http://www.OpenBSD.org/anoncvs.html http://www.OpenBSD.org/ctm.html http://www.OpenBSD.org/cvsync.html http://www.OpenBSD.org/ftp.html Using online OpenBSD documentation: ----------------------------------- Documentation is available if you first install the manual pages distribution set. Traditionally, the UN*X "man pages" (documentation) are denoted by 'name(section)'. Some examples of this are intro(1), man(1), apropos(1), passwd(1), passwd(5) and afterboot(8). The section numbers group the topics into several categories, but three are of primary interest: user commands are in section 1, file formats are in section 5, and administrative information is in section 8. The 'man' command is used to view the documentation on a topic, and is started by entering 'man [section] topic'. The brackets [] around the section should not be entered, but rather indicate that the section is optional. If you don't ask for a particular section, the topic with the least-numbered section name will be displayed. For instance, after logging in, enter man passwd to read the documentation for passwd(1). To view the documentation for passwd(5), enter man 5 passwd instead. If you are unsure of what man page you are looking for, enter apropos subject-word where "subject-word" is your topic of interest; a list of possibly related man pages will be displayed. Adding third party software; ``packages'' and ``ports'': -------------------------------------------------------- As complete as your OpenBSD system is, you may want to add any of several excellent third party software applications. There are several ways to do this. You can: 1) Obtain the source code and build the application based upon whatever installation procedures are provided with the application. 2) Use the OpenBSD ``ports'' collection to automatically get any needed source file, apply any required patches, create the application, and install it for you. 3) Use the OpenBSD ``package'' collection to grab a pre-compiled and tested version of the application for your hardware. If you purchased the OpenBSD CD-ROM set you already have several popular ``packages'', and the ``ports'' collection. Instructions for installing applications from the various sources using the different installation methods follow. You should also refer to the packages(7) manual page. Installing applications from the CD-ROM package collection: The OpenBSD CD-ROM ships with several applications pre-built for various hardware architectures. The number of applications vary according to available disk space. Check the directory 3.7/packages/sparc64 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/3.7/packages/sparc64/ # # umount /cdrom Package names are usually the application name and version with .tgz appended, e.g. emacs-21.3.tgz Installing applications from the ftp.OpenBSD.org package collection: All available packages for your architecture have been placed on ftp.OpenBSD.org in the directory pub/OpenBSD/3.7/packages/sparc64/ 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/3.7/packages/sparc64/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 tinker with the FreeBSD ports or NetBSD pkgsrc. If you can't find an existing port, try to make your own and feed it back to OpenBSD. That's how our ports collection grows. Some details can be found at http://www.OpenBSD.org/porting.html with more help coming from the mailing list, . 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. For more information about reporting bugs, see http://www.OpenBSD.org/report.html