INSTALLATION NOTES for OpenBSD/sparc64 6.7 What is OpenBSD? ---------------- OpenBSD is a fully functional, multi-platform UN*X-like Operating System based on Berkeley Networking Release 2 (Net/2) and 4.4BSD-Lite. There are several operating systems in this family, but OpenBSD differentiates itself by putting security and correctness first. The OpenBSD team strives to achieve what is called a "secure by default" status. This means that an OpenBSD user should feel safe that their newly installed machine will not be compromised. This "secure by default" goal is achieved by taking a proactive stance on security. Since security flaws are essentially mistakes in design or implement- ation, the OpenBSD team puts as much importance on finding and fixing existing design flaws and implementation bugs as it does writing new code. This means that an OpenBSD system will not only be more secure, but it will be more stable. The source code for all critical system components has been checked for remote-access, local-access, denial- of-service, data destruction, and information-gathering problems. In addition to bug fixing, OpenBSD has integrated strong cryptography into the base system. A fully functional IPsec implementation is provided as well as support for common protocols such as SSL and SSH. Network filtering and monitoring tools such as packet filtering, NAT, and bridging are also standard, as well as several routing services, such as BGP and OSPF. For high performance demands, support for hardware cryptography has also been added to the base system. Because security is often seen as a tradeoff with usability, OpenBSD provides as many security options as possible to allow the user to enjoy secure computing without feeling burdened by it. Because OpenBSD is from Canada, the export of Cryptography pieces (such as OpenSSH and IPsec) 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 a mirror server in the US if you are outside of Canada and the US.) A list of software and ideas developed by the OpenBSD project is available on the web at https://www.OpenBSD.org/innovations.html. A comprehensive list of the improvements brought by the 6.7 release is also available at https://www.OpenBSD.org/67.html. OpenBSD/sparc64 runs on 64-bit UltraSPARC-based machines, including most of Sun Microsystems (now Oracle) workstations and their clones. Sources of OpenBSD: ------------------- Please refer to https://www.openbsd.org/ftp.html for all the ways you may acquire OpenBSD. OpenBSD 6.7 Release Contents: ----------------------------- The OpenBSD 6.7 release is organized in the following way. In the .../6.7 directory, for each of the architectures having an OpenBSD 6.7 binary distribution, there is a sub-directory. The sparc64-specific portion of the OpenBSD 6.7 release is found in the "sparc64" subdirectory of the distribution. That subdirectory is laid out as follows: .../6.7/sparc64/ INSTALL.sparc64 Installation notes; this file. SHA256 Output of the cksum(1) program using the option -a sha256, usable for verification of the correctness of downloaded files. SHA256.sig The above file, signed with the OpenBSD signing key for the 6.7 release, usable for verification of the integrity of the above file, and thus of the downloaded files. miniroot67.fs A miniroot filesystem image to be used if you for some reason can't or don't want to use the ramdisk installation method. It can be copied to the swap partition of an existing OpenBSD, Solaris, NetBSD, or Linux installation to allow installing or upgrading to OpenBSD 6.7. floppy67.fs The standard sparc64 boot and installation floppy; see below. This floppy image will boot on some SBus-based sparc64 models, such as: - Ultra 1/1E - Ultra 2 floppyB67.fs Another sparc64 boot and installation floppy; see below. This floppy image will boot on some PCI-based sparc64 models, such as: - SPARCengineUltra AX - SPARCengineUltra AXe - SPARCengineUltra AXi *.tgz sparc64 binary distribution sets; see below. bsd A stock GENERIC sparc64 kernel which will be installed on your system during the install. bsd.mp A stock GENERIC.MP sparc64 kernel, with support for multiprocessor machines, which can be used instead of the GENERIC kernel after the install. bsd.rd A compressed RAMDISK kernel; the embedded filesystem contains the installation tools. Used for simple installation from a pre-existing system. install67.iso The sparc64 boot and installation CD-ROM image, which contains the base and X sets, so that install or upgrade can be done without network connectivity. cd67.iso A simple bootable filesystem image consisting of the bsd.rd installation kernel, suitable to be used as a bootable CD-ROM image, but will require the base and X sets be found via another media or network. installboot The OpenBSD/sparc64 boot loader installation program. bootblk The OpenBSD/sparc64 boot block. ofwboot The OpenBSD/sparc64 secondary boot loader. ofwboot.net The OpenBSD/sparc64 network boot loader. Please note that there are multiple bootable images and kernels, intended to allow installing OpenBSD/sparc64 in a variety of situations without requiring a pre-existing working operating system. The kernel and boot images are provided for net booting installations. Bootable installation/upgrade floppy images: The two floppy images can be copied to a floppy using rawrite.exe, ntrw.exe, or "dd", as described later in this document. Each floppy image is a bootable install floppy which can be used both to install and to upgrade OpenBSD to the current version. It is also useful for maintenance and disaster recovery. The OpenBSD/sparc64 binary distribution sets contain the binaries which comprise the OpenBSD 6.7 release for sparc64 systems. There are eight binary distribution sets. The binary distribution sets can be found in the "sparc64" subdirectory of the OpenBSD 6.7 distribution tree, and are as follows: base67 The OpenBSD/sparc64 6.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. [ 108.1 MB gzipped, 241.9 MB uncompressed ] comp67 The OpenBSD/sparc64 Compiler tools. All of the tools relating to C, C++ and Objective-C are supported. This set includes the system include files (/usr/include), the linker, the compiler tool chain, and the various system libraries (except the shared libraries, which are included as part of the base set). This set also includes the manual pages for all of the utilities it contains, as well as the system call and library manual pages. [ 46.0 MB gzipped, 173.0 MB uncompressed ] game67 This set includes the games and their manual pages. [ 2.7 MB gzipped, 7.0 MB uncompressed ] man67 This set includes all of the manual pages for the binaries and other software contained in the base set. Note that it does not include any of the manual pages that are included in the other sets. [ 6.9 MB gzipped, 29.9 MB uncompressed ] xbase67 This set includes the base X distribution. This includes programs, headers and libraries. [ 17.0 MB gzipped, 60.8 MB uncompressed ] xfont67 This set includes all of the X fonts. [ 38.4 MB gzipped, 56.6 MB uncompressed ] xserv67 This set includes all of the X servers. [ 10.0 MB gzipped, 28.0 MB uncompressed ] xshare67 This set includes all text files equivalent between all architectures. [ 4.3 MB gzipped, 28.8 MB uncompressed ] OpenBSD System Requirements and Supported Devices: -------------------------------------------------- OpenBSD/sparc64 6.7 runs on the following classes of machines: Ultra 1/1E Ultra 2 Ultra 3 Mobile Workstation Ultra 5/10 Ultra 25/45 Ultra 30/60/80 SPARCengineUltra AX SPARCengineUltra AXe SPARCengineUltra AXi SPARCengineUltra AXdp SPARCengineUltra AXmp SPARCengine CP1500 Enterprise 150 Enterprise 220R Enterprise 250 Enterprise 420R Enterprise 450 Enterprise 3000/4000/5000/6000 Enterprise 3500/4500/5500/6500 Enterprise 10000 Sun Blade 100/150 Sun Blade 1000/2000 Sun Blade 1500/2500 Sun Blade T6300 Sun Blade T6320 Sun Blade T6340 Sun Fire V100/V120 Sun Fire V125 Sun Fire V210/V240/V440 Sun Fire V215/V245/V445 Sun Fire V250 Sun Fire 280R Sun Fire V480/V880 Sun Fire V490/V890 Sun Fire V1280 Sun Fire T1000/T2000 Sun SPARC Enterprise T1000/T2000 Sun SPARC Enterprise T5120/T5220 (see note below) Sun SPARC Enterprise T5140/T5240 Sun SPARC Enterprise T5440 Sun SPARC Enterprise M4000/M5000/M8000/M9000 Sun SX1500 Sun SX2500 Sun SX3200 Netra AX1105 Netra AX2200 Netra X1 Netra 20/T4 Netra 120 Netra 210/240/440 Netra 1280 Netra 1290 Netra T1 100/105 Netra T1 AC200/DC200 Netra T 1100 Netra T 1120/1125 Netra T 1400/1405 Netra CP3060 Netra CP3260 Netra T2000 Netra T5220 Netra T5440 Sun Fire E2900/E4900/E6900 Fujitsu PRIMEPOWER 1 Fujitsu PRIMEPOWER 250/450 Fujitsu PRIMEPOWER 650/850 (with SPARC64-V processors only) Fujitsu SPARC Enterprise T1000/T2000 Fujitsu SPARC Enterprise T5120/T5220 Fujitsu SPARC Enterprise T5140/T5240 Fujitsu SPARC Enterprise T5440 Fujitsu SPARC Enterprise M4000/M5000/M8000/M9000 as well on faithful clones of the above Sun systems, including: Momentum Leopard-V RDI/Tadpole UltraBook 170/200 Tadpole SPARCLE 550SX/650SX Tadpole Viper Tadpole/Sun Voyager IIi Note: SPARC Enterprise T5120 and T5220 systems need at least OpenBoot 4.28.0 to run OpenBSD. Please refer to the ``Updating your firmware'' section later for firmware update instructions. Even if your machine is not listed above, it is possible that OpenBSD/sparc64 will work on it. OpenBSD/sparc64 does not work on machines with Fujitsu's SPARC64-I, SPARC64-II, SPARC64-III and SPARC64-IV processors. OpenBSD/sparc64 6.7 supports SMP (Symmetrical MultiProcessor) systems. To support SMP operation, a separate SMP kernel (bsd.mp) is included with the installation file sets. 24MB of RAM should be sufficient to boot and a minimal system can probably be squeezed onto a 250MB disk by installing only the `base' set. However, a minimum of 32MB is recommended for serious usage of the system. Verifying the OpenBSD Installation Media: ----------------------------------------- As of OpenBSD 5.5, installations are able to verify files for the next release. The OpenBSD 6.7 release was signed with the /etc/signify/openbsd-67-base.pub release key. If you have an existing OpenBSD 5.5 or higher installation, you can run signify(1) to verify the signature and checksum. For example, run the following to verify that the cd67.iso file was distributed by the OpenBSD team: signify -C -p /etc/signify/openbsd-67-base.pub -x SHA256.sig cd67.iso If you are unable to run or compile signify(1), use sha256(1) with the SHA256 file to see if a file was corrupt during the transfer. Getting the OpenBSD System onto Useful Media: --------------------------------------------- Installation is supported from several media types, including: CD-ROM (NOT supported if booting from floppy) FFS partitions HTTP If you created an OpenBSD CD-ROM (and have a CD-ROM drive), you may be able to boot from it, or from the supplied bootable CD-ROM mini image. If you can boot from the CD-ROM, you are home free and can proceed to the installation steps. If not, you will need to do some setup work to prepare a bootable image, either a floppy, hard drive, or compatible net boot server. In addition to the bootable image, you also need to consider how to access the binary distribution sets to actually install the system. Although you can access the distribution sets directly from one of the OpenBSD mirrors over the internet, you may wish to transfer the sets to a local HTTP server, or copy them to a partition on the target system's disk. Creating a bootable CD-ROM: First you need to get access to the OpenBSD bootable CD-ROM (ISO) images. They can be found on one of the OpenBSD mirror servers. Two files are available, install67.iso which contains all of the sets needed for installation, and a smaller cd67.iso which contains just the installer, for a network install. Windows 7 users should be able to do this by right clicking on the install67.iso file and clicking burn to CD. OpenBSD users should be able to do this with the cdio command. "cdio tao install67.iso" Users of other operating systems should consult the appropriate documentation. Creating a bootable floppy disk using Windows: First you need to get access to the OpenBSD bootable floppy images. If you can access the distribution from the CD-ROM under DOS, you will find the bootable disks in the 6.7/sparc64 directory. Otherwise, you will have to download them from one of the OpenBSD mirror sites, using an FTP client or a web browser. In either case, take care to do "binary" transfers, since these are images files and any DOS cr/lf translations or Control-z EOF interpretations will result in corrupted transfers. You will also need to go to the "tools" directory and grab a copy of the ntrw.exe utility. Run it 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 a Un*x-like system: First, you will need to obtain a local copy of the bootable filesystem image as described above. You should use the signify(1) and sha256(1) commands to verify the integrity of the images with the SHA256.sig file on the mirror site. Next, use the dd(1) utility to copy the file to the floppy drive. The command would likely be, under OpenBSD: dd if=floppy67.fs of=/dev/rfd0c bs=36b If you are using another operating system, you may have to adapt this to conform to local naming conventions for the floppy and options suitable for copying to a "raw" floppy image. The key issue is that the device name used for the floppy *must* be one that refers to the correct block device, not a partition or compatibility mode, and the copy command needs to be compatible with the requirement that writes to a raw device must be in multiples of 512-byte blocks. The variations are endless and beyond the scope of this document. If you're doing this on the system you intend to boot the floppy on, copying the floppy back to a file and doing a compare or checksum is a good way to verify that the floppy is readable and free of read/write errors. Note that, when installing, the boot floppy can be write-protected (i.e. read-only). Creating a bootable hard disk using SunOS, Solaris or other Unix-like system: If you don't have a floppy drive you can copy the miniroot "miniroot67.fs" onto the hard disk you intend to boot on. Traditionally, the way to do this is to use dd(1) to place the bootable filesystem image in the "swap" partition of the disk (while running in single user mode), and then booting from that partition. Using the "b" partition allows you to boot without overwriting any useful parts of the disk; you can also use another partition, but don't use the "a" or "c" partition without understanding the disk label issues described below under "incompatible systems". This requires that you be running SunOS, Solaris, OpenBSD, or NetBSD, which have a compatible view of SunOS disk labels and partitions. Use the dd(1) utility to copy the file to the hard drive. The command would likely be, under SunOS: dd if=miniroot67.fs of=/dev/rsd0b bs=64b and under Solaris: dd if=miniroot67.fs of=/dev/rdsk/c0t0d0s1 bs=64b The blocksize is arbitrary as long as it's a multiple of 512-bytes and within the maximum supported by the driver, i.e. bs=126b may not work for all cases. Again, device/partition names may vary, depending on the OS involved. If you are preparing the hard drive on an incompatible system or don't care about the hard disk contents, you can also install the bootable image starting at the beginning of the disk. This lets you prepare a bootable hard-drive even if don't have a working operating system on your machine, but it is important to understand that the bootable image installed this way includes a "disk label" which can wipe out any pre-existing disklabels or partitioning for the drive. Creating a network bootable setup using SunOS or other Unix-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 man67.tgz distribution set or see the copy on the OpenBSD web page. You will also need to reference the relevant man pages or administrators guide for the host system. Basically, you will need to set up reverse-arp (rarpd) and boot parameter (rpc.bootparamd) information and make the OpenBSD bootblock, kernel/miniroot partition, and a swap file available as required by the netboot setup. The steps necessary to prepare the distribution sets for installation depend on which method of installation you choose. Some methods require a bit of setup first that is explained below. The installation allows installing OpenBSD directly from HTTP 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 download the distribution sets to a local server or disk and perform the installation from there, rather than directly from the internet. The variety of options listed may seem confusing, but situations vary widely in terms of what peripherals and what sort of network arrangements a user has, the intent is to provide some way that will be practical. If you are upgrading OpenBSD, you also have the option of installing OpenBSD by putting the new distribution sets somewhere in your existing file system, and using them from there. To do that, do the following: Place the distribution sets you wish to upgrade somewhere in your current file system tree. At a bare minimum, you must upgrade the "base" binary distribution, and so must put the "base67" set somewhere in your file system. It is recommended that you upgrade the other sets, as well. Preparing your System for OpenBSD Installation: ----------------------------------------------- If your UltraSPARC machine is somewhat old, it might need a firmware update before it can be used under OpenBSD. You are advised to try to install OpenBSD first; if it can't boot or fails mysteriously, you might need to update your firmware. To do so, check the ``Updating your firmware'' section later in this document. Your OpenBOOT ROM may need some setup. You cannot use the security modes of the OpenBOOT ROM. Make sure that the ROM security modes are disabled: ok setenv security-mode none Most of the new Ultras shipped by Sun (or Oracle) with a preinstalled Solaris have an initial specific factory setup of the boot ROM, in order to start up Solaris WebStart at the first boot; the boot-device variable is set to disk:f. Make sure you reset the boot device to its default value: ok set-default boot-device will work for most systems. This can be adapted if you've multiple systems installed and know what you're doing. To disable automatic boot use the following command: ok setenv auto-boot? false and then to enable it later use: ok setenv auto-boot? true or on an installed system use the eeprom(8) command: # eeprom 'auto-boot?=true' Updating your firmware: ----------------------- If OpenBSD does not boot or install properly on your machine, it might need a firmware update. Updating your firmware is a dangerous operation which may damage your hardware. Be sure to carefully follow these instructions and, if in doubt, please don't do this. You will need to have a working operating system installed on your machine, in order to perform the update. If this is not the case, you might be able to boot the flash updater software via network, but this has not been tested and is not supported by Oracle. Firmware update information can be found at http://www.oracle.com/technetwork/systems/patches/firmware/release-history-jsp-138416.html Follow the patch installation notes very carefully. You will need to open your machine in order to apply this patch. Installing the OpenBSD System: ------------------------------ Installing OpenBSD is a relatively simple process. If you take your time and are careful to read the information presented by the installer, you shouldn't have any trouble. There are several ways to install OpenBSD onto a disk. The easiest way in terms of preliminary setup is to use an OpenBSD installation CD-ROM or an installation floppy (if your machine can boot from floppy). If your machine is hooked up to a network, try and find a server to arrange for a diskless setup. This is a convenient way to install on a machine whose disk does not currently hold a usable operating system. This is difficult to get set up correctly the first time, but easy to use afterwards. (See ``Installing using a diskless setup'' below.) Booting from the Installation Media: Prior to attempting an installation, you should make sure that everything of value on the target system has been backed up. While installing OpenBSD does not necessarily wipe out all the partitions on the hard disk, errors during the install process can have unforeseen consequences and you will probably render the system unbootable if you start, but do not complete the installation. Having the installation media for the prior installation, be it a Solaris or OpenBSD CD-ROM or OpenBSD install diskettes, is good insurance if you want to be able to "go back" for some reason. After taking care of all that, bring your system down gracefully using the shutdown(8) and/or halt(8) commands. This will get you to the monitor prompt. Booting from Floppy Disk installation media: ok boot floppy bsd This will cause the kernel contained in the floppy to be booted. Not all systems are able to boot from floppy; also, Ultra 1, 1E, and 2 systems might need a firmware update to be able to boot from floppy; refer to the ``Updating your firmware'' section earlier in this document for details. Booting From CD-ROM installation media: ok boot cdrom If the boot is successful, you will get a loader version message, executable sizes, and then the kernel copyright and device probe messages. Boot failure modes are typically a lot of CD-ROM drive activity, but no messages or complaints about magic numbers, checksums or formats. Booting from disk: Boot the miniroot by typing the appropriate command at the PROM: ok boot disk:b bsd If you've loaded the miniroot onto some other disk than the default drive 0, modify the boot specifier accordingly, keeping in mind the partition naming a=0, b=1... ok boot disk1:b bsd # example - scsi target 1 or # second ide drive Installing using a diskless setup: First, you must set up a diskless client configuration on a server. If you are using an OpenBSD system as the boot-server, have a look at the diskless(8) manual page for guidelines on how to proceed with this. If the server runs another operating system, you'll have to consult documentation that came with it (on SunOS systems, add_client(8) and the Sun System/Networks administrators guide constitute a good start; on Solaris systems, share(1M) is a good starting point as well). Boot your workstation from the server by entering the appropriate `boot' command at the monitor prompt: ok boot net bsd.rd Installing using the Floppy, CD-ROM, miniroot or netboot procedure: You should now be ready to install OpenBSD. The following is a walk-through of the steps you will take while getting OpenBSD installed on your hard disk. The installation procedure is designed to gather as much information about your system setup as possible at the beginning, so that no human interaction is required as soon as the questions are over. The order of these questions might be quite disconcerting if you are used to other installation procedures, including older OpenBSD versions. If any question has a default answer, it will be displayed in brackets ("[]") after the question. If you wish to stop the installation, you may hit Control-C at any time, but if you do, you'll have to begin the installation process again from scratch. Using Control-Z to suspend the process may be a better option, or at any prompt enter "!" to get a shell, from which "exit" will return you back to that prompt. 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 which contain information about the hardware that was detected and supported by OpenBSD. After the kernel is done initializing, you will be asked whether you wish to do an "(I)nstall", "(U)pgrade" or an "(A)utoinstall". Enter "I" for a fresh install or "U" to upgrade an existing installation. Enter "A" to start an unattended installation where all of your answers are supplied in a response file (more on that in "Preparing an unattended installation of OpenBSD"). If you are connected with a serial console, you will next be asked for your terminal type. You should choose the terminal type from amongst those listed. (If your terminal type is xterm, just use vt220). The first question you will be asked is the system hostname. Reply with the name of the system, without any domain part. You will now be given an opportunity to configure the network. The network configuration you enter (if any) can then be used to do the install from another system using HTTP, and will also be the configuration used by the system after the installation is complete. The install program will give you a list of network interfaces you can configure. For each network interface you select to configure, you will be asked for: - the symbolic host name to use (except for the first interface setup, which will reuse the host name entered at the beginning of the installation). - the IPv4 settings: address and netmask. If the IP address should be obtained from a DHCP server, simply enter "dhcp" when asked for the address. - the IPv6 settings (address, prefix length, and default router). You may enter "autoconf" when asked for the address for the interface to configure automatically via router solicitation messages. After all interfaces have been configured, if there have been any IPv4 interfaces setup, you will be asked for the IPv4 default route. This step is skipped if you only have one IPv4 interface setup, and it is configured with DHCP. The install program will also ask you for your DNS domain name, and the domain name servers, unless this information has already been obtained from a DHCP server during interface setup. You will then be asked to enter the initial root password of the system, twice. Although the install program will only check that the two passwords match, you should make sure to use a strong password. As a minimum, the password should be at least eight characters long and a mixture of both lower and uppercase letters, numbers and punctuation characters. You will then be asked whether you want to start sshd(8) by default. You will next be asked whether you intend to run the X Window System on your machine. The install program needs to know this, to change a configuration setting controlling whether the X server will be able to access the xf86(4) driver; it is not necessary to answer "y" to this question if you only intend to run X client programs on a remote display. If you answered "y" to this question, you will get asked whether you want to start xenodm(1) on boot. You will now be given the possibility to setup a user account on the forthcoming system. This user will be added to the "wheel" group. Enter the desired login name, or "n" if you do not want to add a user account at this point. Valid login names are sequences of digits and lowercase letters, and must start with a lowercase letter. If the login name matches this criteria, and doesn't conflict with any of the administrative user accounts (such as "root", "daemon" or "ftp"), you will be prompted for the user's descriptive name, as well as its password, twice. As for the root password earlier, the install program will only check that the two passwords match, but you should make sure to use a strong password here as well. If you have chosen to setup a user account, and you had chosen to start sshd(8) on boot, you will be asked if you want to allow sshd(8) logins as root. Depending on the installation media you are using, you may now be given the opportunity to configure the time zone your system will use. If the installation program skips this question, do not be alarmed: the time zone will be configured at the end of the installation. The installation program will now tell you which disks it can install on, and ask you which it should use. Reply with the name of your root disk. The file system layout is stored in the OpenBSD disk label. Each file system is stored in its own "disk label partition", which is a subdivision of the OpenBSD disk partition you created. In the text below, "partition" refers to these subdivisions. You will be shown a default layout with the recommended file systems. This default layout is based on the disk size. You will be given the choice of accepting the proposed layout, editing it, or creating your own custom layout. These last two choices will invoke the disklabel(8) interactive editor, allowing you to create your desired layout. Within the editor, you will see at least a "c" partition of fstype "unused". This represents the whole disk and cannot be modified. You must create partition "a" as a native OpenBSD partition, i.e. one with "4.2BSD" as the fstype, to hold the root file system. In addition to partition "a" you should create partition "b" with fstype "swap", and native OpenBSD partitions to hold separate file systems such as /usr, /tmp, /var, and /home. You will need to provide a mount point for all partitions you define. Partitions without mount points, or not of the 4.2BSD fstype, will neither be formatted nor mounted during the installation. For quick help while in the interactive editor, enter "?". The "z" command (which deletes all partitions and starts with a clean label), the "A" command (which performs the automatic partition layout) and the "n" command (to change mount points) are of particular interest. Although the partitions' position and size are written in exact sector values, you do not need a calculator to create your partitions! Human-friendly units can be specified by adding "k", "m" or "g" after any numbers to have them converted to kilobytes, megabytes or gigabytes. Or you may specify a percentage of the disk size using "%" as the suffix. Enter "M" to view the entire manual page (see the info on the "-E" flag). To exit the editor enter "q". After the layout has been saved, new filesystems will be created on all partitions with mount points. This will DESTROY ALL EXISTING DATA on those partitions. After configuring your root disk, the installer will return to the list of available disks to configure. You can choose the other disks to use with OpenBSD in any order, and will get to setup their layout similarly to the root disk above. However, for non-root disks, you will not be proposed a default partition layout. When all your disks are configured, simply hit return at the disk prompt. After these preparatory steps have been completed, you will be able to extract the distribution sets onto your system. There are several install methods supported: HTTP, CD-ROM, or a local disk partition. To install via HTTP: To begin an HTTP install you will need the following pieces of information: 1) Proxy server URL if you are using a URL-based HTTP proxy (squid, CERN FTP, Apache 1.2 or higher). You need to define a proxy if you are behind a firewall that blocks outgoing HTTP connections (assuming you have a proxy available to use). 2) The IP address (or hostname if you configured DNS servers earlier in the install) of an HTTP server carrying the OpenBSD 6.7 distribution. The installation program will try to fetch a list of such servers; depending on your network settings, this might fail. If the list could be fetched, it will be displayed, and you can choose an entry from the list (the first entries are expected to be the closest mirrors to your location). 3) The directory holding the distribution sets. Then refer to the section named "installation set selection" below. To install from CD-ROM: When installing from a CD-ROM, you will be asked which device holds the distribution sets. This will typically be "cd0". If there is more than one partition on the CD-ROM, you will be asked which partition the distribution is to be loaded from. This is normally partition "a". You will also have to provide the relative path to the directory on the CD-ROM which holds the distribution, for the sparc64 this is "6.7/sparc64". Then refer to the section named "installation set selection" below. To install from a local disk partition: When installing from a local disk partition, you will first have to identify which disk holds the distribution sets. This is normally "wdN" or "sdN", where N is a number. Next you will have to identify the partition within that disk that holds the distribution; this is a single letter between "a" and "p". You will also have to identify the type of file system residing in the partition identified. Currently, you can only install from partitions that have been formatted as the Berkeley fast file system (ffs). You will also have to provide the relative path to the directory on the file system where the distribution sets are located. Note that this path should not be prefixed with a "/". Then refer to the next section. Installation set selection: A list of available distribution sets found on the given location will be listed. You may individually select distribution sets to install by entering their names or wildcards (e.g. "*.tgz" or "base*|comp*"), or you may enter "all" to select all the sets (which is what most users will want to do). You may also enter "abort" to deselect everything and restart the selection from scratch, or unselect sets by entering their name prefixed with "-" (e.g. "-x*"). It is also possible to enter an arbitrary filename and have it treated as a file set. When you are done selecting distribution sets, enter "done". The files will begin to extract. After the files have been extracted, you will be given the choice to select a new location from which to install distribution sets. If there have been errors extracting the sets from the previous location, or if some sets have been missing, this allows you to select a better source. Also, if the installation program complains that the distribution sets you have been using do not match their recorded checksums, you might want to check your installation source (although this can happen between releases, if a snapshot is being updated on a mirror server with newer files while you are installing). The last thing you might need to configure, if you did not get the chance to earlier, is the time zone your system will be using. For this work properly, it is expected that you have installed at least the "base67" and "bsd" distribution sets. The installation program will then proceed to save the system configuration, create all the device nodes needed by the installed system, and will install bootblocks on the root disk. On multiprocessor systems, if the bsd.mp kernel has been installed, it will be renamed to "bsd", which is the default kernel the boot blocks look for. The single processor kernel, "bsd", will be available as "bsd.sp". Finally, you will be asked whether you would like to install non-free firmware files (which can't be tightly integrated to the OpenBSD system) on first boot, by invoking fw_update(8) on the next boot. After completing an installation: Now try a reboot. (If needed, swap your SCSI IDs first). The UltraSPARC OpenFirmware will normally load the kernel from the device and filename as instructed by the ``boot-device'' and ``boot-file'' variables. If the ``boot-file'' variable is empty, the OpenBSD bootloader will look for a kernel named ``bsd'', unless a different filename has been specified in the boot command. To reset this variable to its default, empty, value, type the following: ok set-default boot-file Congratulations, you have successfully installed OpenBSD 6.7. When you reboot into OpenBSD, you should log in as "root" at the login prompt. You should create yourself an account, if you skipped this step during installation, and protect it and the "root" account with good passwords. The install program leaves root an initial mail message. We recommend you read it, as it contains answers to basic questions you might have about OpenBSD, such as configuring your system, installing packages, getting more information about OpenBSD, sending in your dmesg output and more. To do this, run mail and then just enter "more 1" to get the first message. You quit mail by entering "q". Some of the files in the OpenBSD 6.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. Net Boot or Diskless Setup Information: The set up is similar to the diskless setup, but not identical, because the Sun setup assumes that the bootblocks load a kernel image, which then uses NFS to access the exported root partition, while the OpenBSD bootblocks use internal NFS routines to load the kernel image directly from the exported root partition. Please understand that no one gets this right the first try, since there is a lot of setup and all the host daemons must be running and configured correctly. If you have problems, extract the diskless(8) manpage, find someone who's been through it before and use the host syslog and tcpdump(8) to get visibility of what's happening (or not). Your UltraSPARC expects to be able to download a second stage bootstrap program via TFTP after having acquired its IP address through RevARP when instructed to boot "over the net". It will look for a filename composed of the machine's IP address. For example, a machine which has been assigned IP address 130.115.144.11 will make a TFTP request for `8273900B'. Normally, this file is a symbolic link to an appropriate second-stage boot program, which should be located in a place where the TFTP daemon can find it (remember, many TFTP daemons run in a chroot'ed environment). You can find the boot program in `/usr/mdec/boot' in the OpenBSD/sparc64 distribution. After the boot program has been loaded into memory and given control by the PROM, it starts locating the machine's remote root directory through the BOOTPARAM protocol. First a BOOTPARAM WHOAMI request is broadcast on the local net. The answer to this request (if it comes in) contains the client's name. This name is used in the next step, a BOOTPARAM GETFILE request -- sent to the server that responded to the WHOAMI request -- requesting the name and address of the machine that will serve the client's root directory, as well as the path of the client's root on that server. Finally, this information (if it comes in) is used to issue a REMOTE MOUNT request to the client's root filesystem server, asking for an NFS file handle corresponding to the root filesystem. If successful, the boot program starts reading from the remote root filesystem in search of the kernel which is then read into memory. You will want export the miniroot67.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 `base67.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 base67.tgz end up in the correct location. One way to do this is to temporarily use a loopback mount on the server, re-routing /usr to your server's exported OpenBSD "/usr" directory. Also put the kernel and the install/upgrade scripts into the root directory. A few configuration files need to be edited: /etc/hosts Add the IP addresses of both server and client. /etc/myname This files contains the client's hostname; use the same name as in /etc/hosts. /etc/fstab Enter the entries for the remotely mounted filesystems. For example: server:/export/root/client / nfs rw 0 0 server:/export/exec/sparc64.OpenBSD /usr nfs rw 0 0 Now you must populate the "/dev" directory for your client. If the server does not run OpenBSD you might save the MAKEDEV output: eo=echo ksh MAKEDEV all > all.sh and then tailor it for your server operating system before running it. Note that MAKEDEV is written specifically for ksh, and may not work on any other Bourne shell. There will be error messages about unknown users and groups. These errors are inconsequential for the purpose of installing OpenBSD. However, you may want to correct them if you plan to use the diskless setup regularly. In that case, you may re-run MAKEDEV on your OpenBSD machine once it has booted. Preparing an unattended installation of OpenBSD: ------------------------------------------------ If "(A)utoinstall" is chosen at the install prompt or if the installation system detects that it booted from the network, and isn't interrupted within 5 seconds, it attempts a fully-automatic installation. The installer runs dhclient(8) on the network interface the system booted from, or in case of multiple interfaces it will ask which one to use. Upon success, it retrieves a response file via HTTP. If that fails, the installer asks for the response file location, which can be either a URL or a local path, and retrieves the response file from there. The "next-server" DHCP option specifies the hostname part of the URL, as in "http:///install.conf". The "filename" DHCP parameter specifies the installer mode, e.g. "auto_install". On architectures where this parameter is used for netbooting, create a symbolic link named "auto_install" pointing to the boot program. The response file contains lines with key/value pairs separated by an equals sign "=", where the key is a non-ambiguous part (up to the question mark) of the installer question, consisting of whitespace separated words. The value is what would have been entered at the interactive prompt. Empty lines and lines beginning with a "#" character are ignored. The installer uses default answers in case of missing answers. Here is a response file example that uses a hashed password (see encrypt(1) for more details) for root and a public ssh key for the user that is created during the installation. System hostname = openbsd Password for root = $2a$14$Z4xRMg8vDpgYH...GVot3ySoj8yby Setup a user = puffy Password for user = ************* Public ssh key for user = ssh-ed25519 AAAAC3NzaC1...g3Aqre puffy@ai What timezone are you in = Europe/Stockholm Location of sets = http HTTP Server = ftp.eu.openbsd.org The "System hostname" key above matches the following full question asked during an interactive installation: System hostname? (short form, e.g. 'foo') While the installation is in progress the installer writes all output to the file /ai.log, which is available as mail on the freshly installed system after the initial reboot. If the installation is successful the system will reboot automatically; otherwise, you will be dropped back into the shell where you can look at the /ai.log file or try again. Upgrading a previously-installed OpenBSD System: ------------------------------------------------ Warning! Upgrades to OpenBSD 6.7 are currently only supported from the immediately previous release. The upgrade process will also work with older releases, but might not execute some migration tasks that would be necessary for a proper upgrade. The best solution, whenever possible, is to backup your data and reinstall from scratch. As a minimum, if the toolchain (the "comp" set) was installed, you should remove all files within /usr/include before attempting to upgrade. To upgrade OpenBSD 6.7 from a previous version, start with the general instructions in the section "Installing OpenBSD". Boot from CD-ROM, bsd.rd, the miniroot, or an installation floppy. When prompted, select the (U)pgrade option rather than the (I)nstall option at the prompt in the install process. You will be presented with a welcome message, and depending on how you are connected to the system, you will be asked to set the terminal type or to choose a keyboard layout. The upgrade script will ask you for the existing root partition, and will use the existing filesystems defined in /etc/fstab to install the new system in. It will also use your existing network parameters. From then, the upgrade procedure is very close to the installation procedure described earlier in this document. However, it is strongly advised that you unpack the etc.tgz and the xetc.tgz files found in /var/sysmerge in a temporary directory and merge changes by hand, or with the help of the sysmerge(8) helper script, since all components of your system may not function correctly until your files in "/etc" are updated. Getting source code for your OpenBSD System: -------------------------------------------- Now that your OpenBSD system is up and running, you probably want to get access to source code so that you can recompile pieces of the system. You can get the pieces over the internet using anonymous CVS, rsync, FTP or HTTP(s). For more information, see: https://www.OpenBSD.org/anoncvs.html https://www.OpenBSD.org/ftp.html Using online OpenBSD documentation: ----------------------------------- Documentation is available if you first install the manual pages distribution set. Traditionally, the UN*X "man pages" (documentation) are denoted by "name(section)". Some examples of this are intro(1), man(1), apropos(1), passwd(1), passwd(5) and afterboot(8). The section numbers group the topics into several categories, but three are of primary interest: user commands are in section 1, file formats are in section 5, and administrative information is in section 8. The "man" command is used to view the documentation on a topic, and is started by entering "man [section] topic". The brackets [] around the section should not be entered, but rather indicate that the section is optional. If you don't ask for a particular section, the topic with the least-numbered section name will be displayed. For instance, after logging in, enter man passwd to read the documentation for passwd(1). To view the documentation for passwd(5), enter man 5 passwd instead. If you are unsure of what man page you are looking for, enter apropos subject-word where "subject-word" is your topic of interest; a list of possibly related man pages will be displayed. Adding third party software - packages and ports: -------------------------------------------------------- As complete as your OpenBSD system is, you may want to add any of several excellent third party software applications. There are several ways to do this. You can: 1) Use the OpenBSD package collection to grab a pre-compiled and tested version of the application for your hardware. 2) Use the OpenBSD ports collection to automatically get any needed source file, apply any required patches, create the application, and install it for you. 3) Obtain the source code and build the application based upon whatever installation procedures are provided with the application. Instructions for installing applications from the various sources using the different installation methods follow. You should also refer to the packages(7) manual page. Installing applications from the ftp.OpenBSD.org package collection: All available packages for your architecture have been placed on ftp.OpenBSD.org in the directory pub/OpenBSD/6.7/packages/sparc64/ You may want to peruse this to see what packages are available. The packages are also on the OpenBSD mirror sites. See https://www.OpenBSD.org/ftp.html for a list of current 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 HTTP server. Example: $ su Password: # pkg_add \ http://ftp.OpenBSD.org/pub/OpenBSD/6.7/packages/sparc64/emacs-21.4p32.tgz Installing applications from the OpenBSD ports collection: See https://www.openbsd.org/faq/faq15.html#Ports for current instructions on obtaining and installing OpenBSD ports. You should also refer to the ports(7) manual page. Installing other applications: If an OpenBSD package or port does not exist for an application you're pretty much on your own. The first thing to do is ask if anyone is working on a port -- there may be one in progress. If no such port exists, you might want to look at the FreeBSD ports or NetBSD pkgsrc for inspiration. If you can't find an existing port, try to make your own and feed it back to OpenBSD. That's how our ports collection grows. Some details can be found in the OpenBSD Porter's Handbook at https://www.openbsd.org/faq/ports/ with more help coming from the mailing list, . Administrivia: -------------- There are various mailing lists available via the mailing list server at . To get help on using the mailing list server, send mail to that address with an empty body, and it will reply with instructions. More information about the various OpenBSD mailing list and proper netiquette is available at https://www.OpenBSD.org/mail.html To report bugs, use the "sendbug" command shipped with OpenBSD, and fill in as much information about the problem as you can. Good bug reports include lots of details. Additionally, bug reports can be sent by mail to: bugs@OpenBSD.org As a favor, please avoid mailing huge documents or files to the mailing lists. Instead, put the material you would have sent on a web server, then mail the appropriate list about it, or if you'd rather not do that, mail the list saying you'll send the data to those who want it. For more information about reporting bugs, see https://www.OpenBSD.org/report.html