INSTALLATION NOTES for OpenBSD/sgi 5.2 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. 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 5.2 release is available on the web at http://www.OpenBSD.org/52.html. OpenBSD/sgi runs on several SGI workstations and servers built upon 64-bit MIPS processors (R4000 and up), including the Indigo, Indigo 2, Indy, O2, Octane, Origin/Onyx and Fuel/Tezro families. Sources of OpenBSD: ------------------- This is a list of currently known FTP and HTTP servers at the time of the 5.2 release. For a more recent list, please refer to http://www.OpenBSD.org/ftp.html Argentina: http://openbsd.org.ar/pub/OpenBSD (Buenos Aires) ftp://ftp.openbsd.org.ar/pub/OpenBSD (Buenos Aires) Australia: http://mirror.internode.on.net/pub/OpenBSD (Adelaide) ftp://mirror.internode.on.net/pub/OpenBSD (Adelaide) http://mirror.aarnet.edu.au/pub/OpenBSD (Brisbane) ftp://mirror.aarnet.edu.au/pub/OpenBSD (Brisbane) http://ftp.iinet.net.au/pub/OpenBSD (Perth) ftp://ftp.iinet.net.au/pub/OpenBSD (Perth) http://mirror.as24220.net/pub/OpenBSD (Melbourne) ftp://mirror.as24220.net/pub/OpenBSD (Melbourne) Austria: http://ftp5.eu.openbsd.org/ftp/pub/OpenBSD (Vienna) ftp://ftp5.eu.openbsd.org/pub/OpenBSD (Vienna) http://ftp2.eu.openbsd.org/pub/OpenBSD (Vienna) ftp://ftp2.eu.openbsd.org/pub/OpenBSD (Vienna) Brazil: http://openbsd.locaweb.com.br/pub/OpenBSD (Sao Paulo) ftp://openbsd.locaweb.com.br/pub/OpenBSD (Sao Paulo) Bulgaria: http://mirror.telepoint.bg/OpenBSD (Sofia) Canada: http://ftp.OpenBSD.org/pub/OpenBSD (Alberta) ftp://ftp.OpenBSD.org/pub/OpenBSD (Alberta) Costa Rica: http://mirrors.ucr.ac.cr/OpenBSD ftp://mirrors.ucr.ac.cr/OpenBSD Denmark: http://ftp.openbsd.dk/pub/OpenBSD (Aalborg) ftp://ftp.openbsd.dk/pub/OpenBSD (Aalborg) Estonia: http://ftp.aso.ee/pub/OpenBSD (Tallinn) ftp://ftp.aso.ee/pub/OpenBSD (Tallinn) France: http://ftp.fr.openbsd.org/pub/OpenBSD (Paris) ftp://ftp.fr.openbsd.org/pub/OpenBSD (Paris) http://ftp.arcane-networks.fr/pub/OpenBSD (Paris) ftp://ftp.arcane-networks.fr/pub/OpenBSD (Paris) http://ftp2.fr.openbsd.org/pub/OpenBSD (Paris) ftp://ftp2.fr.openbsd.org/pub/OpenBSD (Paris) Germany: http://openbsd.cs.fau.de/pub/OpenBSD (Erlangen) ftp://openbsd.cs.fau.de/pub/OpenBSD (Erlangen) http://ftp.spline.de/pub/OpenBSD (Berlin) ftp://ftp.spline.de/pub/OpenBSD (Berlin) ftp://ftp-stud.fht-esslingen.de/pub/OpenBSD (Esslingen) http://ftp.bytemine.net/pub/OpenBSD (Oldenburg) ftp://ftp.bytemine.net/pub/OpenBSD (Oldenburg) http://ftp.halifax.rwth-aachen.de/openbsd (Aachen) ftp://ftp.halifax.rwth-aachen.de/pub/OpenBSD (Aachen) http://artfiles.org/openbsd (Hamburg) Greece: http://ftp.cc.uoc.gr/mirrors/OpenBSD (Heraklion) ftp://ftp.cc.uoc.gr/mirrors/OpenBSD (Heraklion) Hungary: http://ftp.fsn.hu/pub/OpenBSD (Budapest) ftp://ftp.fsn.hu/pub/OpenBSD (Budapest) Ireland: http://ftp.heanet.ie/pub/OpenBSD (Dublin) ftp://ftp.heanet.ie/pub/OpenBSD (Dublin) Japan: http://ftp.jaist.ac.jp/pub/OpenBSD (Ishikawa) ftp://ftp.jaist.ac.jp/pub/OpenBSD (Ishikawa) http://www.ftp.ne.jp/OpenBSD (Saitama) ftp://ftp.kddilabs.jp/OpenBSD (Saitama) Korea: http://mirror.yongbok.net/OpenBSD (Seoul) ftp://mirror.yongbok.net/pub/OpenBSD (Seoul) The Netherlands: http://ftp.nluug.nl/pub/OpenBSD (Utrecht) ftp://ftp.nluug.nl/pub/OpenBSD (Utrecht) http://ftp.bit.nl/pub/OpenBSD (Ede) ftp://ftp.bit.nl/pub/OpenBSD (Ede) Norway: http://baksmell.netrunner.nu/pub/OpenBSD (Trondheim) ftp://baksmell.netrunner.nu/pub/OpenBSD (Trondheim) Pakistan: http://stingray.cyber.net.pk/pub/OpenBSD (Karachi) ftp://stingray.cyber.net.pk/OpenBSD (Karachi) Poland: http://piotrkosoft.net/pub/OpenBSD (Oswiecim) ftp://ftp.piotrkosoft.net/pub/OpenBSD (Oswiecim) http://ftp.icm.edu.pl/pub/OpenBSD (Warszawa) ftp://ftp.icm.edu.pl/pub/OpenBSD (Warszawa) Russia: http://mirror.corbina.net/pub/OpenBSD (Moscow) ftp://mirror.corbina.net/pub/OpenBSD (Moscow) Saudi Arabia: http://mirrors.isu.net.sa/pub/ftp.openbsd.org (Riyadh) ftp://mirrors.isu.net.sa/pub/ftp.openbsd.org (Riyadh) Slovenia: http://www.obsd.si/pub/OpenBSD (Ljubljana) ftp://ftp.obsd.si/pub/OpenBSD (Ljubljana) South Africa: http://mirror.is.co.za/mirror/ftp.openbsd.org (Johannesburg) ftp://ftp.is.co.za/mirror/ftp.openbsd.org (Johannesburg) Spain: http://mirror.cdmon.com/pub/OpenBSD (Barcelona) ftp://mirror.cdmon.com/pub/OpenBSD (Barcelona) Sweden: http://ftp.eu.openbsd.org/pub/OpenBSD (Stockholm) ftp://ftp.eu.openbsd.org/pub/OpenBSD (Stockholm) http://ftp.netbsd.se/OpenBSD (Stockholm) Switzerland: http://mirror.switch.ch/ftp/pub/OpenBSD (Zurich) ftp://mirror.switch.ch/pub/OpenBSD (Zurich) http://ftp.ch.openbsd.org/pub/OpenBSD (Zurich) ftp://ftp.ch.openbsd.org/pub/OpenBSD (Zurich) Turkey: ftp://ftp.ulak.net.tr/OpenBSD United Kingdom: http://www.mirrorservice.org/pub/OpenBSD (Kent) ftp://ftp.mirrorservice.org/pub/OpenBSD (Kent) http://mirror.bytemark.co.uk/OpenBSD (Manchester) ftp://mirror.bytemark.co.uk/OpenBSD (Manchester) USA: http://ftp5.usa.openbsd.org/pub/OpenBSD (Redwood City, CA) ftp://ftp5.usa.openbsd.org/pub/OpenBSD (Redwood City, CA) http://ftp3.usa.openbsd.org/pub/OpenBSD (Boulder, CO) ftp://ftp3.usa.openbsd.org/pub/OpenBSD (Boulder, CO) http://mirror.team-cymru.org/pub/OpenBSD (Chicago, IL) ftp://mirror.team-cymru.org/pub/OpenBSD (Chicago, IL) http://mirror.planetunix.net/pub/OpenBSD (Chicago, IL) ftp://mirror.planetunix.net/pub/OpenBSD (Chicago, IL) http://filedump.se.rit.edu/pub/OpenBSD (Rochester, NY) ftp://filedump.se.rit.edu/pub/OpenBSD (Rochester, NY) http://openbsd.mirror.frontiernet.net/pub/OpenBSD (Rochester, NY) ftp://openbsd.mirror.frontiernet.net/pub/OpenBSD (Rochester, NY) http://ftp.lambdaserver.com/pub/OpenBSD (Chicago, Illinois) ftp://ftp.lambdaserver.com/pub/OpenBSD (Chicago, Illinois) http://openbsd.mirrors.hoobly.com (Pittsburgh, PA) http://mirror.ece.vt.edu/pub/OpenBSD (Blacksburg, VA) http://mirror.servihoo.net/pub/OpenBSD (Kansas City, MO) ftp://mirror.servihoo.net/pub/OpenBSD (Kansas City, MO) http://openbsd.mirrors.pair.com (Pittsburgh, PA) ftp://openbsd.mirrors.pair.com (Pittsburgh, PA) http://mirrors.gigenet.com/pub/OpenBSD (Arlington Heights, IL) ftp://mirrors.gigenet.com/pub/OpenBSD (Arlington Heights, IL) http://mirror.esc7.net/pub/OpenBSD (Dallas, TX) ftp://mirror.esc7.net/pub/OpenBSD (Dallas, TX) http://openbsd.mirrorcatalogs.com/pub/OpenBSD (Denver, CO) ftp://openbsd.mirrorcatalogs.com/pub/OpenBSD (Denver, CO) http://mirrors.nycbug.org/pub/OpenBSD (New York City, NY) ftp://mirrors.nycbug.org/pub/OpenBSD (New York City, NY) http://mirrors.syringanetworks.net/pub/OpenBSD (Boise, ID) ftp://mirrors.syringanetworks.net/pub/OpenBSD (Boise, ID) 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 5.2 Release Contents: ----------------------------- The OpenBSD 5.2 release is organized in the following way. In the .../5.2 directory, for each of the architectures having an OpenBSD 5.2 binary distribution, there is a sub-directory. The sgi-specific portion of the OpenBSD 5.2 release is found in the "sgi" subdirectory of the distribution. That subdirectory is laid out as follows: .../5.2/sgi/ INSTALL.sgi Installation notes; this file. SHA256 Output of the sum(1) program using the option -a sha256, usable for verification of the correctness of downloaded files. *.tgz sgi binary distribution sets; see below. bsd.IP22 A stock GENERIC-IP22 sgi kernel for IP22 class machines, which will be installed on such systems during the install. bsd.IP27 A stock GENERIC-IP27 sgi kernel for IP27 and IP35 class machines, which will be installed on such systems during the install. bsd.IP28 A stock GENERIC-IP28 sgi kernel for IP28 class machines, which will be installed on such systems during the install. bsd.IP30 A stock GENERIC-IP30 sgi kernel for IP30 class machines, which will be installed on such systems during the install. bsd.IP32 A stock GENERIC-IP32 sgi kernel for IP32 class machines, which will be installed on such systems during the install. bsd.IP30.mp A stock GENERIC-IP30.MP sgi kernel for IP30 class machines, with support for multiprocessor systems, which can be used instead of the GENERIC-IP30 kernel after the install. bsd.rd.IP22 A RAMDISK-IP22 kernel; the embedded filesystem contains the installation tools. Used for installation and upgrades. bsd.rd.IP27 A RAMDISK-IP27 kernel; the embedded filesystem contains the installation tools. Used for installation and upgrades. bsd.rd.IP28 A RAMDISK-IP28 kernel; the embedded filesystem contains the installation tools. Used for installation and upgrades. bsd.rd.IP30 A RAMDISK-IP30 kernel; the embedded filesystem contains the installation tools. Used for installation and upgrades. bsd.rd.IP32 A RAMDISK-IP32 kernel; the embedded filesystem contains the installation tools. Used for installation and upgrades. cd52.iso A miniroot filesystem image suitable to be used as a bootable CD-ROM image, but will require the base and X sets be found via another media or network; otherwise similar to the bsd.rd* images above. boot32 A 32-bit ELF boot block for IP32 systems; will be installed into the ``volume header'' of the boot disk. boot64 A 64-bit relocatable ELF boot block for IP27, IP28, IP30 and IP35 systems; will be installed into the ``volume header'' of the boot disk. bootecoff A 32-bit ECOFF boot block for IP22 systems, also used to boot ELF kernels over the network on ELF-unaware PROM; will be installed into the ``volume header'' of the boot disk. The OpenBSD/sgi binary distribution sets contain the binaries which comprise the OpenBSD 5.2 release for sgi systems. There are ten binary distribution sets. The binary distribution sets can be found in the "sgi" subdirectory of the OpenBSD 5.2 distribution tree, and are as follows: base52 The OpenBSD/sgi 5.2 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. [ 54.4 MB gzipped, 187.6 MB uncompressed ] comp52 The OpenBSD/sgi Compiler tools. All of the tools relating to C, C++ and Objective-C 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. [ 51.6 MB gzipped, 197.8 MB uncompressed ] etc52 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.) [ 512.3 KB gzipped, 1.5 MB uncompressed ] game52 This set includes the games and their manual pages. [ 2.6 MB gzipped, 6.3 MB uncompressed ] man52 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. [ 9.2 MB gzipped, 35.7 MB uncompressed ] xbase52 This set includes the base X distribution. This includes programs, headers and libraries. [ 10.9 MB gzipped, 39.2 MB uncompressed ] xetc52 This set includes the X window system configuration files that reside in /etc. It's the equivalent of etc52 for X. [ 71.2 KB gzipped, 274.2 KB uncompressed ] xfont52 This set includes all of the X fonts. [ 37.5 MB gzipped, 48.5 MB uncompressed ] xserv52 This set includes all of the X servers. [ 5.3 MB gzipped, 16.6 MB uncompressed ] xshare52 This set includes all text files equivalent between all architectures. [ 3.2 MB gzipped, 17.5 MB uncompressed ] OpenBSD System Requirements and Supported Devices: -------------------------------------------------- OpenBSD/sgi 5.2 runs on the following machine families: IP22 class machines: Indigo (R4x00 flavour) Indigo2, Challenge M (IP22) (R4x00 flavour) Indy, Challenge S (IP24) (all processor configurations are supported) IP27 class machines: Origin 200 IP28 class machines: POWER Indigo2 R10000 IP30 class machines: Octane Octane 2 IP32 class machines: O2 O2+ (both R50000/RM52xx/RM70000 and R10000/R12000 configurations are supported) IP35 class machines: Origin 3000 Origin 350, Onyx 350 Fuel Tezro Onyx 4 Supported devices include: - Ethernet Adapters built-in IP22/IP28 Seeq 80C03 Ethernet Controller (sq) built-in O2 Mace Ethernet Controller (mec) IOC3 Ethernet Controller (built-in on IP27, IP30 and some IP35) (iec) Broadcom BCM570x (a.k.a. Tigon3) based PCI adapters (bge) including: 3Com 3c996-SX 3Com 3c996B-T HP ProLiant NC7770 PCI-X Gigabit NIC Netgear GA302T SysKonnect SK-9D21 SysKonnect SK-9D41 Intel/DEC 21443 "Tulip" clones (dc) 3Com EtherLink III and Fast EtherLink III Ethernet (ep) Intel i8255x-based (fxp) including: Intel EtherExpress PRO/10+ Intel EtherExpress PRO/100, PRO/100B, and PRO/100+ Intel EtherExpress PRO/100+ "Management Adapter" Intel EtherExpress PRO/100 Dual Port Intel PRO/100 VE, PRO/100 VM, and PRO/100 S Myson Technology MTD8xx 3-in-1 Fast Ethernet (mtd) NE2000 compatible PCI Ethernet (ne) Alteon Tigon I and II Gigabit Ethernet (ti) Via Rhine based Ethernet (vr) 3Com EtherLink XL and Fast EtherLink XL (xl) - SCSI Host Adapters IP22/IP28 built-in WD33C93 (wdsc) O2 built-in Adaptec AIC-7880 (ahc) IP27/IP30/IP35 built-in QLogic ISP (isp) LSI Logic Fusion-MPT Message Passing Interface (mpi) 53C8xx-based SCSI (siop) - RS-232 devices on-board Z8530 compatible serial ports (zstty) on-board NS16550 compatible serial ports (com) - Universal Serial Bus (USB) Controllers and Devices USB Universal Host Controller (uhci) USB Open Host Controller (ohci) USB Ethernet adapters (aue, others untested) USB Generic Human Interface Devices (catch-all) (uhid) USB Hubs (uhub) USB Keyboards (ukbd) USB Mice (ums) USB Mass Storage devices, i.e., USB floppy drives and USB memory stick controllers (umass) USB Modems (umodem) USB Printers (ulpt) - Audio Devices O2 Moosehead A/V Board audio (mavb) - Video Devices Indigo Light (`Entry', `Starter') graphics (light) Indy, Indigo2 Newport (`XL', `XGE') graphics (newport) Indigo, Indy, Indigo2 Express (`XS', `XZ', `Elan', `Extreme') graphics (grtwo) O2 built-in Graphics Back End framebuffer (gbe) Indigo2, Octane Impact and ImpactSR graphics (impact) Octane 2, Fuel, Tezro VPro graphics (odyssey) - Input Devices Indigo keyboard and mouse (zskbd, zsms) Indigo2 and Indy onboard PS/2 controller (pckbc) O2 onboard PS/2 Controller (mkbc) Octane/Origin/Fuel/Tezro onboard PS/2 Controller (iockbc) PS/2 mice (pms) PS/2 keyboards (pckbd) USB keyboard and mice (already listed above) - Miscellaneous Devices Indy and Indigo2 power and volume buttons (panel) O2 and Octane ``soft'' power button (power) If your hardware is not listed above, there is currently no support for it in this release. Currently unsupported hardware include: - audio on IP22/IP28 (Iris Audio, HAL 2) and IP30 (RAD) - some IP27 and IP35 systems (Origin 2000, Onyx 2, Origin 300 and Onyx 300) - R8000 POWER Indigo 2 (IP26) - multiprocessor kernels are currently only supported on IP30 (Octane) systems Getting the OpenBSD System onto Useful Media: --------------------------------------------- Installation is supported from several media types, including: CD-ROM FFS partitions Tape Remote NFS partition FTP HTTP The steps necessary to prepare the distribution sets for installation depend on which method of installation you choose. Some methods require a bit of setup first that is explained below. The installation allows installing OpenBSD directly from FTP mirror sites over the internet, however you must consider the speed and reliability of your internet connection for this option. It may save much time and frustration to use ftp get/reget to transfer the distribution sets to a local server or disk and perform the installation from there, rather than directly from the internet. 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 xbase xetc xfont xserv xshare do dd if=${file}52.tgz of=${TAPE} obs=8k conv=osync done tar cf ${TAPE} bsd mt -f ${TAPE} offline # end of script And then: cd .../5.2/sgi 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). To install OpenBSD using a remote partition, mounted via NFS, you must do the following: NOTE: This method of installation is recommended only for those already familiar with using BSD network configuration and management commands. If you aren't, this documentation should help, but is not intended to be all-encompassing. Place the OpenBSD distribution sets you wish to install into a directory on an NFS server, and make that directory mountable by the machine on which you are installing or upgrading OpenBSD. This will probably require modifying the /etc/exports file of the NFS server and resetting its mount daemon (mountd). (Both of these actions will probably require superuser privileges on the server.) You need to know the numeric IP address of the NFS server, and, if the server is not on a network directly connected to the machine on which you're installing or upgrading OpenBSD, you need to know the numeric IP address of the router closest to the OpenBSD machine. Finally, you need to know the numeric IP address of the OpenBSD machine itself. Once the NFS server is set up properly and you have the information mentioned above, you can proceed to the next step in the installation or upgrade process. If you 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 "base52" 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 install your system, you should identify your system family and familiarize yourself with the ARCBios setup and how to run programs from the Command monitor prompt. Identifying your system: Due to significant design differences in SGI systems, OpenBSD needs to use different kernels, depending on the system family. There are currently five system families supported by OpenBSD: IP22 family: Indigo (R4x00 flavour) Indigo 2, Challenge M (R4x00 flavour) Indy, Challenge S IP27 family: Origin 200, Onyx 2 Origin 2000 IP28 family: POWER Indigo 2 R10000 IP30 family: Octane, Octane 2 IP32 family: O2, O2+ IP35 family: Origin 350, Onyx 350 Fuel Tezro Onyx 4 You should use the kernels (bsd and bsd.rd) with the IP suffix matching your family number, except for IP35 systems which use IP27 kernels. Accessing the Maintenance Console: When the system starts up, press the ESC key or use the mouse and click the ``stop for maintenance'' button. Once in the System Maintenance Menu, select '5' (or click the appropriate icon if you are using the graphics console) to go into the Command Monitor. If the internal disk with the lowest SCSI ID does not contain a valid Volume Header, but is bootable, the Maintenance Console will be entered by default. The first time the Maintenance Console is entered, it may be necessary to force a reset of the environment to its default settings by entering the ``resetenv'' command at the chevron prompt. If some variables have been set explicitly, this may disturb the normal OpenBSD boot process. Switching from serial to graphics console and vice versa: To change to serial console, go into the ARCBios Maintenance Console and change the ``console'' environment variable, and power-cycle the machine. >> setenv console d will select 8N1, no flow control, serial console on the first serial port (labeled ``(1)''), while >> setenv console g will select the graphics console. The speed of the serial console is controlled by the ``dbaud'' environment variable, and defaults to 9600 bps if this variable is not set. Not all graphics options are currently supported by OpenBSD. If your system is configured for graphics console but the kernel does not support your frame buffer, it will fallback to serial console on the first serial port. As of OpenBSD 5.2, the only unsupported graphics console devices are: - Infinite Reality (Kona) frame buffer on IP27/IP35 Onyx systems - Voyager (Ultimate Vision) frame buffer on IP35 Onyx 4 systems Switching from L1 console to serial console and vice versa: IP35 systems without a graphics console can have the PROM console output either on the L1 console serial port, or the regular serial port. The `console' command at the PROM prompt, can select between them: >> console sc will switch to the L1 serial port, while >> console ioc3 or >> console ioc4 will select the regular serial port, depending on the I/O board type. On Fuel systems, there is no external L1 serial port, so `console sc' should never be used on these machines. Origin 300 and 3000 families can switch between `sc' and `ioc3', while Origin 350 and 3500 families (including Tezro and Onyx 4) can switch between `sc' and `ioc4'. The OpenBSD kernel only supports serial console on the regular serial ports; if your PROM console is on the L1 port, the kernel console will nevertheless pick the first IOC3 or IOC4 serial port. Setting the environment: When setting up the system to boot from disk, the ``OSLoader'' environment variable will need to be changed. Its default value is ``sashARCS'', ``sash'' or ``sash64'', which is IRIX's standalone shell and loader. Set it to ``boot'', the name under which the OpenBSD boot loader has been installed. The kernel image loaded by default is specified in the ``OSLoadFilename'' variable, which defaults to ``unix''. To boot OpenBSD, set it to ``bsd''. To enable automatic booting of OpenBSD once the machine has passed its diagnostic tests, change the value of ``AutoLoad'' to ``Yes''. 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. There are several ways to install OpenBSD onto a disk. The easiest way in terms of preliminary setup is to use the OpenBSD ramdisk kernel that can be booted via BOOTP. The normal way is to use the bootable CD-ROM mini image. Booting over the network: First, a bootp or dhcpd server needs to be set up. The bootpd(8) or dhcpd(8) manual page on your server should provide detailed information on how to set up the server. The PROM, by default, will configure itself to use the IP address set in the `netaddr' environment variable. To force the PROM to always get an address from a bootp or dhcp server, clear the variable (`unsetenv netaddr') before attempting to boot from the network. Alternatively, you may want to make sure the value of this variable is correct. Note that, if the `netaddr' variable is unset, the PROM will initialize it to the address obtained from the bootp or dhcp server. The bootp or dhcp server needs to know the ethernet address of the system. On Indigo, Indigo2, Indy and O2 systems, this address can be found by using the ``printenv'' command in the Maintenance Console, looking for the ``eaddr'' variable. On other systems, or if this variable is missing, this address is ususally written on a factory sticker on the back of the machine. The server should also provide a tftp location, where the proper bsd.rd file should be available. IMPORTANT! Older PROM are unable to connect to a tftp server on a port number greater than 32767; if booting stalls almost immediately, it might be necessary to restrict the tftp server to only use 15-bit port numbers. This situation can be detected by running tcpdump on the tftp server, and looking for icmp `port unreachable' errors from the sgi system. The following PROM versions are known to exhibit this troublesome behaviour: - on Indigo: >> version PROM Monitor SGI Version 4.0.5G Rev B IP20, Nov 10, 1992 (BE) - on Indy: >> version PROM Monitor SGI Version 5.1 Rev B3 IP24 Sep 17, 1993 (BE) On the other hand, the following PROM versions are known to be unaffected by this problem: - on Indigo2: >> version PROM Monitor SGI Version 5.3 Rev C IP22 Oct 20, 1994 (BE) - on Indy: >> version PROM Monitor SGI Version 5.3 Rev B10 R4X00/R5000 IP24 Feb 12, 1996 (BE) Note that these lists do not pretend to be complete. If the server system runs OpenBSD, the following command can be used to enforce a safe port number: # sysctl net.inet.ip.portlast=32767 don't forget to restore the previous value of this sysctl after the troublesome system has booted. Once the server is set up, boot with the following command in the Maintenance Console: >> bootp()bsd.rd.IP32 (replacing `IP32' by the family name suitable for your machine). On IP22-class systems, or if the PROM complains about the file format, such as: >> bootp()bsd.rd.IP22 [...] Cannot load bootp()bsd.rd.IP22. Problem reading elf structure at offset -2004877312. Unable to execute bootp()bsd.rd.IP22 ... then this means that the PROM is too old to know about the ELF file format the OpenBSD kernel is provided in. In this case, the kernel needs to be booted from the ``bootecoff'' boot block, which has to be put on the tftp server as well, with: >> bootp()bootecoff bootp()bsd.rd.IP22 If the boot aborts early with a memory related error message, such as: >> bootp()bootecoff bootp()bsd.rd.IP22 [...] Cannot load bootp()bootecoff. Text start 0x80020f0, size 0xa030 doesn't fit in a FreeMemory area. Unable to execute bootp()/bootecoff ... then it is necessary to clean up after an earlier unsuccessful (or aborted) boot attempt. Just leave the PROM interactive mode with `exit', and at the maintenance menu, choose `Enter Command Monitor' again. Booting from CD-ROM installation media: NOTE: This method will not work on IP27 and IP35 class systems, which PROM expect a very specific CD-ROM layout. From the System Maintenance Menu, select '2' (or click on the appropriate icon if in graphics console) to Install System Software. If necessary, select the proper CD-ROM drive, and press enter to confirm your choice. Insert the installation CD-ROM (if you did not do so already) and press enter to boot the system. 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. If the system does not complain about being able to read the CD-ROM, but of not being able to load a particular file, you can nevertheless boot manually. This is the case on IP22 systems. To boot manually from the CD-ROM, select ``Enter Command Monitor'' at the menu, and invoke the bootloader and ramdisk image manually. For example, on an IP22 system, automatic boot may fail with: Cannot load scsi(1)cdrom(4)partition(8)sashARCS. Text start 0x10000, size 0xa120 doesn't fit in a FreeMemory area. Cannot load scsi(1)cdrom(4)partition(8)sashARCS -- not enough space. or: Cannot load scsi(1)cdrom(4)partition(8)sashARCS. Error 15 while loading scsi(1)cdrom(4)partition(8)sashARCS The name of the CD-ROM drive is then ``scsi(1)cdrom(4)'', and the manual boot command will be: >> scsi(1)cdrom(4)partition(8)bootecoff scsi(1)cdrom(4)partition(0)/bsd.rd.IP22 Note that this is a single commandline, the two paths should be separated with spaces. Installing the system: 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. The installation procedure is designed to gather as many information about your system setup as possible at the beginning, so that no human interaction is required as soon as the questions are over. The order of these questions might be quite disconcerting if you are used to other installation procedures, including older OpenBSD versions. 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 will occur, though). Boot your machine from the installation media as described above. It will take a while to load the kernel especially from a 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". 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. After the kernel is done initialization, 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. If you are connected with a serial console, you will next be asked for your terminal type. You should choose the terminal type from amongst those listed. (If your terminal type is xterm, just use vt220). If you are connected using a glass console, you will next be asked for your keyboard layout (the default being the US QWERTY layout). Depending on your keyboard type, not all international layouts may be supported; answering `?' (which, on QWERTY layouts, is the key to the left of the right `shift' key, shifted) will display a list of supported layouts. (If you do not need to change the keyboard layout, just press enter.) The first question you will be asked is the system hostname. Reply with the name of the system, without any domain part. You will now be given 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. The install program will give you a list of network interfaces you can configure. For each network interface you select to configure, you will be asked for: - the symbolic host name to use (except for the first interface setup, which will reuse the host name entered at the beginning of the installation). - the IPv4 settings: address and netmask. If the IP address should be obtained from a DHCP server, simply enter ``dhcp'' when asked for the address. - the IPv6 settings (address, prefix length, and default router). You may enter ``rtsol'' when asked for the address for the interface to configure automatically via router solicitation messages. After all interfaces have been configured, if there have been any IPv4 interfaces setup, you will be asked for the IPv4 default route. This step is skipped if you only have one IPv4 interface setup, and it is configured with DHCP. The install program will also ask you for your DNS domain name, and the domain name servers, unless this information has already been obtained from a DHCP server during interface setup. You will also be presented with an opportunity to do more manual configuration. If you accept, you will be dropped to a shell; when you are done, enter `exit' to return to the installation program. You will then be asked to enter the initial root password of the system, twice. Although the install program will only check that the two passwords match, you should make sure to use a strong password. As a minimum, the password should be at least eight characters long and a mixture of both lower and uppercase letters, numbers and punctuation characters. You will then be asked whether you want to start sshd(8) by default, as well as ntpd(8). If you choose to start ntpd(8), you will be asked for your ntp server; if you don't have any preferred ntp server, press enter to confirm the default setting of using the pool.ntp.org servers. You will now be given the possibility to setup a user account on the forthcoming system. This user will be added to the `wheel' group. Enter the desired login name, or `n' if you do not want to add a user account at this point. Valid login names are sequences of digits and lowercase letters, and must start with a lowercase letter. If the login name matches this criteria, and doesn't conflict with any of the administrative user accounts (such as `root', `daemon' or `ftp'), you will be prompted with the users descriptive name, as well as its password, twice. As for the root password earlier, the install program will only check that the two passwords match, but you should make sure to use a strong password here as well. If you have chosen to setup a user account, and you had chosen to start sshd(8) on boot, you will be given the possibility to disable sshd(8) logins as root. The installation program will now tell you which disks it can install on, and ask you which it should use. Reply with the name of your root disk. You will the be asked if you want to use DUID notation in /etc/fstab, instead of traditional device names. You are strongly advised to use DUIDs, as they allow you to move your disks to different controllers, or change their bus identifiers, without having to modify /etc/fstab every time your configuration changes. Next the disk label which defines the layout of the OpenBSD partitions must be set up. Each file system you want will require a separate partition. You will be proposed a default partition layout, trying to set up separate partitions, disk size permitting. You will be given the possibility to either accept the proposed layout, or edit it, or create your own custom layout. These last two choices will invoke the disklabel(8) interactive editor, allowing you to create your desired layout. Within the editor, you will probably start out with only the 'c' partition of fstype 'unused' that represents the whole disk. This partition can not be modified. You must create partition 'a' as a native OpenBSD partition, i.e. one with "4.2BSD" as the fstype, to hold the root file system. In addition to partition 'a' you should create partition 'b' with fstype "swap", and native OpenBSD partitions to hold separate file systems such as /usr, /tmp, /var, and /home. You will need to provide a mount point for all partitions you define. Partitions without mount points, or not of 4.2BSD fstype, will neither be formatted nor mounted during the installation. For quick help while in the interactive editor, enter '?'. The `z' command (which deletes all partitions and starts with a clean label), the `A' command (which performs the automatic partition layout) and the `n' command (to change mount points) are of particular interest. Although the partitions position and size are written in exact sector values, you do not need a calculator to create your partitions! Human-friendly units can be specified by adding `k', `m' or `g' after any numbers to have them converted to kilobytes, megabytes or gigabytes. Or you may specify a percentage of the disk size using `%' as the suffix. Enter 'M' to view the entire manual page (see the info on the ``-E'' flag). To exit the editor enter 'q'. No partitions should overlap with the SGI Volume Header, which by default will use the first 3134 sectors. Additionally, the 'a' partition must be the first partition on the disk, immediately following the SGI Volume Header. If the default Volume Header size is used, the 'a' partition should be located at offset 3135. If the 'a' partition is not located immediately after the Volume Header the boot loader will not be able to locate and load the kernel. After the layout has been saved, new filesystems will be created on all partitions with mount points. This will DESTROY ALL EXISTING DATA on those partitions. After configuring your root disk, the installer will return to the list of available disks to configure. You can choose the other disks to use with OpenBSD in any order, and will get to setup their layout similarly to the root disk above. However, for non-root disks, you will not be proposed a default partition layout. When all your disks are configured, simply hit return at the disk prompt. 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, CD-ROM, tape, NFS or a local disk partition. To install via FTP or HTTP: To begin an FTP or HTTP install you will need the following pieces of information: 1) Proxy server URL if you are using a URL-based FTP or 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 FTP or HTTP connections (assuming you have a proxy available to use). 2) The IP address (or hostname if you configured DNS servers earlier in the install) of an FTP or HTTP server carrying the OpenBSD 5.2 distribution. The installation program will try to fetch a list of such servers; depending on your network settings, this might fail. If the list could be fetched, it will be displayed, and you can choose an entry from the list (the first entries are expected to be the closest mirrors to your location). 3) The directory holding the distribution sets. The default value of pub/OpenBSD/5.2/sgi is almost always correct on FTP servers; for HTTP servers there is no standard location for this. 4) For FTP installs only, the login and password for the FTP account. You will only be asked for a password for non-anonymous FTP. Then refer to the section named "installation set selection" below. 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". If there is more than one partition on the CD-ROM, you will be asked which partition the distribution is to be loaded from. This is normally partition "a". You will also have to provide the relative path to the directory on the CD-ROM which holds the distribution, for the sgi this is "5.2/sgi". Then refer to the section named "installation set selection" below. To install from an NFS mounted directory: When installing from an NFS-mounted directory, you must have completed network configuration above, and also set up the exported file system on the NFS server in advance. First you must identify the IP address of the NFS server to load the distribution from, and the file system the server expects you to mount. The install program will also ask whether or not TCP should be used for transport (the default is UDP). Note that TCP only works with newer NFS servers. You will also have to provide the relative path to the directory on the file system where the distribution sets are located. Note that this path should not be prefixed with a '/'. Then refer to the section named "installation set selection" 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. 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 '/'. Then refer to the next section. Installation set selection: A list of available distribution sets found on the given location will be listed. You may individually select distribution sets to install, by entering their name, or wildcards (e.g. `*.tgz' or `base*|comp*', or `all' to select all the sets (which is what most users will want to do). You may also enter `abort' to deselect everything and restart the selection from scratch, or unselect sets by entering their name prefixed with `-' (e.g. `-x*'). It is also possible to enter an arbitrary filename and have it treated as a file set. When you are done selecting distribution sets, enter `done'. The files will begin to extract. To install from tape: Unlike all other installation methods, there is no way to know the names of the files on tape. Because of this, it is impossible to check that the files on tape match the machine architecture and release of OpenBSD/sgi. Moreover, since tape filenames are not known, the file checksums can not be verified. Use this installation method only if there is no better option. In order to install from tape, the distribution sets to be installed must have been written to tape previously, either in tar format or gzip-compressed tar format. You will also have to identify the tape device where the distribution sets are to be extracted from. This will typically be "nrst0" (no-rewind, raw interface). Next you will have to specify how many files have to be skipped on the tape. This number is usually zero. The install program will not automatically detect whether an image has been compressed, so it will ask for that information before starting the extraction of each file. After the files have been extracted, you will be given the choice to select a new location from which to install distribution sets. If there have been errors extracting the sets from the previous location, or if some sets have been missing, this allows you to select a better source. Also, if the installation program complains that the distribution sets you have been using do not match their recorded checksums, you might want to check your installation source (although this can happen between releases, if a snapshot is being updated on an FTP or HTTP server with newer files while you are installing). The last thing you'll need to configure is the time zone your system will be using. For this to work properly, it is expected that you have installed at least the "base52", "etc52", and "bsd" distribution sets. The installation program will then proceed to save the system configuration, create all the device nodes needed by the installed system, and will install bootblocks on the root disk. On multiprocessor systems, if the bsd.mp kernel has been installed, it will be renamed to `bsd', which is the default kernel the boot blocks look for. The single processor kernel, `bsd', will be available as `bsd.sp'. Finally, you will be asked whether you would like to install non-free firmware files (which can't be tightly integrated to the OpenBSD system) on first boot, by invoking fw_update(8) on the next boot. Congratulations, you have successfully installed OpenBSD 5.2. 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 5.2 distribution might need to be tailored for your site. We recommend you run: man afterboot which will tell you about a bunch of the files needing to be reviewed. If you are unfamiliar with UN*X-like system administration, it's recommended that you buy a book that discusses it. Upgrading a previously-installed OpenBSD System: ------------------------------------------------ Warning! Upgrades to OpenBSD 5.2 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. As a minimum, if the toolchain (the ``comp'' set) was installed, you should remove all files within /usr/include before attempting to upgrade. To upgrade OpenBSD 5.2 from a previous version, start with the general instructions in the section "Installing OpenBSD". Boot from the CD-ROM or the bsd.rd kernel. When prompted, select the (U)pgrade option rather than the (I)nstall option at the prompt in the install process. You will be presented with a welcome message and asked if you really wish to upgrade. 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 neither the ``etc52.tgz'' nor the ``xetc52.tgz'' sets, 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 etc52.tgz and xetc52.tgz sets in a temporary directory and merge changes by hand, or with the help of the sysmerge(8) helper script, 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, CVSync or FTP. For more information, see http://www.OpenBSD.org/anoncvs.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) Use the OpenBSD ``package'' collection to grab a pre-compiled and tested version of the application for your hardware. 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) Obtain the source code and build the application based upon whatever installation procedures are provided with the application. 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 5.2/packages/mips64 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/5.2/packages/mips64/ # # 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/5.2/packages/mips64/ 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/5.2/packages/mips64/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/faq/ports/ports.html for current instructions on obtaining and installing OpenBSD ports. You should also refer to the ports(7) manual page. Installing other applications: If an OpenBSD package or port does not exist for an application you're pretty much on your own. The first thing to do is ask if anyone is working on a port -- there may be one in progress. If no such port exists, you might want to look at the FreeBSD ports or NetBSD pkgsrc for inspiration. If you can't find an existing port, try to make your own and feed it back to OpenBSD. That's how our ports collection grows. Some details can be found in the OpenBSD Porter's Handbook at http://www.openbsd.org/faq/ports/ with more help coming from the mailing list, . Administrivia: -------------- There are various mailing lists available via the mailing list server at . To get help on using the mailing list server, send mail to that address with an empty body, and it will reply with instructions. There are also two OpenBSD Usenet newsgroups, comp.unix.bsd.openbsd.announce for important announcements and comp.unix.bsd.openbsd.misc for general OpenBSD discussion. More information about the various OpenBSD mailing list and proper netiquette is available at http://www.OpenBSD.org/mail.html To report bugs, use the 'sendbug' command shipped with OpenBSD, and fill in as much information about the problem as you can. Good bug reports include lots of details. Additionally, bug reports can be sent by mail to: bugs@OpenBSD.org 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