INSTALLATION NOTES for OpenBSD/sparc 4.1 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.1 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.1 release is available on the web at http://www.OpenBSD.org/41.html. OpenBSD/sparc runs on 32 bit SPARC-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 4.1 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) ftp://mirror.pacific.net.au/OpenBSD (Sydney) 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.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) Hungary: ftp://ftp.fsn.hu/pub/OpenBSD (Budapest) Ireland: ftp://ftp.esat.net/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) South Africa: ftp://ftp.is.co.za/pub/OpenBSD (Johannesburg) Spain: ftp://ftp.rediris.es/mirror/OpenBSD (Madrid) Sweden: ftp://ftp.su.se/pub/OpenBSD (Stockholm) ftp://ftp.btradianz.se/pub/OpenBSD (Stockholm) Switzerland: ftp://mirror.switch.ch/pub/OpenBSD (Zurich) 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.sese.asu.edu/pub/OpenBSD (Tempe, AZ) 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://ftp.nyc.openbsd.org/pub/OpenBSD (New York, NY) ftp://mirrors.24-7-solutions.net/pub/OpenBSD (New York, NY) ftp://openbsd.mirrors.pair.com (Pittsburgh, PA) ftp://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.1 Release Contents: ----------------------------- The OpenBSD 4.1 release is organized in the following way. In the .../4.1 directory, for each of the architectures having an OpenBSD 4.1 binary distribution, there is a sub-directory. The sparc-specific portion of the OpenBSD 4.1 release is found in the "sparc" subdirectory of the distribution. That subdirectory is laid out as follows: .../4.1/sparc/ INSTALL.sparc Installation notes; this file. CKSUM, MD5 Output of the cksum(1) and md5(1) programs, usable for verification of the correctness of downloaded files. miniroot41.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, NetBSD, Linux, SunOS, or Solaris installation to allow installing or upgrading to OpenBSD 4.1. floppy41.fs The standard sparc boot and installation floppy; see below. *.tgz sparc binary distribution sets; see below. bsd A stock GENERIC sparc kernel which will be installed on your system during the install. bsd.scsi3 A kernel with SCSI target 3 re-mapped as 0 and 0 mapped as 3. bsd.rd A compressed RAMDISK kernel; the embedded filesystem contains the installation tools. Used for simple installation from a pre-existing system. cd41.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/sparc boot loader installation program. bootxx The OpenBSD/sparc boot block. boot The OpenBSD/sparc secondary boot loader. boot.net The OpenBSD/sparc network boot loader. Please note that there are multiple bootable images and kernels, intended to allow installing OpenBSD/sparc in a variety of situations without requiring a pre-existing working operating system. The kernel and boot images are provided for net booting installations. While the OpenBSD bootblocks will work with the provided miniroot images, Sun bootblocks require a separate kernel image and root filesystem. 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/sparc binary distribution sets contain the binaries which comprise the OpenBSD 4.1 release for sparc systems. There are eleven binary distribution sets. The binary distribution sets can be found in the "sparc" subdirectory of the OpenBSD 4.1 distribution tree, and are as follows: base41 The OpenBSD/sparc 4.1 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. [ 36.2 MB gzipped, 107.1 MB uncompressed ] comp41 The OpenBSD/sparc Compiler tools. All of the tools relating to C, C++, Objective-F 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. [ 57.2 MB gzipped, 217.4 MB uncompressed ] etc41 This distribution set contains the system configuration files that reside in /etc and in several other places. This set MUST be installed if you are installing the system from scratch, but should NOT be used if you are upgrading. (If you are upgrading, it's recommended that you get a copy of this set and CAREFULLY upgrade your configuration files by hand; see the section named Upgrading a previously-installed OpenBSD System" below.) [ 1.1 MB gzipped, 3.6 MB uncompressed ] game41 This set includes the games and their manual pages. [ 2.5 MB gzipped, 5.7 MB uncompressed ] man41 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.4 MB uncompressed ] misc41 This set includes the system dictionaries (which are rather large), and the typesettable document set. [ 2.1 MB gzipped, 7.1 MB uncompressed ] xbase41 This set includes the base X distribution. This includes programs, headers and libraries. [ 10.1 MB gzipped, 30.1 MB uncompressed ] xetc41 This set includes the X window system configuration files that reside in /etc. It's the equivalent of etc41 for X. [ 89.2 KB gzipped, 351.3 KB uncompressed ] xfont41 This set includes all of the X fonts. [ 31.6 MB gzipped, 35.8 MB uncompressed ] xserv41 This set includes all of the X servers. [ 9.3 MB gzipped, 27.3 MB uncompressed ] xshare41 This set includes all text files equivalent between all architectures. [ 1.9 MB gzipped, 10.4 MB uncompressed ] OpenBSD System Requirements and Supported Devices: -------------------------------------------------- OpenBSD/sparc 4.1 runs on the following classes of machines: * sun4: the VME series - 4/100: Original SPARC with VME. Many hardware bugs. - 4/200: A fairly decent VME-only machine - 4/300: a 25MHz VME machine with many devices built onto the main board. In other respects, it is quite similar to the SS1+. * sun4c: - SS1: the original 20MHz sun4c. Hardware limitations prevent SBus DMA peripherals from working in some of the slots. - SS1+: 25MHz version of the above. Hardware limitations prevent SBus DMA peripherals from working in some of the slots. - IPC: SS1+ in a cube, with bwtwo graphics builtin - SLC: SS1+ built into a B&W monitor - SS2: 40MHz version of the SS1 - IPX: SS2 in a cube, with cgsix graphics builtin - ELC: SS2-performance built into a B&W monitor * sun4m: - 600MP: The original Sun4m machine. This is an mbus machine with SBus and VME busses. - LC: 50MHz MicroSPARC-1 based machines (aka Classic) - LX: LC with a few more devices - SS4: Reduced cost version of the SS5, available at 70MHz and 110MHz - SS5: MicroSPARC-2 based machines available in 60, 70, 85, and 110 MHz versions - SS5: TurboSPARC cpus in accelerated SS5 machines, running at 170MHz - SS10: Pizzabox mbus-based machine - SS20: Improved pizzabox mbus-based machine - Sun Voyager * As well as faithful clones of the above Sun systems, such as: - Aries Research Inc, Parrot II (SS2 clone) - Axil 243 and 245 (and possibly other models) (SS5 clones) - Axil 320 (SS20 clone) - Opus 5000 (SS1 clone) - Opus 5250 (SS1 clone) - SPARCbook 3, 3GS, 3GX, 3TX and 3XP by Tadpole (MicroSPARC-2) - CPU5V: VME card by Force Computer (sun4m) - TWS,SuperCOMPstation-20S (SS20 clone) - Tatung micro COMPstation 5 (SS5 clone) - Tatung micro COMPstation LX (LX clone) - RDI,PowerLite: sun4m models, available in 50, 85 and 110 MHz - RDI,BrideLite - DTKstation/Classic+ - Transtec SS5/170 For sun4m machines, the following mbus CPU modules are supported: - SM30: 30 or 36 MHz SuperSPARC with no secondary cache - SM40: 40 MHz SuperSPARC with no secondary cache - SM41: 40 MHz SuperSPARC with 1MB of secondary cache - SM50: 50 MHz SuperSPARC with no secondary cache - SM51: 50 MHz SuperSPARC with 1MB of secondary cache - SM51-2: 50 MHz SuperSPARC with 2MB of secondary cache - SM61: 60 MHz SuperSPARC with 1MB of secondary cache - SM61-2: 60 MHz SuperSPARC with 2MB of secondary cache - SM71: 75 MHz SuperSPARC with 1MB of secondary cache - SM81: 85 MHz SuperSPARC with 1MB of secondary cache - SM81-2: 85 MHz SuperSPARC with 2MB of secondary cache - SM100: dual 40 MHz Cypress 7C601 with 64KB of primary cache - Ross HyperSPARC RT620/625 at 90 MHz, with 256KB of primary cache - Ross HyperSPARC RT620/625 at 125 MHz, with 256KB of primary cache - Ross HyperSPARC RT620/625 at 150 MHz, with 512KB of primary cache - Ross HyperSPARC RT620/625 at 166 MHz, with 512KB of primary cache - Ross HyperSPARC RT620/625 at 180 MHz, with 512KB of primary cache The minimal configuration requires 4MB of RAM and ~60MB 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. (OpenBSD with 4MB of RAM feels like Solaris with 4MB of RAM.) Note that until you have around 16MB of RAM, getting more RAM is more important than getting a faster CPU.) Installation from "ramdisk" kernels requires 8MB of RAM. Supported devices include: * Sun keyboard and mouse - Type 2, 3, 4, and 5 keyboards with several layouts * Floppy drives: - sun4c and sun4m floppy disk drive * Serial ports: - ttya and ttyb on-board serial ports (can be used as console if needed) - 4/300 ttyc and ttyd on-board serial ports - SBus magma serial port cards, including: 4Sp, 8Sp, 12Sp, 16Sp, LC2+1Sp, 2+1Sp, 4+1Sp, 8+2Sp, and 2+1HS Sp. - SBus Serial Parallel Interface (SUNW,spif, 501-1931) * Audio support: - on-board audio support for systems with AMD79C30 8-bit audio chips (this includes sun4c models, SPARCclassic, and 600MP) - SUNW,CS4231 16-bit audio chips found on SPARCstation 4/5 * Framebuffers: - SBus and sun4c/sun4m on-board video: + bwtwo - black and white + cgthree - 8-bit color, unaccelerated The cgthree driver also supports the cgRDI, an onboard cgthree-like framebuffer found in some laptops. + cgsix - 8-bit color, accelerated (GX, GX+, TGX, TGX+) This driver should also work with faithful emulations or clones of the SBus cgsix. + cgtwelve - 24-bit color, 1-bit overlay, accelerated (but the driver does not support hardware acceleration) + cgfourteen - 8/24-bit color, 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) + TCX - 8/24-bit color + Vigra VS10, VS11 and VS12 framebuffers (8-bit color, selectable VGA-compatible modes and connector) + Weitek Power9000 (pninek) framebuffer found in Tadpole SPARCbook 3 (8 bit accelerated) + Weitek Power9100 (pnozz) framebuffer found in Tadpole SPARCbook 3GS, 3GX, 3TX and 3XP (8, 16 or 32-bit accelerated) + ZX (aka Leo) - 8/24-bit color, overlay planes, double-buffered, 3-D acceleration - 4/200 on-board bwtwo - P4 video (4/100 and 4/300): + bwtwo - black and white + cgthree - 8-bit color, unaccelerated + cgfour - 8-bit color, 1-bit overlay, unaccelerated + cgsix - 8-bit color, accelerated + cgeight - 24-bit color, 1-bit overlay, unaccelerated - VME video (sun4): + cgtwo - 8-bit color, unaccelerated + cgthree - 8-bit color, unaccelerated + cgsix - 8-bit color, accelerated * Ethernet adapters: - on-board AMD Lance Ethernet (le) - SBus AMD Lance Ethernet cards (le) - SBus cards containing both AMD Lance le and esp SCSI (le) - on-board Intel 82586 Ethernet on 4/100 and 4/200 (ie) - VME Intel 82586 Ethernet cards (ie) - SBus 10/100Mbit qec+be found on Sun FastEthernet cards (SUNW,501-2450) (be) - SBus Quad 10/100Mbit qec+qe found on Sun Quad Ethernet cards (SUNW,501-2062) (qe) - SBus 10/100MBit hme Ethernet cards (hme) [*] - SBus 10/100MBit SunSwift SUNW,fas Ethernet+SCSI cards (hme) [*] - SBus Quad 10/100MBit hme and qfe Ethernet cards (hme) [*] [*] Not supported in sun4c-class machines due to PROM limitations. * SCSI controllers: - on-board SCSI controller (sun4c, sun4m, and 4/300) (esp) - SBus SCSI controllers (including 3rd party compatible boards) (esp) - SBus cards containing both AMD Lance le and esp SCSI (esp) - SBus SUNW,fas Ethernet+SCSI cards (esp) [*] - VME "SUN-3"/"si" SCSI controller (interrupt driven DMA) (si) - 4/110 "SCSI weird" on-board controller (polled DMA) (sw) - QSP/ISP SCSI controllers (i.e. "PTI,ptisp", "ptisp", "SUNW,isp" and "QLGC,isp") (isp) [*] Not supported in sun4c-class machines due to PROM limitations. * SMD and other disk controllers: - Xylogics 7053 VME SMD disk controller (xd) - Xylogics 450/451 VME SMD disk controller (xy) * PC Cards (PCMCIA): - PCMCIA Controllers: + Sun SBus PCMCIA bridge (stp) + Tadpole PCMCIA controller (tslot) - Wireless Ethernet adapters (wi) + Intersil PRISM-2-3 based IEEE 802.11b Compact Flash adapters (will be detected as PCMCIA adapters) AmbiCom WL1100C-CF ASUS WL-110 Belkin F5D6060 (version 1) Buffalo AirStation D-Link DCF-660W ELSA XI800 Linksys WCF12 Netgear MA701 Pretec Compact WLAN OC-WLBXX-A Senao NL-2511CF + 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 - NE2000-based Ethernet Adapters 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 - 3Com EtherLink LAN PC Cards 3Com 3C556, 3C562 3Com 3C574TX, 3C[CX]FE574BT 3Com 3C589, 3C589B, 3C589C, 3C589D, 3C589E * Miscellaneous: - SBus Expansion Subsystem (SUNW,xbox) (xbox) - Force FGA5000 VME/SBus bridge (fga) - Force system configuration registers (scf) - Force flash memory (flash) - Tadpole microcontroller (power/system control) (tctrl) - Prestoserve NVRAM Sbus cards (limited support) (presto) OpenBSD/sparc 4.1 does NOT run on these machines (yet): - Sun 4/400 Lacking support for the I/O cache, and related Ethernet problems. - sun4d -- SPARCcenter 2000, SPARCserver 1000 XDBus and multiprocessor support issues. - sun4u (UltraSPARCs) These machines are supported by the OpenBSD/sparc64 port. - clones that are significantly different from the Sun systems (e.g. K-Bus based Solbourne) Hardware that we do NOT currently support, but get many questions about: * Serial Cards: - VME mti 16-port serial card - VME alm2 16-port serial card - VME mcp 4-port serial card (or is it 8-port) * Disk Controllers: - VME "sc" SCSI controller - VME IPI controller * Framebuffers: - VME cgfive, 8-bit color, 1-bit overlay, double-buffered, unaccelerated without GP/GP2 - VME cgnine, 24-bit color, 1-bit overlay, double-buffered, unaccelerated without GP/GP2 - VME GP/GP2 Graphics Processor (drives a cgfive or cgnine) - SBus cgeight, 24-bit color, unaccelerated - SBus GT, 24-bit color, 8-bit color, overlay planes, double-buffered, 3-D acceleration (aka "Graphics Tower") * On-board Audio and ISDN This is present on some sun4m systems (LX, LC, SPARCstation 10/20) * Multiple Processors/Modules in sun4m systems OpenBSD will not currently boot on some machines with multiple processors. You must remove the extra CPUs. * SBus SUNW,bpp (parallel port) * SBus FDDI cards The supplied GENERIC kernel is the best attempt at a configuration that works on the widest range of machines (sun4, sun4c, and sun4m). 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 Not all methods are supported on all SPARC Systems and some of them work only with the floppy or the miniroot installation. 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. However, not all SPARC systems support booting from CD-ROM, and the current boot image is only known to work on sun4c and sun4m architecture workstations. 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, tape, 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 or onto a SCSI tape. 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 4.1/sparc 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 "floppy41.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=floppy41.fs of=/dev/rfd0c bs=36b and, under Solaris: dd if=floppy41.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=floppy41.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 floppy installation image "floppy41.fs" or the miniroot "miniroot41.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 use 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=floppy41.fs of=/dev/rsd0b bs=36b - or - dd if=miniroot41.fs of=/dev/rsd0b bs=36b and under Solaris: dd if=floppy41.fs of=/dev/rdsk/c0t0d0s1 bs=36b - or - dd if=miniroot41.fs of=/dev/rdsk/c0t0d0s1 bs=36b 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 SPARC, but it is important to understand that the bootable image installed this way includes a "disk label" which can wipe out any pre-existing disk labels or partitioning for the drive. The floppy image is used only for booting, and can be placed in a partition that will be overwritten during the install process, since it actually runs off a ram-disk image in the kernel. In contrast the miniroot is a normal unix root filesystem and you must place it in a partition that will not be overwritten until you've completed the installation process. To copy the floppy image to the whole disk, overwriting labels: Under SunOS: dd if=floppy41.fs of=/dev/rsdXc bs=36b and under Solaris: dd if=floppy41.fs of=/dev/rdsk/c0tXd0s2 bs=36b Two notes - X should be replaced by the unit number of the target disk, which is most likely *not* the disk/partition that's your current root partition. Again names may vary depending on the OS involved. Second, after doing this, the disklabel will be one that would be appropriate for a floppy, i.e. one partition of 2880 blocks, and you'll probably want to change that later on. To copy the floppy image to the hard disk, preserving SunOS, Solaris, NetBSD or OpenBSD labels: Under SunOS: dd if=floppy41.fs of=/dev/rsdXc bs=1b skip=1 seek=1 and Solaris: dd if=floppy41.fs of=/dev/rdsk/c0tXd0s2 \ bs=1b skip=1 seek=1 You need to be sure that your version of dd(1) supports the skip and seek operands, otherwise you can try a technique like: dd if=/dev/rsdXc of=/tmp/label bs=1b count=1 dd if=floppy41.fs of=/dev/rsdXc bs=36b dd if=/tmp/label of=/dev/rsdXc bs=1b count=1 In either case, you've created a situation where the disk label and the filesystem information don't agree about the partition size and geometry, however the results will be usable. 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 man41.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 (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=bsd.rd obs=8k conv=sync dd of=${TAPE} if=boot obs=8k conv=sync fi for file in base etc comp game man misc xbase xetc xfont xserv xshare do dd if=${file}41.tgz of=${TAPE} obs=8k conv=sync done tar cf ${TAPE} bsd mt -f ${TAPE} offline # end of script And then: cd .../4.1/sparc 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.1/sparc 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 "base41" set somewhere in your file system. It is recommended that you upgrade the other sets, as well. Preparing your System for OpenBSD Installation: ----------------------------------------------- Before you start you might need to consider your disk configuration to sort out a quirk in SCSI-ID to SD-UNIT mapping that exists on Sun SPARCstations. Upon leaving the factory, SunOS and the OpenBOOT ROM map according to this table: SCSI-ID -> SunOS SD-UNIT 0 sd3 1 sd1 2 sd2 3 sd0 4 sd4 5 sd5 6 sd6 Unlike SunOS and the OpenBOOT ROM, a generic OpenBSD kernel numbers SCSI drives sequentially as it finds them. The drive with the lowest SCSI-ID will be called sd0, the next one sd1, etc. To ease the installation process, two OpenBSD kernels are provided in the installation sets. The default OpenBSD kernel (bsd) is set up to use the OpenBSD mapping, while a special kernel (bsd.scsi3) is set up to match the Sun mapping above by hard-wiring SCSI-ID#3 to sd0 and SCSI-ID#0 to sd3. The remaining drives will be dynamically mapped to other sd* numbers. This is mostly a non-issue if you have only one drive on your system, but can get confusing if you have multiple drives. If you plan to eliminate SunOS altogether it may be best to correct the SCSI-IDs of your drives, while if you plan to leave SunOS installed, it may be better to install OpenBSD on a drive with SCSI-ID 1 or 0. Older OpenBoot proms (versions 1.x) provide an environment variable, sd-targets, that controls the drive<->SCSI-ID mapping; you can change this to reflect the natural ordering or just set the boot related variables to boot from the correct drive, whatever the numbering. Its default-value is ``31204567'', which means unit 0 and 3 are exchanged. To revert to the ``normal'' behaviour, enter the following command: ok setenv sd-targets 01234567 NOTE: if you elect to build a custom kernel you may want to "hardwire" the SCSI-IDs to sd0->SCSI-ID 0 or your desired scheme, this helps prevent accidents if you change the SCSI bus configuration or a drive is down. Your OpenBOOT ROM may need some setup. If you are running OpenBSD on a sun4c, or sun4m system, the ROM must be set to "new" command mode. If your sun4c or sun4m machine comes up and gives you a `>' prompt instead of `ok', type: >n ok setenv sunmon-compat? false ok This is needed because OpenBSD relies on the behaviour of the "new" command mode. OpenBSD will not boot correctly on sun4c or sun4m systems that are not running in "new" command mode. The sun4 systems such as the 4/110, 4/200, and 4/300 system do not have a "new" command mode, and will work fine as-is. Also, you cannot use the security modes of the SPARC OpenBOOT ROM. Make sure that the ROM security modes are disabled: ok setenv security-mode none 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) command: # eeprom 'auto-boot?=true' Please note that while OpenBSD and SunOS 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 SunOS environments on the same system. If the OpenBSD fsck(8) utility is used on a SunOS filesystem, it will set OpenBSD "clean flags" and BSD4.4 summary fields in the superblock. SunOS does *not* like this and you will have to do a "fsck -b 32" under SunOS to access an alternate superblock to repair the filesystem. You should always specify SunOS filesystem with a "pass number" of 0 in their /etc/fstab entry to prevent this, and preferably mount them "RO". If SunOS 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 SunOS 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 and SunOS, but they will only see the first 8 partitions and you may "lose" information about the extended partitions. OpenBSD and Sun BSD 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 SunOS bootblocks, but remember that OpenBSD bootblocks must be installed with OpenBSD installboot and SunOS bootblocks with SunOS installboot. 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. If the disks connected to your machine are SMD disks, it is recommended that you know their geometry, 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 miniroot that can be booted off your local disk's swap partition. The normal way is to use the OpenBSD CD-ROM, or the bootable CD-ROM mini image, or an installation floppy, or an installation tape, depending on your hardware. If your SPARC 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 SunOS or Solaris system, using the system tools, as well as gunzip (and gnu tar on SunOS); see ``Installing from SunOS'' or ``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 SunOS 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. Sun PROM monitor commands and setup differ considerably depending on the system architecture and age; you may needed to reference the PROM monitor manual for your system for details. There are four main cases: sun4 (older servers, deskside workstations): prompt is a ">", boot command is "b", uses sd(c,s,p) syntax with s defined as scsi-unit*8+lun in hex OpenBoot Version 1 (newer servers, desktop workstations): prompt is "ok", boot command is "boot" uses sd(c,s,p) syntax with s defined as scsi-unit. OpenBoot Version 2 (newer servers, desktop workstations): prompt is "ok", boot command is "boot" uses diskn:p syntax. OpenBoot Version 2 (certain newer desktop workstations): prompt is "ok", boot command is "boot" uses diskn syntax unless booting from a non-standard partition, in which case: boot /sbus/esp/sd@t,0:p bsd (where "t" is the scsi target, and "p" is the partition. examples would be t="3" and p="b") If you expect your workstation to have an OpenBoot Prom but get a ">", enter the "n" command to enter the "new command mode". You can set this as the default by doing a "setenv sunmon-compat? false" command, followed by a "reset" command. Note that OpenBoot Proms also do the Sun SCSI-ID shuffle for disks; this is described elsewhere in some detail. For the purposes of this section, drive 0 refers to the internal or first SCSI drive, which usually has a SCSI-ID of 3. Booting from Floppy Disk installation media: ok boot fd()bsd # for version 1 OpenBOOT ROMs ok boot floppy bsd # for version 2 OpenBOOT ROMs This will cause the kernel contained in the floppy to be booted. Booting from CD-ROM installation media: > b sd(,30,0)4.1/sparc/bsd.rd # for Sun4 monitors* # (not working currently) ok boot sd(,6,0)4.1/sparc/bsd.rd # for version 1 OpenBOOT ROMs ok boot cdrom 4.1/sparc/bsd.rd # for version 2 OpenBOOT ROMs 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. Not all sparc systems support bootable CD-ROM and the current boot image is only known to work on sun4c and sun4m architectures. If it does not work, you'll have to create a boot floppy or bootable hard disk using the instructions under preparing boot media. Booting from SCSI disk (miniroot or floppy image): Boot the miniroot by typing the appropriate command at the PROM: > b sd(,,1)bsd # for sun4 monitors* ok boot sd(,,1)bsd # for version 1 OpenBOOT ROMs ok boot disk:b bsd # for version 2 OpenBOOT ROMs ok boot /sbus/esp/sd@3,0:b bsd # for version 2 OpenBOOT ROMs # that won't take disk:p syntax. If you've loaded the miniroot onto some other disk than the default drive 0, modify the boot specifier accordingly, keeping in mind the drive vs. SCSI-ID shuffling and partition a=0, b=1... > b sd(0,10,1)bsd # example - scsi target 2 on sun4 monitors* ok boot sd(0,3,1)bsd # example - scsi target 0 on v1 OpenBOOT ROM ok boot disk3:b bsd # example - scsi target 0 on v2 OpenBOOT ROM ok boot /sbus/esp/sd@0,0:b bsd # example - scsi target 0 on v2 # OpenBOOT ROM that won't take # disk:p syntax. (*) for sun4 this is scsi-target*8+scsi-lun (usually 0) expressed in hex... Booting from SCSI tape: Boot the miniroot by typing the appropriate command at the PROM: > b st(,,1) # for sun4 monitors # (not working currently) ok boot st(,,1) # for version 1 OpenBOOT ROMs ok boot tape:1 # for version 2 OpenBOOT ROMs ok boot /sbus/esp/st@4,0:1 # for version 2 OpenBOOT ROMs # that won't take tape:n syntax. The above instructions assume your tape drive is the default tape drive using SCSI ID 4. If your drive uses ID 5, modify the boot command accordingly: > b st(,28,1) # example - 2nd tape drive on sun4 monitors ok boot st(,5,1) # example - 2nd tape drive on v1 OpenBOOT ROM ok boot tape1:1 # example - 2nd tape drive on v2 OpenBOOT ROM ok boot /sbus/esp/st@5,0:1 # example - 2nd tape drive on v2 # OpenBOOT ROM that won't take # tape:n syntax 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. Depending on the PROM version in your machine, this command takes one of the following forms: > b le()bsd.rd # for sun4 monitors ok boot le()bsd.rd # for version 1 OpenBOOT ROMs ok boot net bsd.rd # for version 2 OpenBOOT ROMs Installing using the Floppy, CD-ROM, tape, 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 disks name and geometry. Its name will be something like "sd0" for SCSI drives, and "xd0" or "xy0" for SMD drives. As mentioned above, you will need your disks geometry (which will be printed on a line beginning with its name) when creating OpenBSD partitions. You will also need to know the device name to tell the install tools what disk to install on. If you cannot read the messages as they scroll by, do not worry -- you can get at this information later inside the install program. You will next be asked for your terminal type. 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. 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". 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 4.1 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.1/sparc 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.1 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, unless you have created a bootable tape, in which case the number will be 2. 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 sparc this is "4.1/sparc". 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 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 "base41", "etc41", and "bsd" distribution sets. After completing an installation: Now try a reboot. (If needed, swap your SCSI IDs first.) The Sun monitor normally tries to load a file called "vmunix". On OpenBOOT ROM systems you can change it to load OpenBSD instead using the following commands: On version 1 OpenBOOT ROMs: >n ok setenv boot-from sd(0,0,0)bsd ok On version 2 OpenBOOT ROMs: ok setenv boot-file bsd ok setenv boot-device /sbus/esp/sd@0,0 On sun4 systems, you may not need to specify the boot file, as the OpenBSD boot blocks will look for "bsd" on the boot device by default. Congratulations, you have successfully installed OpenBSD 4.1. 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.1 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/sparc, 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 SunOS: You need a SunOS machine to install OpenBSD. You also need at least the following pieces: - the *.tgz files you want to install (as a minimum, base41.tgz and etc41.tgz) - gunzip (GNU gzip) SunOS binary - gtar (GNU tar) SunOS binary - a "/boot" file from a SunOS machine that matches your machine type (e.g. sun4m or sun4c) - an OpenBSD kernel, most likely "/bsd" All these pieces, except "/boot" and the GNU utilities, are supplied in the OpenBSD/sparc distribution. You need to format and partition the disk using SunOS (since OpenBSD/sparc uses SunOS disk labels.) Give yourself adequate partition sizes. Here is an example layout: partition size offset will be.. sd0a 80000 0 / sd0b 256000 80000 swap sd0c 4165271 0 `whole disk' sd0d 100000 436000 /var sd0f 100000 336000 /tmp sd0g 3229271 936000 /usr sd0h 400000 536000 /var/tmp Use SunOS to newfs the partitions which will have filesystems on them. (OpenBSD's filesystem format is almost identical to SunOS.) sunos# newfs /dev/rsd0a [... lots of output] Repeat for any other partition (in this example, /dev/rsd0d, /dev/rsd0f, /dev/rsd0g, /dev/rsd0h). 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 SunOS boot blocks do not understand the extended 4.4BSD filesystem format. Mount those partitions in a tree formation, under /mnt; ie: sunos# df Filesystem kbytes used avail capacity Mounted on [...] /dev/sd0a 38427 0 38427 0% /mnt /dev/sd0d 48249 0 48249 0% /mnt/var /dev/sd0f 48249 0 48249 0% /mnt/tmp /dev/sd0g 1564024 0 1564024 0% /mnt/usr /dev/sd0h 193536 0 193536 0% /mnt/var/tmp Place a standard SunOS "boot" program in /mnt (your new root partition), and use the SunOS command "installboot" to make it work. The installboot man page says to do something like this: sunos# cp /usr/mdec/sdboot /mnt/boot sunos# sync; sync sunos# /usr/mdec/installboot -vlt /mnt/boot /usr/mdec/bootsd /dev/rsd2a You can now extract the provided "*.tgz" files onto your disk. sunos# ls -FC base41.tgz comp41.tgz man41.tgz xfont41.tgz bsd etc41.tgz misc41.tgz xserv41.tgz bsd.scsi3 game41.tgz xbase41.tgz sunos# gunzip < base41.tgz | (cd /mnt; gtar xvpf -) [...] for each set And finally copy an OpenBSD kernel (either bsd or bsd.scsi3) onto your disk. sunos# cp bsd.scsi3 /mnt/bsd The GNU gunzip and gtar programs are not distributed as part of SunOS, but may be present in your /usr/local/bin. If not, you will need to obtain them from a GNU archive and install before proceeding. The OpenBSD tar files are in the "new format" that includes directory information, and the standard SunOS tar will not extract from them successfully. 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 then customize your installation. 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, base41.tgz and etc41.tgz) - gunzip (GNU gzip) Solaris binary - a boot block file from a Solaris machine that matches your machine type, for ufs filesystem, such as /usr/platform/`uname -i`/lib/fs/ufs/bootblk - an OpenBSD kernel, most likely "/bsd" All these pieces, except the boot block and the GNU utilities, are supplied in the OpenBSD/sparc distribution. You need to format and partition the disk using Solaris (since OpenBSD/sparc 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 block 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 /usr/platform/`uname -i`/lib/fs/ufs/bootblk /mnt/bootblk 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 base41.tgz comp41.tgz man41.tgz xfont41.tgz bsd etc41.tgz misc41.tgz xserv41.tgz bsd.scsi3 game41.tgz xbase41.tgz solaris# gunzip < base41.tgz | (cd /mnt; tar xvpf -) [...] for each set And finally copy an OpenBSD kernel (either bsd or bsd.scsi3) onto your disk. solaris# cp bsd.scsi3 /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 then customize your installation. Net Boot or Diskless Setup Information: The set up is similar to SunOS 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 SPARCstation 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 followed by the machine's architecture, separated by a period. For example, a sun4c machine which has been assigned IP address 130.115.144.11, will make a TFTP request for `8273900B.SUN4C'. 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/sparc distribution. Unfortunately, it is necessary to install this file differently for sun4 and sun4c clients: the sun4 version needs to have its `a.out' header stripped off (otherwise the machine will crash), while the sun4c version must retain it (otherwise the PROM will complain). Here's an example to illustrate this whole mess: server# cd //usr/mdec if client is a sun4: server# set SKIP=1 server# set KARCH=SUN4 else server# set SKIP=0 server# set KARCH=SUN4C server# dd if=boot of=/tftpboot/boot.MACHINE.OpenBSD.$KARCH skip=$SKIP bs=32 server# cd /tftpboot server# ln -s boot.MACHINE.OpenBSD.$KARCH 8273900B.$KARCH 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 miniroot41.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 `base41.tgz' and `etc41.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 base41.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/sun4.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 4.1 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.1 from a previous version, start with the general instructions in the section "Installing OpenBSD". Boot from the 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 ``etc41.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 etc41.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.1/packages/sparc 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.1/packages/sparc/ # # 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.1/packages/sparc/ 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.1/packages/sparc/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 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