INSTALLATION NOTES for OpenBSD/sun3 2.7 What is OpenBSD? ---------------- OpenBSD is a Berkeley Networking Release 2 (Net/2) and 4.4BSD-Lite -derived Operating System. It is a fully functional UN*X-like system which runs on many architectures and is being ported to more. Continuing the multi-platform tradition, OpenBSD has added ports to mvme68k, powerpc and arc machines. Kernel interfaces have continued to be refined, and now several subsystems and device drivers are shared among the different ports. You can look for this trend to continue. Security of the system as a whole has been significantly improved. Source code for all critical system components has been checked for remote-access, local-access, denial-of-service, data destruction, or information-gathering problems. Tools like ssh, ipf, ipnat, and nc have been added to the tree because security conscious people often need them. OpenBSD 2.7 has significantly enhanced the binary emulation subsystem (which includes iBCS2, Linux, OSF/1, SunOS, SVR4, Solaris and Ultrix compatibility) and several kernel subsystems have been generalized to support this more readily. The binary emulation strategy is aimed at making the emulation as accurate as possible. Cryptography components are part of OpenBSD. OpenBSD is from Canada, and export of these pieces (such as kerberosIV) to the world is not restricted. Note that it can not be re-exported from the US once it has entered the US. Because of this, take care NOT to get the distrib- ution from an FTP server in the US if you are outside of Canada and the US. Many new user programs have been added in OpenBSD 2.7, as well, bringing it closer to our goal of supplying a complete and modern UN*X-like environment. Tools like perl and ksh are standard, as are numerous other useful tools. OpenBSD 2.7 is the first "full" release of OpenBSD for the sun3, including a full set of binaries. This binary distribution is referred to elsewhere in this document by the name OpenBSD/sun3. This release offers the following features: * Native boot programs for disk, network, and tape * Automated installation tools (using a "miniroot") * SCSI driver supporting DMA, interrupts, and disconnect/reselect with SCSI-2 devices (optional) * Frame buffer drivers for bwtwo, cgtwo, cgfour, all compatible with SunOS and the X Window System * Support for the Virtually Addressed Cache (VAC) on Sun3/260 models (and vastly improved performance) * SMD disk drivers -- almost (still need testing) * SunOS 4.1 compatibility (runs most Sun3 applications) * Supports most SCSI devices (CD-ROM, etc) * Diskless boot capability Sources of OpenBSD: ------------------- This is a list of currently known ftp servers: Korea: ftp://ftp1.kr.openbsd.org/pub/OpenBSD == ftp://sunsite.kren.ne.kr/pub/OpenBSD Australia: ftp://ftp.aba.net.au/pub/OpenBSD == ftp://ftp.au.openbsd.org/pub/OpenBSD France: ftp://ftp.lip6.fr/pub/OpenBSD == ftp://ftp.fr.openbsd.org/pub/OpenBSD ftp://frp.univ-evry.fr/pub/OpenBSD Germany: ftp://ftp.fu-berlin.de/unix/OpenBSD == ftp://ftp.de.openbsd.org/pub/unix/openbsd/mirrors/OpenBSD Japan: ftp://ftp.tut.ac.jp/OpenBSD == ftp://ftp.jp.openbsd.org/OpenBSD ftp://ftp.dti.ad.jp/pub/OpenBSD Sweden: ftp://ftp.stacken.kth.se/pub/OpenBSD == ftp://ftp.se.openbsd.org/pub/OpenBSD ftp://ftp1.se.openbsd.org/pub/OpenBSD Switzerland: ftp://web.eunet.ch/pub/OpenBSD == ftp://ftp.eu.openbsd.org/pub/OpenBSD Thailand: ftp://ftp.ruibon.ac.th/pup/OpenBSD == ftp://ftp.th.openbsd.org/pub/OpenBSD Korea: ftp://sunsite.kren.ne.kr/pup/OpenBSD == ftp://ftp.kr.openbsd.org/pub/OpenBSD United Kingdom: ftp://ftp.demon.co.uk/pub/OpenBSD USA: ftp://freestuff.cs.colorado.edu/pub/OpenBSD == ftp://ftp3.usa.openbsd.org/pub/OpenBSD ftp://openbsd.eecs.umich.edu/pub/OpenBSD == ftp://ftp1.usa.openbsd.org/pub/OpenBSD ftp://ftp4.usa.openbsd.org/pub/OpenBSD ftp://ftp.geek-girl.com/pub/OpenBSD == ftp://ftp.usa.openbsd.org/pub/OpenBSD ftp://ftp6.usa.openbsd.org/pub/OpenBSD ftp://ftp.op.net/pub/OpenBSD ftp://freon.republic.k12.mo.us/pub/OpenBSD frp://ftp.msoe.edu/pub/OpenBSD Canada: ftp://lager.ucs.ualberta.ca/pub/OpenBSD == ftp://ftp.openbsd.org/pub/OpenBSD ftp://ftp.ca.openbsd.org/pub/OpenBSD ftp://ftp1.ca.openbsd.org/pub/OpenBSD ftp://obsd.compmore.net/pub/OpenBSD == ftp://ftp2.ca.openbsd.org/pub/OpenBSD ftp://ftp.styx.org/pub/OpenBSD As well, the file ftp://ftp.openbsd.org/pub/OpenBSD/2.7/ftplist contains a list which is continually updated. If you wish to become a distribution site for OpenBSD, contact deraadt@cvs.openbsd.org. OpenBSD 2.7 Release Contents: ----------------------------- The OpenBSD 2.7 release is organized in the following way. In the .../2.7 directory, for each of the architectures having an OpenBSD 2.7 binary distribution, there is a sub-directory. The sun3-specific portion of the OpenBSD 2.7 release is found in the "sun3" subdirectory of the distribution. That subdirectory is laid out as follows: .../2.7/sun3/ INSTALL.sun3 Installation notes; this file. CKSUM Output of the cksum(1) and md5(1) programs MD5 usable for verification of the correctness of downloaded files. *.tgz sun3 binary distribution sets; see below. bsd A stock GENERIC sun3 kernel which will be installed on your system during the install. bsd.rd A compressed RAMDISK kernel; the embedded filesystem contains the installation tools. Used for simple installation from a pre- existing system. installboot The OpenBSD/sun3 boot loader installation program. bootxx The OpenBSD/sun3 boot block. netboot The OpenBSD/sun3 network boot loader. tapeboot The OpenBSD/sun3 tape boot loader. ufsboot The OpenBSD/sun3 disk boot loader. These files can be used to make a boot tape suitable for installing OpenBSD/sun3. These files can also be used to configure an NFS server to support installation "over the network". See the section "Getting the OpenBSD System onto Useful Media" for instructions on either method. The OpenBSD/sun3 binary distribution sets contain the binaries which comprise the OpenBSD 2.7 release for sun3 systems. There are ten binary distribution sets. The binary distribution sets can be found in the "sun3" subdirectory of the OpenBSD 2.7 distribution tree, and are as follows: base27 The OpenBSD/sun3 2.7 base binary distribution. You MUST install this distribution set. It contains the base OpenBSD utilities that are necessary for the system to run and be minimally functional. It includes shared library support, and excludes everything described below. [ 19.4 gzipped, 61.9M uncompressed ] comp27 The OpenBSD/sun3 Compiler tools. All of the tools relating to C, C++, and FORTRAN (yes, there are two!) are supported. This set includes the system include files (/usr/include), the linker, the compiler tool chain, and the various system libraries (except the shared libraries, which are included as part of the base set). This set also includes the manual pages for all of the utilities it contains, as well as the system call and library manual pages. [ 13.1M gzipped, 40.6M uncompressed ] etc27 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.) [ 988K gzipped, 3.2M uncompressed ] game27 This set includes the games and their manual pages. [ 2.6M gzipped, 6.4M uncompressed ] man27 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. [ 4.8M gzipped, 18.4M uncompressed ] misc27 This set includes the system dictionaries (which are rather large), the typesettable document set, and man pages for other architectures which happen to be installed from the source tree by default. [ 1.6M gzipped, 5.5M uncompressed ] OpenBSD System Requirements and Supported Devices: -------------------------------------------------- OpenBSD/sun3 2.7 runs on most Sun3 machines, including: 3/50, 3/60, 3/110 3/75, 3/140, 3/150, 3/160, 3/180 3/260, 3/280 OpenBSD/sun3 2.7 does not run on the Sun3/80 and Sun3/4x0 (sun3x class) because the sun3x MMU and other devices are very different. The minimal configuration requires 4M of RAM and ~80MB of disk space. To install the entire system requires much more disk space (approx. 100MB additional space is necessary for full sources). To run X or compile the system, more RAM is recommended. Good performance requires 8MB of RAM, or 16 MB when running the X Window System. The following Sun3 hardware is supported: Serial ports (RS232): built-in ttya, ttyb Video adapters: bwtwo, cgtwo, cgfour Network interfaces: On-board Lance Ethernet (le) On-board or VME Intel Ethernet (ie) SCSI: (Most SCSI disks, tapes, CD-ROMs, etc.) On-board "si" (SCSI-3) VME "si" (SCSI-3) board SMD Disks: (the big, heavy ones 8^) Xylogics 450/451 [Note 1] Xylogics 753/7053 [Note 1] Input devices: Sun keyboard and mouse Miscellaneous: Battery-backed real-time clock. Note 1: SMD disk support is almost ready, but could not be tested in time for this release. Drivers are provided for the Xylogics 450/451 and Xylogics 753/7053 VME boards only as source code. They compile but have never touched a disk. If it's not on this list, there is no support for it in this release. Getting the OpenBSD System onto Useful Media: --------------------------------------------- Installation is supported from several media types, including: FFS partitions Tape Remote NFS partition FTP HTTP However, you can only boot the installation procedure from tape or network. This requires some setup work to prepare a bootable image, either a tape, or a compatible net boot server. Although you can access the distribution sets directly from one of the FTP mirrors over the internet, you may wish to transfer the sets to a local FTP or NFS server, or copy them to a partition on the target system's disk or onto a SCSI tape. 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 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 networks host. Extract the OpenBSD diskless(8) man page from the man27.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 (bootpd) 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 on the internet. To install or upgrade OpenBSD using a tape, you need to do the following: To install OpenBSD from a tape, you need to make a tape that contains the distribution set files, each in "tar" format or in "gzipped tar format". First you will need to transfer the distribution sets to your local system, using ftp. 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=/dev/nrst0 mt -f ${tape} rewind if test $# -lt 1 then for file in tapeboot bsd.rd do dd if=${file} of=${tape} obs=8k conv=sync done fi for file in base etc comp game man misc do dd if=${file}27.tgz of=${tape} obs=8k conv=sync done tar cf ${tape} bsd mt -f ${tape} offline # end of script And then: cd .../2.7/sun3 sh -x /tmp/maketape Note that 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 .../2.7/sun3 sh -x /tmp/maketape noboot If you're using a system other than OpenBSD or SunOS, the tape name and other requirements may change. 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 on 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 the numeric IP address of the NFS server, and, if the server is not on a network directly connected to the machine on which you're installing or upgrading OpenBSD, you need to know the numeric IP address of the router closest to the OpenBSD machine. Finally, you need to know the numeric IP address of the OpenBSD machine itself. Once the NFS server is set up properly and you have the information mentioned above, you can proceed to the next step in the installation or upgrade process. If you're installing OpenBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading. If you are upgrading OpenBSD, you also have the option of installing OpenBSD by putting the new distribution sets somewhere in your existing file system, and using them from there. To do that, you must do the following: Place the distribution sets you wish to upgrade somewhere in your current file system tree. At a bare minimum, you must upgrade the "base" binary distribution, and so must put the "base27" set somewhere in your file system. If you wish, you can do the other sets, as well, but you should NOT upgrade the "etc" distribution; the "etc" distribution contains system configuration files that you should review and update by hand. Once you have done this, you can proceed to the next step in the upgrade process, actually upgrading your system. Preparing your System for OpenBSD Installation: ----------------------------------------------- Sun3 machines usually need little or no preparation before installing OpenBSD, other than the usual, well advised precaution of BACKING UP ALL DATA on any attached storage devices. You will need to know the SCSI target ID of the drive on which you will install OpenBSD. Note that SunOS/sun3 uses confusing names for the SCSI devices: target 1 is sd2, target 2 is sd4, etc. It might be a good time to run the diagnostics on your Sun3. First, attach a terminal to the "ttya" serial port, then set the "Diag/Norm" switch to the Diagnostic position, and power-on the machine. The Diag. switch setting forces console interaction to occur on ttya. The console location (ttya, ttyb, or keyboard/display) is controlled by address 0x1F in the EEPROM, which you can examine and change in the PROM monitor by entering "q1f" followed by a numeric value (or just a '.' if you don't want to change it). Console values are: 00: default graphics display 10: tty a (9600-N-8-1) 11: tty b (1200-N-8-1) 20: Color option board on P4 OpenBSD will use the EEPROM setting to determine which device to use as the console, so you should make sure it is correct. 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. 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 the new OpenBSD "-s enable" option to the "tunefs" command, which enable the soft update feature. Although untested, it is likely that SunOS would be confused by a filesystem with soft update flags enabled. OpenBSD supports both OpenBSD "native" disklabels and "Sun compatible" disklabels. Unless you have some really good reason, you should stick with the Sun compatible labels. The disklabel(8) "-r" switch says to use OpenBSD labels, which is a bit counter-intuitive and contrary to the reasons why might want to use "-r" on other OpenBSD ports. Don't use "-r" with disklabel(8). The OpenBSD "Sun Compatible" disklabel have been extended to support 16 partitions, which may be compatible with Solaris, but the old SunOS format(8) utility only sees the first 8 partititions and may "lose" information about the extended partitions. Use SunOS format(8) only with *extreme* caution on drives that contain OpenBSD partitions. OpenBSD and Sun BSD bootblocks are similar in concept, though implemented differently. The OpenBSD bootblocks are architecture independent and also understand the extended disklabels 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 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 miniroot that can be booted off a tape. If your Sun3 is hooked up in a network and you can find a server to arrange for a diskless setup, which 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 system, using SunOS tools and gnu tar and gunzip (see ``Installing from SunOS'' below). This section of the install document is really broken into several parts: - booting from the installation media - the miniroot install script - after completing an installation - installing from Sun OS - net boot or diskless setup information The first section explains how to run tho install scripts. The second section gets you up to the point where you've booted the kernel from whatever media or setup described in the previous section, to where you have to respond to prompts from the install script. The next section describes the path through the install script, and the remainder are notes which might be useful, but outside the bounds of simple "how two" instructions. 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. Have the installation media for the prior installation, be it a SunOS or OpenBSD tape is good insurance if you want to be able to "go back" for some reason. After taking care of all that, bring your system down gracefully using the shutdown(8) and/or halt(8) commands. This will get you to the monitor prompt. Booting from SCSI tape Boot the miniroot by typing the appropriate command at the PROM: > b st() 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,) This will cause the kernel contained in the miniroot to be booted. After the initial device probe messages you'll be asked to start the install or upgrade procedure. Proceed to the section ``Running the installation scripts'' below. Installing using a diskless setup First, you must setup a diskless client configuration on a server. If you are using a 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). Boot your workstation from the server by entering the appropriate `boot' command at the monitor prompt. Depending on the ethernet chip in your machine, this command takes one of the following forms: > b le()bsd.rd # for sun pizza boxes (3/50, 3/60) > b ie()bsd.rd # for other sun3s This will cause the kernel provided by the diskless setup to be booted. After the initial probe messages you'll asked to start the install or upgrade procedure. Proceed to the section ``Running the installation scripts'' below. The miniroot install script: 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 may have to begin the installation process again from scratch. Using Control-Z to suspend the process may be a better option. 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 medias is probably bad, your diskless setup isn't correct or you may have a hardware or configuration problem. You will then be presented with the OpenBSD kernel boot messages. You will want to read them to determine your disk's name and geometry. Its name will be something like "sd0" or "wd0" and the geometry will be printed on a line that begins with its name. As mentioned above, you will need your disk's geometry when creating OpenBSD partitions. You will also need to know the device name to tell the install tools what disk to install on. While booting, you will probably see several warnings. You may be warned that the kernel can't figure out what device it booted from and that no swap space is present. Do not be alarmed, these are completely normal. The first warning occurs because while OpenBSD/sun3 can boot from the floppy drive, the kernel itself lacks a floppy driver for some architectures. When the loading process is complete, the boot floppy will be ejected and you will be prompted to insert a filesystem floppy, just hit return since the filesystem is contained in the kernel image just loaded. Next there will be a prompt asking you for a shell name, just hit return to start executing the installation setup script. You will next be asked for your terminal type. If you are installing from a keyboard/monitor console, the default of "sun" if 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). Next you will be prompted for a choice of which text editor to use at several places in the install script. You will probably want to use "vi" if your terminal supports this. After entering the terminal type you will be greeted by a welcome message and asked if you really want to continue. Assuming you answered yes, the install program will then tell you which disks of that type it can install on, and ask you which it should use. The name of the disk is typically "sd0". Reply with the name of your disk. Next you will have to edit or create a disklabel for the disk OpenBSD is being installed on. The installation script will invoke the text 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. 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 root and /usr, you may also want to specify /var and /home partitions. The swap partition (usually 'b') should have a type of "swap", all other native OpenBSD partitions should have a type of "4.2BSD". Block and fragment sizes are usually 8192 and 1024 bytes, but can also be 16384 and 2048 bytes. The install program will now label your disk and ask which file systems should be created on which partitions. It will auto- matically select the 'a' partition to be the root file system. Next it will ask for which disk and partition you want a file system created on. This will be the same as the disk name (eg. "sd0") with the letter identifying the partition (eg. "d") appended (eg. "sd0d"). Then it will ask where this partition is to be mounted, eg. /usr. This process will be repeated until you type "done". At this point you will be asked to confirm that the file system information you have entered is correct, and given an opportunity to change the file system table. Next it will create the new file systems as specified, OVERWRITING ANY EXISTING DATA. This is the point of no return. After all your file systems have been created, the install program will give you an opportunity to configure the network. The network configuration you enter (if any) can then be used to do the install from another system using NFS, HTTP or FTP, and will also be the configuration used by the system after the installation is complete. If you select to configure the network, the install program will ask you for a name of your system and the DNS domain name to use. Note that the host name should be without the domain part, and that the domain name should NOT include the host name part. Next the system will give you a list of network interfaces you can configure. For each network interface you select to configure, it will ask for the IP address to use, the symbolic host name to use, the netmask to use and any interface-specific flags to set. The interface-specific flags are usually used to determine which media the network card is to use. This is driver dependent, but for the sun3 le(4) driver, the flags usually carry meaning: -link0 -link1 Use existing setting (only setup by netboot) link0 -link1 Use UTP (twisted pair) port -link0 link1 Use AUI port *** IMPORTANT - these are the correct setting for sun3 ethernet cards, the suggestions shown by the install script are generic and may or may not be correct... 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 has been completed, you will be able to extract the distribution sets onto your system. There are several install methods supported; FTP, HTTP, tape, CD-ROM, NFS or a local disk partition. To install from a tape, the distrib- ution sets must have been written to tape prior to running the installation program, either as tar images or as gzipped tar images. Note that installation sets on multiple floppies is not currently supported. To install via FTP: To begin an FTP install you will need the following pieces of information. Don't be daunted by this list; the defaults are sufficient for most people. 1) Proxy server URL if you are using a URL-based ftp proxy (squid, CERN ftp, Apache 1.2 or higher). You need to define a proxy if you are behind a firewall that blocks outgoing ftp (assuming you have a proxy available to use). 2) Do you need to use active mode ftp? By default, ftp will attempt to use passive mode and fall back to an active connection if the server does not support passive mode. You only need to enable this option if you are connecting to a buggy ftp daemon that implements passive ftp incorrectly. Note that you will not be asked about active ftp if you are using a proxy. 3) The IP address (or hostname if you enabled DNS earlier in the install) of an ftp server carrying the OpenBSD 2.7 distribution. If you don't know, just hit return when asked if you want to see a list of such hosts. 4) The ftp directory holding the distribution sets. The default value of pub/OpenBSD/2.7/sun3 is almost always correct. 5) The login and password for the ftp account. You will only be asked for a password for non-anonymous ftp. For instructions on how to complete the installation via ftp, see the section named "Common URL installations" below. To install via HTTP: To begin an HTTP install you will need the following pieces of information: 1) Proxy server URL if you are using a URL-based http proxy (squid, CERN ftp, Apache 1.2 or higher). You need to define a proxy if you are behind a firewall that blocks outgoing http connections (assuming you have a proxy available to use). 3) The IP address (or hostname if you enabled DNS earlier in the install) of an http server carrying the OpenBSD 2.7 distribution. If you don't know, just hit return when asked if you want to see a list of such hosts. 4) The directory holding the distribution sets. There is no standard location for this; You should use the directory specified along with the server in the list of official http mirror sites that you received in step 3. For instructions on how to complete the installation via http, see the section named "Common URL installations" below. To install from tape: In order to install from tape, the distribution sets to be installed must have been written to tape previously, either in tar format or gzip-compressed tar format. You will also have to identify the tape device where the distribution sets are to be extracted from. This will typically be "nrst0" (no-rewind, raw interface). Next you will have to provide the file number of the set that is to be extracted. Note that the file number starts at 1, which is the first file written to the tape, unless you have created a bootable tape, in which case the file number starts at 3. The install program will not automatically detect whether an image has been compressed, so it will ask for that information before starting the extraction. To install from a NFS mounted directory: When installing from a NFS-mounted directory, you must have completed network configuration above, and also set up the exported file system on the NFS server in advance. First you must identify the IP address of the NFS server to load the distribution from, and the file system the server expects you to mount. The install program will also ask whether or not TCP should be used for transport (the default is UDP). Note that TCP only works with newer NFS servers. You will also have to provide the relative path to the directory on the file system where the distribution sets are located. Note that this path should not be prefixed with a '/'. For instructions on how to complete the installation from the CD-ROM distribution, see the section named "Common file system installations" below. To install from a local disk partition: When installing from a local disk partition, you will first have to identify which disk holds the distribution sets. This is normally "wdN" or "sdN" where N is a number 0 through 9. Next you will have to identify the partition within that disk that holds the distribution, this is a single letter between 'a' and 'p'. You will also have to identify the type of file system residing in the partition identified. Currently, you can only install from partitions that has 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 the a local disk partition, see the next section. Common file system installations: The following instructions are common to installations from local disk partitions, NFS mounted directories and CD-ROMs. A list of available distribution sets will be listed. You may individually select distribution sets to install or enter `all' to install all of the sets (which is what most users will want to do). You may also enter `list' to get a file list or `done' when you are done selecting distribution sets. You may also use wildcards in place of a file name, eg `*.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, eg `*.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 "base27", "etc27", and "bsd" distribution sets. After completing an installation: Now try a reboot. (If needed, swap your scsi id's first). Initially I'd suggest you "boot sd()bsd -bs", then try multiuser after that. if you boot single-user the OpenBSD incantation to make the root filesystem writable is OpenBSD# mount -u /dev/sd0a / Congratulations, you have successfully installed OpenBSD 2.7. When you reboot into OpenBSD, you should log in as "root" at the login prompt. You should create yourself an account and protect it and the "root" account with good passwords. You should have got a mail from the install program we recommend you to read, it contains answers to basic questions you might have about OpenBSD (like setting up your system, installing packages, getting more information about OpenBSD, sending in your dmesg output and more). This you can do by running mail and then just enter "1" to get the first message. You quit mail by entering "q". Some of the files in the OpenBSD 2.7 distribution might need to be tailored for your site. We recommend you run: man afterboot which will tell you about a bunch of the files needing to be reviewed. If you are unfamiliar with UN*X-like system administration, it's recommended that you buy a book that discusses it. If you will be running your OpenBSD system from a serial console, you may need to edit /etc/ttys and change the terminal type, and getty method from "sun" and "console" 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/sun3, 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. On installing X11 for OpenBSD/sun3, you may wish to add a line similar to 'ldconfig /usr/X11R6/lib' to the end of your /etc/rc.local file. This will add the X libraries to your dynamic linking search path at boot time. If you are unfamiliar with UN*X-like system administration, it's recommended that you buy a book that discusses it. 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, base27.tgz) gunzip (GNU gzip) SunOS binary gtar (GNU tar) SunOS binary a "/boot" file from a SunOS machine a kernel, most likely "/bsd" All these pieces, except "/boot" and the GNU utilities are supplied in the OpenBSD/sun3 distribution. You need to format and partition the disk using SunOS (since OpenBSD/sun3 uses SunOS disk labels.) Give yourself adequate partition sizes. Here is an example layout: partition size offset will be.. sd0a 28140 0 / sd0b 16170 28140 swap sd0c 204540 0 `whole disk' sd0g 160230 44310 /usr BTW, These are not recommended sizes. Use SunOS to newfs the partitions which will have filesystems on them. (OpenBSD's filesystem format is identical to SunOS). sunos# newfs /dev/rsd0a [... lots of output] sunos# newfs /dev/rsd0g [... lots of output] 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 11501 0 11501 0% /mnt /dev/sd0g 179529 0 179529 0% /mnt/usr 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/rsd0a You can now extract the provided "*.tgz files onto your disk. sunos# ls -FC base27.tgz comp27.tgz man27.tgz xfont27.tgz bsd etc27.tgz misc27.tgz xserv27.tgz game27.tgz xbase27.tgz sunos# gunzip < base27.tgz | (cd /mnt; gtar xvpf -) [...] for each set And finally copy the OpenBSD kernel onto your disk. sunos# cp bsd /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, setup /mnt/etc/fstab to match your actual disk layout. (Minus the "/mnt" component of each path, of course :-) Now proceed to reboot the machine and the customize your installation. Net Boot or Diskless Setup Information: The set up is similar to 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 sun3 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 corresponding to the machine's IP address. For example, a sun3 machine which has been assigned IP address 130.115.144.11, will make an TFTP request for `8273900B'. Normally, this file is a symbolic link to an appropriate second-stage boot program, which should be located in a place where the TFTP daemon can find it (remember, many TFTP daemons run in a chroot'ed environment). You can find the boot program in `/usr/mdec/boot' in the OpenBSD/sun3 distribution. Here's an example to illustrate this whole mess: server# cd //usr/mdec server# cp boot /tftpboot/boot.sun3.OpenBSD server# cd /tftpboot server# ln -s boot.sun3.OpenBSD 8273900B 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 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 miniroot27.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 `base27.tgz' and `etc27.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 base27.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/sun3.OpenBSD /usr nfs rw 0 0 Now you must populate the the `/dev' directory for your client. For this, you can simply change your working directory to `/dev' and run the MAKEDEV script: `sh MAKEDEV all'. Upgrading a previously-installed OpenBSD System: ------------------------------------------------ To upgrade to OpenBSD 2.7 from a previous version start with the general instructions in the section "Installing OpenBSD". After booting with the miniroot, select the (U)pdate option rather than the (I)nstall option at the prompt in the install process. The upgrade script will use the existing disk partitions to install the new system in, and also preserves files in `/etc' which you are likely to have customized since a previous installation. Getting source code for your OpenBSD System: -------------------------------------------- Now that your OpenBSD system is up and running, you probably want to get access to source code so that you can recompile pieces of the system. A few methods are provided. If you have an OpenBSD CD, the source code is provided. Otherwise, you can get the pieces over the Internet using ANONCVS, CTM or FTP. For more information, see http://www.openbsd.org/anoncvs.html http://www.openbsd.org/ctm.html http://www.openbsd.org/ftp.html Using online OpenBSD documentation: ----------------------------------- Documentation is available if you first install the manual distribution set. Traditionally, the UN*X "man pages" (documentation) are denoted by 'name(section)'. Some examples of this are intro(1), man(1), apropos(1), passwd(1), and passwd(5). The section numbers group the topics into several categories, but three are of primary interest: user commands are in section 1, file formats are in section 5, and administrative information is in section 8. The 'man' command is used to view the documentation on a topic, and is started by entering 'man [section] topic'. The brackets [] around the section should not be entered, but rather indicate that the section is optional. If you don't ask for a particular section, the topic with the least-numbered section name will be displayed. For instance, after logging in, enter man passwd to read the documentation for passwd(1). To view the documentation for passwd(5), enter man 5 passwd instead. If you are unsure of what man page you are looking for, enter apropos subject-word where "subject-word" is your topic of interest; a list of possibly related man pages will be displayed. Adding third party software; ``packages'' and ``ports'': ------------------------------------------------------- As complete as your OpenBSD system is, you may want to add any of several excellent third party software applications. There are several ways to do this. You can: 1) Obtain the source code and build the application based upon whatever installation procedures are provided with the application. 2) Use the OpenBSD ``ports'' collection to automatically get any needed source file, apply any required patches, create the application, and install it for you. 3) Use the OpenBSD ``package'' collection to grab a pre-compiled and tested version of the application for your hardware. If you purchased the OpenBSD CD-ROM you already have several popular ``packages'', and the ``ports'' collection. NOTE: Some important packages which are not permitted on the CD (due to patents) are available on our FTP servers. In particular, we provide the USA and international versions of both SSH and PGP. The filenames are: ssh-usa-1.2.27.tgz ssh-intl-1.2.27.tgz pgp-usa-2.6.3.tgz pgp-intl-2.6.3.tgz Instructions for installing applications from the various sources using the different installation methods follow. If emacs is to be installed it should be installed first as it creates the ``info'' directory file that may be modified by other applications. You should also refer to the packages(7) manual page. Installing applications from the CD-ROM package collection: The OpenBSD CD-ROM ships with several applications pre-built for various hardware architectures. The number of applications vary according to available disk space. Check the directory 2.7/packages/sun3 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 appropriage CD-ROM 3) use the ``pkg_add'' command to install the software Example (in which we use su(1) to get superuser privileges, thus you have to be in group "wheel", see the manual page for su(1)). $ su Password: # mkdir -p /cdrom # mount /dev/cd0a /cdrom # pkg_add /cdrom/2.7/packages/sun3/ # # umount /cdrom Package names are usually the application name and version with .tgz appended, e.g. emacs-20.3.tgz Installing applications from the ftp.openbsd.org package collection: All available packages for your architecture have been placed on ftp.openbsd.org in the directory pub/OpenBSD/2.7/packages/sun3/ You may want to peruse this to see what packages are available. The packages are also on the OpenBSD FTP mirror sites. See http://www.openbsd.org/ftp.html for a list of current ftp mirror sites. Installation of a package is very easy. 1) become the superuser (root) 2) use the ``pkg_add'' command to install the software ``pkg_add'' is smart enough to know how to download the software from the OpenBSD ftp server. Example: $ su Password: # pkg_add ftp://ftp.openbsd.org/pub/OpenBSD/2.7/packages/sun3/emacs-20.3.tgz Note: there are both USA and INTERNATIONAL versions of ssh and pgp on the ftp server. Be sure to grab the correct version. The USA versions, ssh-usa-1.2.26.tgz and pgp-usa-2.6.3.tgz, use RSAREF, a legal requirement for use within the United States due to patent issues. Packages available include (at least): ImageMagick-4.2.0.tgz m4-1.4.tgz Xaw3d-1.3.tgz mm-2.7.tgz aalib-1.2.tgz mpeg_lib-1.2.1.tgz afm-1.0.tgz mpeg_play-2.4.tgz autoconf-2.13.tgz netpbm-19940301.tgz bash-2.03.tgz netpipes-4.1.1-export.tgz bison-1.25.tgz nmh-1.0.tgz bzip2-0.9.0c.tgz pgp-2.6.3-intl.tgz compface-1.0.tgz pgp-2.6.3-usa.tgz cucipop-1.31.tgz pine-4.10.tgz dejagnu-1.3.tgz png-1.0.3.tgz egcs-1.1.2.tgz psutils-1.17-a4.tgz emacs-20.3.tgz psutils-1.17-letter.tgz enscript-1.6.1.tgz screen-3.7.6.tgz ethereal-0.5.1.tgz sharutils-4.2.tgz expect-5.28.tgz sniffit-0.3.5.tgz fetchmail-4.7.9.tgz ssh-1.2.27-intl.tgz freetype-1.2.tgz ssh-1.2.27-usa.tgz gettext-0.10.35.tgz tar-1.12.tgz ghostscript-5.10.tgz tcl-8.0.5.tgz gimp-1.1.4.tgz tcsh-6.08.00.tgz glib-1.2.1.tgz teTeX-0.4.tgz glimpse-4.1.tgz tiff-3.4.tgz gmake-3.77.tgz tk-8.0.5.tgz gnuplot-3.7.tgz transfig-3.2.1.tgz gtk+-1.2.1.tgz unzip-5.40.tgz gv-3.5.8.tgz viewfax-2.3.tgz id-utils-3.2.tgz wget-1.5.3.tgz idled-1.16.tgz xcolors-1.3.tgz iozone-2.01.tgz xfig-3.2.2.tgz ircii-2.8.2-epic3.004.tgz xntp3-5.93e-export.tgz ispell-3.1.20.tgz xpaint-2.5.5.tgz jove-4.16.tgz xpdf-0.80.tgz jpeg-6b.tgz xphoon-91.9.18.tgz lesstif-0.88.0.tgz xspread-2.1.tgz libslang-1.2.2.tgz xv-3.10a.tgz Note: these packages may not exist for all architectures; other packages may be added. Some packages are only available via ftp. Installing applications from the CD-ROM ports collection: The CD-ROM ``ports'' collection is a set of Makefiles, patches, and other files used to control the building and installation of an application from source files. Creating an application from sources can require a lot of disk space, sometimes 50 megabytes or more. The first step is to determine which of your disks has enough room. Once you've made this determination read the file README.ports on CD-ROM 2 to see how to copy or mount the ports directory. To build an application you must: 1) become the superuser (root) 2) have network access, or obtain the actual source files by some other means. 3) cd to the ports directory containing the port you wish to build. To build samba, for example, where you'd previously copied the ports files into the /usr/ports directory: cd /usr/ports/net/samba 4) make 5) make install 6) make clean Installing applications from the OpenBSD ports collection: See http://www.openbsd.org/ports.html for current instructions on obtaining and installing OpenBSD ports. You should also refer to the ports(7) manual page. Installing other applications: If an OpenBSD package or port does not exist for an application you're pretty much on your own. The first thing to do is ask ports@openbsd.org if anyone is working on a port -- there may be one in progress. If no luck there you may try the FreeBSD ports or NetBSD package collection. If you are on an i386 based machine it is quite possible that the FreeBSD port, if one exists, will work for you. If you can't find an existing port try to make your own and feed it back to OpenBSD. That's how our ports collection grows. Some details can be found at http://www.openbsd.org/porting.html with more help coming from the mailing list, ports@openbsd.org. Administrivia: -------------- There are various mailing lists available via the mailing list server at . To get help on using the mailing list server, send mail to that address with an empty body, and it will reply with instructions. There are also two OpenBSD Usenet newsgroups, comp.unix.bsd.openbsd.announce for important announcements and comp.unix.bsd.openbsd.misc for general OpenBSD discussion. To report bugs, use the 'sendbug' command shipped with OpenBSD, and fill in as much information about the problem as you can. Good bug reports include lots of details. Additionally, bug reports can be sent by mail to: bugs@OpenBSD.ORG Use of 'sendbug' is encouraged, however, because bugs reported with it are entered into the OpenBSD bugs database, and thus can't slip through the cracks. As a favor, please avoid mailing huge documents or files to the mailing lists. Instead, put the material you would have sent up for FTP somewhere, then mail the appropriate list about it, or, if you'd rather not do that, mail the list saying you'll send the data to those who want it.