INSTALLATION NOTES for OpenBSD/sparc 2.9 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 ipf, ipnat, and bridging are also standard. For high performance demands, support for hardware cryptography has also been added to the base system. Because security is often seen as a tradeoff with usability, OpenBSD provides as many security options as possible to allow the user to enjoy secure computing without feeling burdened by it. To integrate more smoothly in other environments, OpenBSD 2.9 also provides several binary emulation subsystems (which includes iBCS2, Linux, OSF/1, SunOS, SVR4, Solaris, and Ultrix compatibility), aiming at making the emulation as accurate as possible so that it is transparent to the user. Many new user programs and device drivers have been added in OpenBSD 2.9, as well, bringing it closer to our goal of supplying a complete and modern UN*X-like environment. Tools like perl and an improved ksh are standard, as are numerous other useful tools. Because OpenBSD is from Canada, the export of Cryptography pieces (such as SSH, IPSEC, and KerberosIV) 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.) OpenBSD/sparc 2.9 is brought to you by the same people who did the first free BSD sparc port (based on Chris Torek's 4.4BSD work). Many more sparc models and devices are now supported. In addition to the providing SunOS 4.1 compatibility, OpenBSD 2.9 will also run some number of SunOS 5 (SVR4) executables in binary emulation mode. Sources of OpenBSD: ------------------- This is a list of currently known ftp servers: Argentina: ftp://ftp.openbsd.org.ar/pub/OpenBSD Australia: ftp://ftp.aba.net.au/pub/OpenBSD == ftp://ftp.au.openbsd.org/pub/OpenBSD ftp://ftp.it.net.au/mirrors/OpenBSD ftp://ftp.planetmirror.com/pub/OpenBSD ftp://ftp.wiretapped.net/pub/OpenBSD ftp://mirror.aarnet.edu.au/pub/OpenBSD Austria: ftp://gd.tuwien.ac.at/opsys/OpenBSD Belgium: ftp://openbsd.rug.ac.be/pub/OpenBSD Canada: ftp://openbsd.sunsite.ualberta.ca/pub/OpenBSD == ftp://ftp.openbsd.org/pub/OpenBSD ftp://ftp.ca.openbsd.org/pub/OpenBSD ftp://ftp1.ca.openbsd.org/pub/OpenBSD China (Hong Kong): ftp://ftp.shellhung.org/pub/OpenBSD France: ftp://ftp.lip6.fr/pub/OpenBSD == ftp://ftp.fr.openbsd.org/pub/OpenBSD ftp://ftp.grolier.fr/pub/OpenBSD == ftp://ftp2.fr.openbsd.org/pub/OpenBSD ftp://ftp.bsdfr.org/pub/OpenBSD == ftp://ftp3.fr.openbsd.org/pub/OpenBSD Germany: ftp://ftp.fu-berlin.de/unix/OpenBSD == ftp://ftp.de.openbsd.org/unix/OpenBSD ftp://ftp.leo.org/pub/OpenBSD == ftp://ftp2.de.openbsd.org/unix/OpenBSD ftp://ftp.fh-wolfenbuettel.de/pub/os/openbsd ftp://ftp.freenet.de/pub/ftp.openbsd.org/pub/OpenBSD ftp://ftp.gigabell.net/pub/OpenBSD Greece: ftp://filoktitis.noc.uoa.gr/pub/OpenBSD ftp://ftp.duth.gr/pub/OpenBSD Hungary: ftp://ftp.fsn.hu/pub/OpenBSD Ireland: ftp://ftp.esat.net/pub/OpenBSD Italy: ftp://ftp.volftp.mondadori.com/mirror/openbsd Japan: ftp://ftp.dti.ad.jp/pub/OpenBSD == ftp://ftp.jp.openbsd.org/OpenBSD ftp://ftp2.jp.openbsd.org/OpenBSD ftp://ftp.kddlabs.co.jp/OpenBSD ftp://ftp.netlab.is.tsukuba.ac.jp/pub/os/OpenBSD ftp://mirror.nucba.ac.jp/mirror/OpenBSD The Netherlands: ftp://ftp.calyx.nl/pub/OpenBSD ftp://ftp.nl.uu.net/pub/OpenBSD ftp://ftp.nluug.nl/pub/OpenBSD New Zealand: ftp://mirror.qsi.net.nz/pub/OpenBSD == ftp://ftp.nz.openbsd.org/pub/OpenBSD Norway: ftp://ftp.inet.no/pub/OpenBSD ftp://sunsite.uio.no/pub/OpenBSD Romania: ftp://quasar.uvt.ro/pub/OpenBSD Russia: ftp://ftp.chg.ru/pub/OpenBSD ftp://ftp.radio-msu.net/pub/OpenBSD ftp://vell.nsc.ru/pub/OpenBSD Saudi Arabia: ftp://ftp.isu.net.sa/pub/mirrors/ftp.openbsd.org/pub/OpenBSD South Korea: ftp://ftp.snu.ac.kr/pub/BSD/OpenBSD Spain: ftp://ftp.rediris.es/mirror/OpenBSD Sweden: ftp://ftp.stacken.kth.se/pub/OpenBSD == ftp://ftp.se.openbsd.org/pub/OpenBSD ftp://ftp1.se.openbsd.org/pub/OpenBSD ftp://ftp.luth.se/pub/OpenBSD ftp://ftp.sunet.se/pub/OpenBSD Switzerland: ftp://sunsite.cnlab-switch.ch/pub/OpenBSD Taiwan: ftp://openbsd.csie.nctu.edu.tw/pub/OpenBSD Thailand: ftp://ftp.riubon.ac.th/pub/OpenBSD == ftp://ftp.th.openbsd.org/pub/OpenBSD ftp://ftp.kmitl.ac.th/pub/OpenBSD United Kingdom: ftp://ftp.knowledge.com/pub/mirrors/OpenBSD ftp://ftp.plig.org/pub/OpenBSD ftp://sunsite.org.uk/Mirrors/ftp.openbsd.org/pub/OpenBSD USA: ftp://openbsd.cs.colorado.edu/pub/OpenBSD == ftp://ftp.usa.openbsd.org/pub/OpenBSD ftp://ftp3.usa.openbsd.org/pub/OpenBSD ftp://ftp6.usa.openbsd.org/pub/OpenBSD ftp://ftp.eecs.umich.edu/pub/OpenBSD == ftp://ftp1.usa.openbsd.org/pub/OpenBSD ftp://ftp4.usa.openbsd.org/pub/OpenBSD ftp://ftp.cerias.purdue.edu/pub/os/OpenBSD == ftp://ftp7.usa.openbsd.org/pub/os/OpenBSD ftp://archive.progeny.com/OpenBSD ftp://carroll.cac.psu.edu/pub/OpenBSD ftp://download.sourceforge.net/pub/mirrors/OpenBSD ftp://ftp.geto.net/OpenBSD ftp://ftp.op.net/pub/OpenBSD ftp://ftp.src.uchicago.edu/pub/OpenBSD ftp://ftp.tux.org/bsd/openbsd ftp://ftp.twoguys.org/pub/OpenBSD ftp://gandalf.neark.org/pub/distributions/OpenBSD ftp://mirror.csit.fsu.edu/pub/OpenBSD ftp://mirrors.rcn.net/pub/OpenBSD ftp://rt.fm/pub/OpenBSD As well, the file ftp://ftp.openbsd.org/pub/OpenBSD/2.9/ftplist contains a list which is continually updated. If you wish to become a distribution site for OpenBSD, contact miod@openbsd.org. OpenBSD 2.9 Release Contents: ----------------------------- The OpenBSD 2.9 release is organized in the following way. In the .../2.9 directory, for each of the architectures having an OpenBSD 2.9 binary distribution, there is a sub-directory. The sparc-specific portion of the OpenBSD 2.9 release is found in the "sparc" subdirectory of the distribution. That subdirectory is laid out as follows: .../2.9/sparc/ INSTALL.sparc Installation notes; this file. CKSUM Output of the cksum(1) and md5(1) programs MD5 usable for verification of the correctness of downloaded files. miniroot29.fs A miniroot filesystem image to be used if you for some reason can't or don't want to use the ramdisk installation method. floppy29.fs The standard sparc boot and installation floppy; see below. *.tgz sparc binary distribution sets; see below. bsd A stock GENERIC sparc kernel which will be installed on your system during the install. bsd.rd A compressed RAMDISK kernel; the embedded filesystem contains the installation tools. Used for simple installation from a pre- existing system. bsd.scsi3 A kernel with SCSI target 3 re-mapped as 0 and 0 mapped as 3. installboot The OpenBSD/sparc boot loader installation program bootxx The OpenBSD/sparc boot block boot The OpenBSD/sparc secondary boot loader boot.net The OpenBSD/sparc network boot loader Please note that there are multiple bootable images and kernels, intended to allow installing OpenBSD/sparc in a variety of situations without requiring a pre-existing working operating system. The "miniroot29.fs" is a small bootable root filesystem that can be used for installation or upgrade where there is some means to copy the miniroot image into a swap or unused partition on the system, and also for diskless or net booting. This can be convenient if you have a existing installation of OpenBSD, NetBSD, SunOS, or Solaris and wish to test or upgrade the existing system to OpenBSD. The "floppy29.fs" is a bootable floppy image, with contents similar to a miniroot stored in a compressed kernel with pre-loaded ramdisk. These bootable images are also useful as "failsafe" boots for system maintenance and disaster recovery. The kernel and boot images are provided for net booting installations. While the OpenBSD bootblocks will work with the provided miniroot images, Sun bootblocks require a separate kernel image and root filesystem. Bootable installation images: floppy29.fs This disk contains a compressed ramdisk filesystem, and holds all utilities needed to install OpenBSD 2.9 miniroot29.fs This is a miniroot filesystem image which can be copied to the swap partition of an existing OpenBSD, NetBSD, Linux, SunOS, or Solaris installation to allow upgrading to OpenBSD 2.9 The OpenBSD/sparc binary distribution sets contain the binaries which comprise the OpenBSD 2.9 release for sparc systems. There are ten binary distribution sets. The binary distribution sets can be found in the "sparc" subdirectory of the OpenBSD 2.9 distribution tree, and are as follows: base29 The OpenBSD/sparc 2.9 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. [ 18.4M gzipped, 56.4M uncompressed ] comp29 The OpenBSD/sparc 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. [ 12.1M gzipped, 39.7M uncompressed ] etc29 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.) [ 165.2K gzipped, 740.0K uncompressed ] game29 This set includes the games and their manual pages. [ 2.7M gzipped, 6.7M uncompressed ] man29 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. [ 3.4M gzipped, 13.1M uncompressed ] misc29 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.4M uncompressed ] xbase29 This set includes the base X distribution. This includes programs, headers, libraries, configuration files. [ 4.6M gzipped, 12.9M uncompressed ] xshare29 This set includes all text files equivalent between all architectures. [ 1.4M gzipped, 8.3M uncompressed ] xfont29 This set includes all of the X fonts. [ 6.0M gzipped, 7.3M uncompressed ] xserv29 This set includes all of the X servers. [ 5.4M gzipped, 14.6M uncompressed ] OpenBSD System Requirements and Supported Devices: -------------------------------------------------- OpenBSD/sparc 2.9 runs on the following classes of machines: - sun4 -- 4/100, 4/200, and 4/300. (note that support for the 4/400 processor is incomplete) - sun4c -- SS1, SS1+, SS2, IPC, ELC, IPX, and SLC - sun4m -- Sun Sparc Classic, LX, 4, 5, 10, 20, and 600MP. Tadpole SPARCbook 3GS and 3GX *** See Notes Below - faithful clones of the above Sun systems (e.g. Integrix, Force) OpenBSD/sparc 2.9 does NOT run on these machines (yet): - Sun 4/400 -- Lacking support for the I/O cache, and related ethernet problems. - sun4d -- SPARCcenter 2000, SPARCserver 1000, XDBus and multiprocessor support issues. - sun4u (Ultrasparcs) -- currently no support for 64-bit Sparc architecture extensions. sun4u will have its own port. - clones that are significantly different from the Sun systems (e.g. Solbourne) The minimal configuration requires 4M of RAM and ~60M of disk space. To install the entire system requires much more disk space, and to run X or compile the system, more RAM is recommended. (OpenBSD with 4M of RAM feels like Solaris with 4M of RAM.) Note that until you have around 16M of RAM, getting more RAM is more important than getting a faster CPU.) Installation from "ramdisk" kernels requires 8M of RAM. Supported devices include: sun4c and sun4m SBus video: cgsix, cgthree, and bwtwo frame buffers sun4m on-board machine specific video: TCX, cgfourteen (aka SX), p9100 (Tadpole 3GS, 3GX) sun4 video (not thoroughly tested...): P4 -- on-board bwtwo, cgfour, cgsix, cgeight VME -- cgtwo, cgthree, cgsix serial ports: ttya and ttyb (can be used as console if needed), ttyc and ttyd (Sun 4/300 only) SBus magma serial port cards, including: 4Sp, 8Sp, 12Sp, 16Sp, LC2+1Sp, 2+1Sp, 4+1Sp, and 8+2Sp. SBus Serial Parallel Interface (SUNW,spif) ethernet: on-board AMD Lance ethernet ("le0"), SBus AMD Lance ethernet cards, on-board Intel 82586 ethernet (ie0 on 4/100's and 4/200's), VME Intel 82586 ethernet cards SBus SunSwift and Quad FastEthernet cards (hme, qfe) SBus FastEthernet cards (qec+be) SBus QuadEthernet cards (qec+qe) SCSI: on-board "esp" SCSI controller (sun4c's, and the 4/300), SBus "esp" SCSI controller (including 3rd party compatibles), Sun "SUN-3"/"si" VME SCSI controller (polled mode only, slow), Sun "SCSI Weird"/"sw" on-board controller (4/110 only, polled) VME disks: Xylogics 7053 VME/SMD disk controller ("xd"), Xylogics 450/451 VME disk controller ("xy") [note: VME/IPI disks are not supported] Audio: sun4c/Classic AMD audio. sun4m (ss4/ss5) CS4231 audio. Miscellaneous devices: Sun floppy disk drive on sun4c machines. Sun keyboard and mouse. Sun SBus Expansion Subsystem (SUNW,xbox) Tadpole microcontroller (tctrl) Force FGA5000 SBus/VME bridge Force system configuration registers Force flash memory Hardware the we do NOT currently support, but get many questions about: Multiprocessor machines (Will not boot correctly on multiple CPU sun4m) Audio driver for some sun4m machines (LX,ZX,ss10,ss20) Floppy driver for sun4m (can boot/install from ramdisk floppies though) Interrupt driven SCSI driver for Sun 4/100's and 4/200's VME mti 16-port serial card VME alm2 16-port serial card VME mcp 4-port serial card VME IPI controller VME cgfive framebuffer VME cgnine framebuffer VME GP/GP2 Graphics Processor SBus cgeight framebuffers SBus GS framebuffer (aka cgtwelve) SBus GT framebuffer ("Graphics Tower") SBus ZX framebuffer (aka Leo) Tadpole onboard PCMCIA and modem *** Note: sun4m and general sparc caveats As of the OpenBSD 2.9 release there are still a few outstanding problems with OpenBSD on some Sparc architectures. Certain lower end CPU modules are known to have problems, in particular the cache-less SM30 and SM40. Support for the Viking/SuperSPARC implementations with cache has improved dramatically. Some sun4m machines are lacking useful floppy/audio support and the VME bus on the 600MP is unsupported. The supplied GENERIC kernel is the best attempt at a configuration that works on the widest range of machinery (sun4, sun4c, and sun4m). If you have problems with the OpenBSD 2.9 kernel in this distribution, please visit the OpenBSD web page (http://www.openbsd.org) and the mailing lists to review the current status and check for updates and distribution errata. If you have Sparc hardware you can donate or make available at nominal cost, please mention this on the lists, many things aren't being tested or developed simply because developers usually have only a Sparcstation at hand, not an array of systems. Donation or mid/long term loan of UltraSparc (sun4u) or HyperSparc (sun4m) systems would help ensure the long-term viability of OpenBSD on Sparc based systems. Your support in terms of documenting previously unknown problems with OpenBSD/sparc, helping debug known problems, implementing missing pieces, and testing OpenBSD on various architectures is actively encouraged. The OpenBSD mailing lists, web-pages and sendbug utility are your best tools for helping make OpenBSD/sparc a better release. Getting the OpenBSD System onto Useful Media: --------------------------------------------- Installation is supported from several media types, including: FFS partitions Tape Remote NFS partition CD-ROM FTP HTTP Not all methods are supported on all Sparc Systems and some of them work only with the floppy or the miniroot installation. If you have the OpenBSD CD-ROM distribution (and a CD-ROM drive), you may be able boot from it. Not all sparc systems support booting from CD-ROM and the current boot images is only known to work on sun4c and some sun4m architecture workstations. If you can boot from the CD-ROM, you are home free and can proceed to the installation steps. If not, you will need to do some setup work to prepare a bootable image, either a floppy, hard drive, or compatible net boot server. In addition to the bootable image, you also need to consider how to access the binary distribution sets to actually install the system. If you have the OpenBSD CD-ROM distribution you can either access the CD-ROM directly from the bootable image or remotely mounted on another system via NFS. Although you can access the distribution sets directly from the CD-ROM or from one of the FTP mirrors over the internet, you may wish to transfer the sets to a local FTP 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 bootable floppy disk using DOS/Windows: First you need to get access to the OpenBSD Bootable floppy images. If you can access the CD-ROM distribution under DOS the bootable disks are in the 2.9/sparc directory, otherwise you you will have to download them from one of the OpenBSD ftp or http mirror sites, using ftp or a web-viewer. In either case, take care to do "binary" transfers, since these are images files and any DOS cr/lf translations or control/z EOF interpretations will result in corrupted transfers. You will also need to go to the "tools" directory and grab a copy of the rawrite.exe utility and its documentation. This program is needed to correctly copy the bootable filesystem image to the floppy, since it's an image of a unix partition containing a ffs filesystem, not a MSDOS format diskette. Once you have installed rawrite.exe, just run it and specify the name of the bootable image, such as "floppy.fs" and the name of the floppy drive, such as "a:". Be sure to use good quality HD (1.44MB) floppies, formatted on the system you're using. The image copy and boot process is not especially tolerant of read errors. Note that if you are using NT to write the images to disk, you will need to use ntrw.exe instead. It is also available in the "tools" directory. Grab it and run in with the correct arguments like this "ntrw :" Note that, when installing, the boot floppy can be write-protected (i.e. read-only). Creating a bootable floppy disk using SunOS or other Un*x-like system: First, you will need obtain a local copy of the bootable filesystem image as described above. If possible use cksum or md5 to verify the checksums of the images vs. the values in the CKSUM or MD5 files on the mirror site. Next, use the dd(1) utility to copy the file to the floppy drive. Under SunOS, the command would be: dd if=floppy29.fs of=/dev/rfd0c bs=36b If you are using something other than SunOS, you may have to adapt this to conform to local naming conventions for the floppy and options suitable for copying to a "raw" floppy image. The key issue is that the device name used for the floppy *must* be one that refers to the whole 2880 block image, not a partition or compatibility mode, and the copy command needs to be compatible with the requirement that writes to a raw device must be in multiples of 512-byte blocks. The variations are endless and beyond the scope of this document. If you're doing this on the system you intend to boot the floppy on, copying the floppy back to a file and doing a compare or checksum is a good way to verify that the floppy is readable and free of read/write errors. Creating a bootable hard disk using SunOS or other Un*x-like system: If you don't have a floppy drive you can copy the single floppy installation image "floppy29.fs" or the mini-root "miniroot29.fs" onto the hard disk you intend to boot on. Traditionally, the way to do this is to use dd(1) to place the bootable filesystem image in the "swap" partition of the disk (while running in single user mode), and then booting from that partition. Using the "b" partition allows you to boot without overwriting any useful parts of the disk, you can also use another partition, but don't used the "a" or "c" partition without understanding the disklabel issues described below under "incompatible systems". This requires that you be running SunOS, Solaris, OpenBSD or NetBSD which have a compatible view of SunOS disk labels and partitions. Use the dd(1) utility to copy the file to the hard drive. Under SunOS, the command would be: dd if=floppy29.fs of=/dev/rsd0b bs=36b - or - dd if=miniroot29.fs of=/dev/rsd0b bs=36b The blocksize is arbitrary as long as it's a multiple of 512-bytes and within the maximum supported by the driver, i.e. bs=126b may not work for all cases. Again, device/partition names may vary, depending on the OS involved. If you are preparing the hard drive on an incompatible system or don't care about the hard disk contents, you can also install the bootable image starting at the beginning of the disk. This lets you prepare a bootable hard-drive even if don't have a working operating system on your Sparc, but it important to understand that the bootable image installed this way includes a "disk label" which can wipe out any pre-existing disklabels or partitioning for the drive. The floppy image is used only for booting, and can be placed in a partition that will be overwritten during the install process, since it actually runs off a ram-disk image in the kernel. In contrast the miniroot is a normal unix root filesystem and you must place in a partition that will not be overwritten until you've completed the installation process. To copy the floppy image to the whole disk, overwriting labels: dd if=floppy29.fs of=/dev/rsdXc bs=36b Two notes - X should be replaced by the unit number of the target disk, which is most likely *not* the disk/partition that's your current root partition. Again names may vary depending on the OS involved. Second, after doing this, the disklabel will be one that would be appropriate for a floppy, i.e. one partition of 2880 block, and you'll probably want to change that later on. If you're starting with a virgin disk and trying to do this under SunOS, use format(8) and newfs(8) to set up the partitions and mark the intended partition as an normal partition type. If you're using OpenBSD, perhaps on another architecture, OpenBSD will create a "fictitious label" that will let you access the whole disk. To copy the floppy image to the hard disk, preserving SunOS, Solaris NetBSD or OpenBSD labels: dd if=floppy29.fs of=/dev/rsdXc bs=1b skip=1 seek=1 You need to be sure that your version of dd(1) supports the skip and seek operands, otherwise you can try a technique like: dd if=/dev/rsdXc of=/tmp/label bs=1b count=1 dd if=floppy29.fs of=/dev/rsdXc bs=36b dd if=/tmp/label of=/dev/rsdXc bs=1b count=1 In either case, you've created a situation where the disklabel and the filesystem information don't agree about the partition size and geometry, however the results will be usable. Creating a network bootable setup using SunOS or other Un*x-like system: The details of setting up a network bootable environment vary considerably, depending on the network's host. Extract the OpenBSD diskless(8) man page from the man29.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 new single floppy 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 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=/dev/nrst0 mt -f ${tape} rewind if test $# -lt 1 then for file in bsd.rd boot do dd if=${file} of=${tape} obs=8k conv=sync done fi for file in base etc comp game man misc xbase xfont xserv xshare do dd if=${file}29.tgz of=${tape} obs=8k conv=sync done tar cf ${tape} bsd mt -f ${tape} offline # end of script And then: cd .../2.9/sparc 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.9/sparc sh -x /tmp/maketape noboot If you're using a system other than OpenBSD or SunOS, the tape name and other requirements may change. 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 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 "base29" 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: ----------------------------------------------- Before you start you might need to consider your disk configuration to sort out a quirk in SCSI-ID to SD-UNIT mapping that exists on Sun Sparcstations. Upon leaving the factory, SunOS and the OpenBOOT ROM map according to this table: SCSI-ID -> SunOS SD-UNIT 0 sd3 1 sd1 2 sd2 3 sd0 4 sd4 5 sd5 6 sd6 Unlike SunOS and the OpenBOOT ROM, a generic OpenBSD kernel numbers scsi drives sequentially as it finds them. The drive with the lowest scsi-id will be called sd0, the next one sd1, etc. To ease the installation process, two OpenBSD kernels are provide in the installation sets. The default OpenBSD kernel (bsd) is set up to use the OpenBSD mapping, while a special kernel (bsd.scsi3) is set up to match the Sun mapping above by hard-wiring scsi-id#3 to sd0 and scsi-id#0 to sd3. The remaining drives will be dynamically mapped to other sd* numbers. This is mostly a non-issue if you have only one drive on your system, but can get confusing if you have multiple drives. If you plan to eliminate SunOS altogether it may be best to correct the scsi-id's of your drives, while if you plan to leave SunOS installed, it may be better to install OpenBSD on a drive with scsi-id 1 or 0. Some OpenBoot proms provide an environment variable that controls the drive<->scsi-id mapping, you can change this to reflect the natural ordering or just set the boot related variables to boot from the correct drive, whatever the numbering. NOTE: if you elect to build a custom kernel you may want to "hardwire" the scsi-id's to sd0->scsi-id 0 or your desired scheme, this helps prevent accidents if you change the SCSI bus configuration or a drive is down. Your OpenBOOT ROM may need some setup. If you are running OpenBSD on a sun4c, or sun4m system, the ROM must be set to "new" command mode. If your sun4c or sun4m machine comes up and gives you a `>' prompt instead of `ok', type: >n ok setenv sunmon-compat? false ok This is needed because OpenBSD relies on the behaviour of the "new" command mode. OpenBSD will not boot correctly on sun4c or sun4m systems that are not running in "new" command mode. The sun4 systems such as the 4/110, 4/200, and 4/300 system do not have a "new" command mode, and will work fine as-is. Also, you cannot use the security modes of the sparc OpenBOOT ROM. Make sure that the ROM security modes are disabled: ok setenv security-mode none Please note that while OpenBSD and SunOS have a reasonable degree of compatibility between disk labels and filesystems there are some problems to watch out for during initial installation or when trying to maintain both OpenBSD and SunOS environments on the same system. If the OpenBSD fsck(8) utility is used on a SunOS filesystem, it will set OpenBSD "clean flags" and BSD4.4 summary fields in the superblock. SunOS does *not* like this and you will have to do a "fsck -b 32" under SunOS to access an alternate superblock to repair the filesystem. You should always specify SunOS filesystem with a "pass number" of 0 in their /etc/fstab entry to prevent this, and preferably mount them "RO". If SunOS fsck is used on an OpenBSD filesystem in the default OpenBSD (4.4BSD) format, it will first complain about the superblock and then about missing . and .. entries. Do *not* try to "correct" these problems, as attempting to do so will completely trash the filesystem. You should avoid using soft updates (option softdep in /etc/fstab) on your shared filesystems. Although untested, it is likely that SunOS would be confused by a filesystem with soft update flags enabled. The OpenBSD "Sun Compatible" disklabel 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 partitions 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 and are careful to read and remember the information which is presented to you by the install program, it shouldn't be too much trouble. Before you begin, you should know the geometry of your hard disk, i.e. the sector size (note that sector sizes other than 512 bytes are not currently supported), the number of sectors per track, the number of tracks per cylinder (also known as the number of heads), and the number of cylinders on the disk. The OpenBSD kernel will try to discover these parameters on its own, and if it can it will print them at boot time. If possible, you should use the parameters it prints. (You might not be able to because you're sharing your disk with another operating system, or because your disk is old enough that the kernel can't figure out its geometry.) There are several ways to install OpenBSD onto a disk. The easiest way in terms of preliminary setup is to use the OpenBSD miniroot that can be booted off your local disk's swap partition. The normal way is to use the OpenBSD installation floppy, or an installation tape. If your Sparc 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). Booting from the Installation Media: Prior to attempting an installation, you should make sure that everything of value on the target system has been backed up. While installing OpenBSD does not necessarily wipe out all the partitions on the hard disk, errors during the install process can have unforeseen consequences and you will probably render the system unbootable if you start, but do not complete the installation. Having the installation media for the prior installation, be it a SunOS or OpenBSD CD-ROM or OpenBSD install diskettes is good insurance if you want to be able to "go back" for some reason. After taking care of all that, bring your system down gracefully using the shutdown(8) and/or halt(8) commands. This will get you to the monitor prompt. Sun PROM monitor commands and setup differ considerably depending on the system architecture and age, you may needed to reference the PROM monitor manual for your system for details. There are four main cases: sun4 (older servers, deskside workstations): prompt is a ">", boot command is "b", uses sd(c,s,p) syntax with s defined as scsi-unit*8+lun in hex OpenBoot Version 1 (newer servers, desktop workstations): prompt is "ok", boot command is "boot" uses sd(c,s,p) syntax with s defined as scsi-unit. OpenBoot Version 2 (newer servers, desktop workstations): prompt is "ok", boot command is "boot" uses diskn:p syntax. OpenBoot Version 2 (certain newer desktop workstations): prompt is "ok", boot command is "boot" uses diskn syntax unless booting from a non-standard partition, in which case: boot /sbus/esp/sd@t,0:p bsd (where "t" is the scsi target, and "p" is the partition. examples would be t="3" and p="b") If you expect your workstation to have an OpenBoot Prom but get a ">", enter then "n" command to enter the "new command mode". You can set this as the default by doing a "setenv sunmon-compat? false" command, followed by a "reset" command. Note that OpenBoot Proms also do the Sun SCSI-ID shuffle for disks, this is described elsewhere in some detail. For the purposes of this section, drive 0 refers to the internal or first SCSI drive, which usually has a SCSI-ID of 3. Booting from Floppy Disk installation media: ok boot fd()bsd # for version 1 OpenBOOT ROMs ok boot floppy bsd # for version 2 OpenBOOT ROMs This will cause the kernel contained in the floppy to be booted. After the initial device probe messages you'll asked to start the install or upgrade procedure. Proceed to the section ``Running the installation scripts'' below. Booting From CD-ROM installation media: > b sd(,30,0)2.9/sparc/bsd.rd # for Sun4 monitors* # (not working currently) ok boot sd(,6,0)2.9/sparc/bsd.rd # for version 1 OpenBOOT ROMs ok boot cdrom 2.9/sparc/bsd.rd # for version 2 OpenBOOT ROMs If the boot is successful, you will get a loader version message, executable sizes and then the Kernel copyright and device probe messages. Boot failure modes are typically a lot of CD-ROM drive activity, but no messages or complaints about magic numbers, checksums or formats. Not all sparc systems support bootable CDROMS and the current boot image is only known to work on sun4c and sun4m architectures. If it does not work, you'll have to create a boot floppy or bootable hard disk using the instructions under preparing boot media. After the initial device probe messages you'll asked to start the install or upgrade procedure. Proceed to the section ``Running the installation scripts'' below. Booting from SCSI disk (miniroot or floppy image): Boot the miniroot by typing the appropriate command at the PROM: > b sd(,,1)bsd # for sun4 monitors* ok boot sd(,,1)bsd # for version 1 OpenBOOT ROMs ok boot disk:b bsd # for version 2 OpenBOOT ROMs ok boot /sbus/esp/sd@3,0:b bsd # for version 2 OpenBOOT ROMs # that won't take disk:p syntax. If you've loaded the miniroot onto some other disk than the default drive 0, modify the boot specifier accordingly, keeping in mind the drive vs. scsi-id shuffling and partition a=0, b=1... > b sd(0,10,1)bsd # example - scsi target 2 on sun4 monitors* ok boot sd(0,3,1)bsd # example - scsi target 0 on v1 OpenBOOT ROM ok boot disk3:b bsd # example - scsi target 0 on v2 OpenBOOT ROM ok boot /sbus/esp/sd@0,0:b bsd # example - scsi target 0 on v2 # OpenBOOT ROM that won't take # disk:p syntax. (*) for sun4 this is scsi-target*8+scsi-lun (usually 0) expressed in hex... This will cause the kernel contained in the miniroot to be booted. After the initial device probe messages you'll asked to start the install or upgrade procedure. Proceed to the section ``Running the installation scripts'' below. Booting from SCSI tape: Boot the miniroot by typing the appropriate command at the PROM: > b st(,,1) # for sun4 monitors # (not working currently) ok boot st(,,1) # for version 1 OpenBOOT ROMs ok boot tape:1 # for version 2 OpenBOOT ROMs ok boot /sbus/esp/st@4,0:1 # for version 2 OpenBOOT ROMs # that won't take tape:n syntax. The above instructions assume your tape drive is the default tape drive using SCSI id 4. If your drive uses id 5, modify the boot command accordingly: > b st(,28,1) # example - 2nd tape drive on sun4 monitors ok boot st(,5,1) # example - 2nd tape drive on v1 OpenBOOT ROM ok boot tape1:1 # example - 2nd tape drive on v2 OpenBOOT ROM ok boot /sbus/esp/st@5,0:1 # example - 2nd tape drive on v2 # OpenBOOT ROM that won't take # tape:n syntax 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 PROM version in your machine, this command takes one of the following forms: > b le()bsd.rd # for sun4 monitors ok boot le()bsd.rd # for version 1 OpenBOOT ROMs ok boot net bsd.rd # for version 2 OpenBOOT ROMs 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. Installing using the Floppy, CD-ROM, tape, miniroot or netboot procedure: You should now be ready to install OpenBSD. The following is a walk-through of the steps you will take while getting OpenBSD installed on your hard disk. If any question has a default answer, it will be displayed in brackets ("[]") after the question. If you wish to stop the installation, you may hit Control-C at any time, but if you do, you'll have to begin the installation process again from scratch. Using Control-Z to suspend the process may be a better option, or at any prompt enter '!' to get a shell, from which 'exit' will return you back to that prompt (no refresh of the prompt though). Boot your machine from the installation media as described above. It will take a while to load the kernel especially from a floppy or slow network connection, most likely more than a minute. If some action doesn't eventually happen, or the spinning cursor has stopped and nothing further has happened, either your boot media is bad, your diskless setup isn't correct, or you may have a hardware or configuration problem. Once the kernel has loaded, you will be presented with the OpenBSD kernel boot messages. You will want to read them to determine your disk's name and geometry. Its name will be something like "sd0" or "wd0" and the geometry will be printed on a line that begins with its name. As mentioned above, you will need your disk's geometry when creating OpenBSD partitions. You will also need to know the device name to tell the install tools what disk to install on. If you cannot read the messages as they scroll by, do not worry -- you can get at this information later inside the install program. While booting, you 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/sparc can boot from the floppy drive, the kernel itself lacks a floppy driver for some architectures. 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). 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 (e.g. "sd0") with the letter identifying the partition (e.g. "d") appended (e.g. "sd0d"). Then it will ask where this partition is to be mounted, e.g. /usr. This process will be repeated until you 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 media flags to set. This is driver dependent, but for the sparc le(4) driver, the flags usually carry meaning: auto Use existing setting (only setup by netboot) 10baseT Use UTP (twisted pair) port 10base5 Use AUI port *** IMPORTANT - these are the correct setting for Sparc 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.9 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.9/sparc is almost always correct. 5) The login and password for the ftp account. You will only be asked for a password for non-anonymous ftp. For instructions on how to complete the installation via ftp, see the section named "Common URL installations" below. To install via HTTP: To begin an HTTP install you will need the following pieces of information: 1) Proxy server URL if you are using a URL-based http proxy (squid, CERN ftp, Apache 1.2 or higher). You need to define a proxy if you are behind a firewall that blocks outgoing http connections (assuming you have a proxy available to use). 3) The IP address (or hostname if you enabled DNS earlier in the install) of an http server carrying the OpenBSD 2.9 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 CD-ROM: When installing from a CD-ROM, you will be asked which device holds the distribution sets. This will typically be either "cd0" or "acd0". Next you will be asked which partition on the CD-ROM the distribution is to be loaded from. This is normally partition "a". Next you will have to identify the file system type that has been used to create the distribution on the CD-ROM, this can be either FFS or ISO CD9660. The OpenBSD CD distribution uses the CD9660 format. You will also have to provide the relative path to the directory on the CD which holds the distribution, for the sparc this is "2.9/sparc". For instructions on how to complete the installation from the CD-ROM distribution, see the section named "Common file system installations" below. To install from a 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, e.g. `*.tgz' or even `base*|comp*'. It is also possible to enter an arbitrary filename and have it treated as a file set. Once you have selected the file sets you want to install and entered `done' you will be prompted to verify that you really do want to extract file sets. Assuming you acquiesce, the files will begin to extract. If not, you will be given the option of installing sets via one of the other install methods. Common URL installations: Once you have entered the required information, the install program will fetch a file list and present a list of all the distribution sets that were found in the specified directory. (If no valid sets were found, you will be notified and given the option of unpacking any gzipped tar files found or getting a file list if none were found.) At this point you may individually select distribution sets to install or enter `all' to install all of the sets (which is what most users will want to do). You may also enter `list' to get a file list or `done' when you are done selecting distribution sets. You may also use wildcards in place of a file name, e.g. `*.tgz' or even `base*|comp*'. It is also possible to enter an arbitrary filename and have it treated as a file set. Once you have selected the file sets you want to install and entered `done' you will be prompted to verify that you really do want to download and install the files. Assuming you acquiesce, the files will begin to download and unpack. If not, you will be given the option of installing sets via one of the other install methods. When all the selected distribution sets has been extracted, you will be allowed to select which time zone your system will be using, all the device nodes needed by the installed system will be created for you and the file systems will be unmounted. For this to work properly, it is expected that you have installed at least the "base29", "etc29", 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 / The Sun monitor normally tries to load a file called "vmunix". On OpenBOOT ROM systems you can change it to load OpenBSD instead using the following commands: On version 1 OpenBOOT ROMs: >n ok setenv boot-from sd(0,0,0)bsd ok On version 2 OpenBOOT ROMs: ok setenv boot-file bsd ok setenv boot-device /sbus/esp/sd@0,0 On sun4 systems, you may not need to specify the boot file, as the OpenBSD boot blocks will look for "bsd" on the boot device by default. Congratulations, you have successfully installed OpenBSD 2.9. 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.9 distribution might need to be tailored for your site. We recommend you run: man afterboot which will tell you about a bunch of the files needing to be reviewed. If you are unfamiliar with UN*X-like system administration, it's recommended that you buy a book that discusses it. If you will be running your OpenBSD system from a serial console, you may need to edit /etc/ttys and change the terminal type, and getty method from "sun" and "suncons" to "vt100" and "std.9600" or something similar. Also when running from a serial console, you may wish to adjust the eeprom settings for input-device, output-device, screen-#columns, and screen-#rows as appropriate. If you plan on using the extra serial ports on 4/300 systems, you'll need to make sure you have device nodes for them e.g.: mknod /dev/ttyc c 12 4 mknod /dev/ttyd c 12 5 To use these ports for terminals etc, you will want to add them to /etc/ttys. In order to use 'tip' on OpenBSD/sparc, you'll need to edit /etc/ttys and add "local" to the end of the tty configuration line, and run 'ttyflags -a' to put your changes into effect. 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, base29.tgz and etc29.tgz) gunzip (GNU gzip) SunOS binary gtar (GNU tar) SunOS binary a "/boot" file from a SunOS machine that matches your machine type (e.g. sun or sun4c) a kernel, most likely "/bsd" All these pieces, except "/boot" and the GNU utilities are supplied in the OpenBSD/sparc distribution. You need to format and partition the disk using SunOS (since OpenBSD/sparc uses SunOS disk labels.) Give yourself adequate partition sizes. Here is an example layout: partition size offset will be.. sd0a 80000 0 / sd0b 256000 80000 swap sd0c 4165271 0 `whole disk' sd0d 100000 436000 /var sd0f 100000 336000 /tmp sd0g 3229271 936000 /usr sd0h 400000 536000 /var/tmp Use SunOS to newfs the partitions which will have filesystems on them. (OpenBSD's filesystem format is identical to SunOS). sunos# newfs /dev/rsd0a [... lots of output] Repeat for any other partition (in this example, /dev/rsd0d, /dev/rsd0f, /dev/rsd0g, /dev/rsd0h). NOTE: If you are able to, there is a performance benefit from newfs'ing using OpenBSD. If you newfs using the OpenBSD newfs command, be sure to use the -O flag for your / partition, so that newfs will use the 4.3BSD filesystem format, rather than the new 4.4BSD filesystem format. If you forget, you will not be able to boot -- the SunOS boot blocks do not understand the extended 4.4BSD filesystem format. Mount those partitions in a tree formation, under /mnt; ie: sunos# df Filesystem kbytes used avail capacity Mounted on [...] /dev/sd0a 38427 0 38427 0% /mnt /dev/sd0d 48249 0 48249 0% /mnt/var /dev/sd0f 48249 0 48249 0% /mnt/tmp /dev/sd0g 1564024 0 1564024 0% /mnt/usr /dev/sd0h 193536 0 193536 0% /mnt/var/tmp Place a standard SunOS "boot" program in /mnt (your new root partition), and use the SunOS command "installboot" to make it work. The installboot man page says to do something like this: sunos# cp /usr/mdec/sdboot /mnt/boot sunos# sync; sync sunos# /usr/mdec/installboot -vlt /mnt/boot /usr/mdec/bootsd /dev/rsd2a You can now extract the provided "*.tgz files onto your disk. sunos# ls -FC base29.tgz comp29.tgz man29.tgz xfont29.tgz bsd etc29.tgz misc29.tgz xserv29.tgz bsd.scsi3 game29.tgz xbase29.tgz sunos# gunzip < base29.tgz | (cd /mnt; gtar xvpf -) [...] for each set And finally copy an OpenBSD kernel (either bsd or bsd.scsi3) onto your disk. sunos# cp bsd.scsi3 /mnt/bsd The GNU gunzip and gtar programs are not distributed as part of SunOS, but may be present in your /usr/local/bin. If not, you will need to obtain them from a GNU archive and install before proceeding. The OpenBSD tar files are in the "new format" that includes directory information, and the standard SunOS tar will not extract from them successfully. After the files have been extracted, 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 Sparcstation expects to be able to download a second stage bootstrap program via TFTP after having acquired its IP address through RevARP when instructed to boot "over the net". It will look for a filename composed of the machine's IP address followed by the machine's architecture, separated by a period. For example, a sun4c machine which has been assigned IP address 130.115.144.11, will make an TFTP request for `8273900B.SUN4C'. Normally, this file is a symbolic link to an appropriate second-stage boot program, which should be located in a place where the TFTP daemon can find it (remember, many TFTP daemons run in a chroot'ed environment). You can find the boot program in `/usr/mdec/boot' in the OpenBSD/sparc distribution. Unfortunately, it is necessary to install this file differently for sun4 and sun4c clients: the sun4 version needs to have its `a.out' header stripped off (otherwise the machine will crash), while the sun4c version must retain it (otherwise the PROM will complain). Here's an example to illustrate this whole mess: server# cd //usr/mdec if client is a sun4: server# set SKIP=1 server# set KARCH=SUN4 else server# set SKIP=0 server# set KARCH=SUN4C server# dd if=boot of=/tftpboot/boot.sparc.OpenBSD.$KARCH skip=$SKIP bs=32 server# cd /tftpboot server# ln -s boot.sparc.OpenBSD.$KARCH 8273900B.$KARCH After the boot program has been loaded into memory and given control by the PROM, it starts locating the machine's remote root directory through the BOOTPARAM protocol. First a BOOTPARAM WHOAMI request is broadcast on the local net. The answer to this request (if it comes in) contains the client's name. This name is used in 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 miniroot29.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 `base29.tgz' and `etc29.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 base29.tgz end up in the correct location. One way to do this is to temporarily use a loopback mount on the server, re-routing /usr to your server's exported OpenBSD "/usr" directory. Also put the kernel and the install/upgrade scripts into the root directory. A few configuration files need to be edited: /etc/hosts Add the IP addresses of both server and client. /etc/myname This files contains the client's hostname; use the same name as in /etc/hosts. /etc/fstab Enter the entries for the remotely mounted filesystems. For example: server:/export/root/client / nfs rw 0 0 server:/export/exec/sun4.OpenBSD /usr nfs rw 0 0 Now you must populate the the `/dev' directory for your client. If you server runs SunOS 4.x, you can simply change your working directory to `/dev' and run the MAKEDEV script: `sh MAKEDEV all'. On SunOS 5.x systems, MAKEDEV can also be used, but there'll be error messages about unknown user and groups. These errors are inconsequential for the purpose of installing OpenBSD. However, you may want to correct them if you plan to the diskless setup regularly. In that case, you may re-run MAKEDEV on your OpenBSD machine once it has booted. Upgrading a previously-installed OpenBSD System: ------------------------------------------------ To upgrade OpenBSD 2.9 from a previous version, start with the general instructions in the section "Installing OpenBSD". Boot from the miniroot or the installation floppy. When prompted, select the (U)pgrade option rather than the (I)nstall option at the prompt in the install process. The upgrade script will ask you for the existing root partition, and will use the existing filesystems defined in /etc/fstab to install the new system in, and also preserve 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. 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.9/packages/sparc to see which packages are available for your hardware architecture. That directory will be on the same CD-ROM containing the OS installation files for your architecture. To install one or more of these packages you must 1) become the superuser (root) 2) mount the appropriate CD-ROM 3) use the ``pkg_add'' command to install the software Example (in which we use su(1) to get superuser privileges, thus you have to be in group "wheel", see the manual page for su(1)). $ su Password: # mkdir -p /cdrom # mount /dev/cd0a /cdrom # pkg_add /cdrom/2.9/packages/sparc/ # # 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.9/packages/sparc/ You may want to peruse this to see what packages are available. The packages are also on the OpenBSD FTP mirror sites. See http://www.openbsd.org/ftp.html for a list of current ftp mirror sites. Installation of a package is very easy. 1) become the superuser (root) 2) use the ``pkg_add'' command to install the software ``pkg_add'' is smart enough to know how to download the software from the OpenBSD ftp server. Example: $ su Password: # pkg_add ftp://ftp.openbsd.org/pub/OpenBSD/2.9/packages/sparc/emacs-20.3.tgz 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 freetype-1.2.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.