INSTALLATION NOTES for OpenBSD/hp300 5.3 What is OpenBSD? ---------------- OpenBSD is a fully functional, multi-platform UN*X-like Operating System based on Berkeley Networking Release 2 (Net/2) and 4.4BSD-Lite. There are several operating systems in this family, but OpenBSD differentiates itself by putting security and correctness first. The OpenBSD team strives to achieve what is called a 'secure by default' status. This means that an OpenBSD user should feel safe that their newly installed machine will not be compromised. This 'secure by default' goal is achieved by taking a proactive stance on security. Since security flaws are essentially mistakes in design or implement- ation, the OpenBSD team puts as much importance on finding and fixing existing design flaws and implementation bugs as it does writing new code. This means that an OpenBSD system will not only be more secure, but it will be more stable. The source code for all critical system components has been checked for remote-access, local-access, denial- of-service, data destruction, and information-gathering problems. In addition to bug fixing, OpenBSD has integrated strong cryptography into the base system. A fully functional IPsec implementation is provided as well as support for common protocols such as SSL and SSH. Network filtering and monitoring tools such as packet filtering, NAT, and bridging are also standard, as well as several routing services, such as BGP and OSPF. For high performance demands, support for hardware cryptography has also been added to the base system. Because security is often seen as a tradeoff with usability, OpenBSD provides as many security options as possible to allow the user to enjoy secure computing without feeling burdened by it. Because OpenBSD is from Canada, the export of Cryptography pieces (such as OpenSSH, IPsec, and Kerberos) to the world is not restricted. (NOTE: OpenBSD can not be re-exported from the US once it has entered the US. Because of this, take care NOT to get the distribution from an FTP server in the US if you are outside of Canada and the US.) A comprehensive list of the improvements brought by the 5.3 release is available on the web at http://www.OpenBSD.org/53.html. OpenBSD 5.3 runs on the HP 9000/300 and 400 series of workstations, based on Motorola 68030 and 68040 processors. Sources of OpenBSD: ------------------- This is a list of currently known FTP and HTTP servers at the time of the 5.3 release. For a more recent list, please refer to http://www.OpenBSD.org/ftp.html Argentina: http://openbsd.org.ar/pub/OpenBSD (Buenos Aires) ftp://ftp.openbsd.org.ar/pub/OpenBSD (Buenos Aires) Australia: http://mirror.internode.on.net/pub/OpenBSD (Adelaide) ftp://mirror.internode.on.net/pub/OpenBSD (Adelaide) http://mirror.aarnet.edu.au/pub/OpenBSD (Brisbane) ftp://mirror.aarnet.edu.au/pub/OpenBSD (Brisbane) http://ftp.iinet.net.au/pub/OpenBSD (Perth) ftp://ftp.iinet.net.au/pub/OpenBSD (Perth) Austria: http://ftp5.eu.openbsd.org/ftp/pub/OpenBSD (Vienna) ftp://ftp5.eu.openbsd.org/pub/OpenBSD (Vienna) http://ftp2.eu.openbsd.org/pub/OpenBSD (Vienna) ftp://ftp2.eu.openbsd.org/pub/OpenBSD (Vienna) Belgium: http://ftp.belnet.be/pub/OpenBSD (Brussels) ftp://ftp.belnet.be/pub/OpenBSD (Brussels) Brazil: http://openbsd.locaweb.com.br/pub/OpenBSD (Sao Paulo) ftp://openbsd.locaweb.com.br/pub/OpenBSD (Sao Paulo) Bulgaria: http://mirror.telepoint.bg/OpenBSD (Sofia) Canada: http://ftp.OpenBSD.org/pub/OpenBSD (Alberta) ftp://ftp.OpenBSD.org/pub/OpenBSD (Alberta) Costa Rica: http://mirrors.ucr.ac.cr/OpenBSD ftp://mirrors.ucr.ac.cr/OpenBSD Denmark: http://ftp.openbsd.dk/pub/OpenBSD (Aalborg) ftp://ftp.openbsd.dk/pub/OpenBSD (Aalborg) Estonia: http://ftp.aso.ee/pub/OpenBSD (Tallinn) ftp://ftp.aso.ee/pub/OpenBSD (Tallinn) http://ftp.estpak.ee/pub/OpenBSD (Tallinn) ftp://ftp.estpak.ee/pub/OpenBSD (Tallinn) France: http://ftp.fr.openbsd.org/pub/OpenBSD (Paris) ftp://ftp.fr.openbsd.org/pub/OpenBSD (Paris) http://ftp2.fr.openbsd.org/pub/OpenBSD (Paris) ftp://ftp2.fr.openbsd.org/pub/OpenBSD (Paris) Germany: http://openbsd.cs.fau.de/pub/OpenBSD (Erlangen) ftp://openbsd.cs.fau.de/pub/OpenBSD (Erlangen) http://ftp.spline.de/pub/OpenBSD (Berlin) ftp://ftp.spline.de/pub/OpenBSD (Berlin) ftp://ftp-stud.fht-esslingen.de/pub/OpenBSD (Esslingen) http://ftp.bytemine.net/pub/OpenBSD (Oldenburg) ftp://ftp.bytemine.net/pub/OpenBSD (Oldenburg) http://ftp.halifax.rwth-aachen.de/openbsd (Aachen) ftp://ftp.halifax.rwth-aachen.de/pub/OpenBSD (Aachen) http://artfiles.org/openbsd (Hamburg) Greece: http://ftp.cc.uoc.gr/mirrors/OpenBSD (Heraklion) ftp://ftp.cc.uoc.gr/mirrors/OpenBSD (Heraklion) Hungary: http://ftp.fsn.hu/pub/OpenBSD (Budapest) ftp://ftp.fsn.hu/pub/OpenBSD (Budapest) Ireland: http://ftp.heanet.ie/pub/OpenBSD (Dublin) ftp://ftp.heanet.ie/pub/OpenBSD (Dublin) Japan: http://ftp.jaist.ac.jp/pub/OpenBSD (Ishikawa) ftp://ftp.jaist.ac.jp/pub/OpenBSD (Ishikawa) http://www.ftp.ne.jp/OpenBSD (Saitama) ftp://ftp.kddilabs.jp/OpenBSD (Saitama) The Netherlands: http://ftp.nluug.nl/pub/OpenBSD (Utrecht) ftp://ftp.nluug.nl/pub/OpenBSD (Utrecht) http://ftp.bit.nl/pub/OpenBSD (Ede) ftp://ftp.bit.nl/pub/OpenBSD (Ede) Norway: http://baksmell.netrunner.nu/pub/OpenBSD (Trondheim) ftp://baksmell.netrunner.nu/pub/OpenBSD (Trondheim) Pakistan: http://stingray.cyber.net.pk/pub/OpenBSD (Karachi) ftp://stingray.cyber.net.pk/OpenBSD (Karachi) Poland: http://ftp.icm.edu.pl/pub/OpenBSD (Warszawa) ftp://ftp.icm.edu.pl/pub/OpenBSD (Warszawa) Russia: http://mirror.corbina.net/pub/OpenBSD (Moscow) ftp://mirror.corbina.net/pub/OpenBSD (Moscow) http://mirror.yandex.ru/pub/OpenBSD (Moscow) ftp://mirror.yandex.ru/pub/OpenBSD (Moscow) Saudi Arabia: http://mirrors.isu.net.sa/pub/ftp.openbsd.org (Riyadh) ftp://mirrors.isu.net.sa/pub/ftp.openbsd.org (Riyadh) Slovenia: http://www.obsd.si/pub/OpenBSD (Ljubljana) ftp://ftp.obsd.si/pub/OpenBSD (Ljubljana) South Africa: http://mirror.is.co.za/mirror/ftp.openbsd.org (Johannesburg) ftp://ftp.is.co.za/mirror/ftp.openbsd.org (Johannesburg) Spain: http://mirror.cdmon.com/pub/OpenBSD (Barcelona) ftp://mirror.cdmon.com/pub/OpenBSD (Barcelona) Sweden: http://ftp.eu.openbsd.org/pub/OpenBSD (Stockholm) ftp://ftp.eu.openbsd.org/pub/OpenBSD (Stockholm) Switzerland: http://mirror.switch.ch/ftp/pub/OpenBSD (Zurich) ftp://mirror.switch.ch/pub/OpenBSD (Zurich) http://ftp.ch.openbsd.org/pub/OpenBSD (Zurich) ftp://ftp.ch.openbsd.org/pub/OpenBSD (Zurich) Turkey: ftp://ftp.ulak.net.tr/pub/OpenBSD United Kingdom: http://www.mirrorservice.org/pub/OpenBSD (Kent) ftp://ftp.mirrorservice.org/pub/OpenBSD (Kent) http://mirror.bytemark.co.uk/OpenBSD (Manchester) ftp://mirror.bytemark.co.uk/OpenBSD (Manchester) http://mirror.ox.ac.uk/pub/OpenBSD (Oxford) ftp://mirror.ox.ac.uk/pub/OpenBSD (Oxford) USA: http://ftp5.usa.openbsd.org/pub/OpenBSD (Redwood City, CA) ftp://ftp5.usa.openbsd.org/pub/OpenBSD (Redwood City, CA) http://ftp3.usa.openbsd.org/pub/OpenBSD (Boulder, CO) ftp://ftp3.usa.openbsd.org/pub/OpenBSD (Boulder, CO) http://mirror.team-cymru.org/pub/OpenBSD (Chicago, IL) ftp://mirror.team-cymru.org/pub/OpenBSD (Chicago, IL) http://mirror.planetunix.net/pub/OpenBSD (Chicago, IL) ftp://mirror.planetunix.net/pub/OpenBSD (Chicago, IL) http://filedump.se.rit.edu/pub/OpenBSD (Rochester, NY) ftp://filedump.se.rit.edu/pub/OpenBSD (Rochester, NY) http://openbsd.mirrors.hoobly.com (Pittsburgh, PA) http://mirror.ece.vt.edu/pub/OpenBSD (Blacksburg, VA) http://mirror.servihoo.net/pub/OpenBSD (Kansas City, MO) http://openbsd.mirrors.pair.com (Pittsburgh, PA) ftp://openbsd.mirrors.pair.com (Pittsburgh, PA) http://mirrors.gigenet.com/pub/OpenBSD (Arlington Heights, IL) ftp://mirrors.gigenet.com/pub/OpenBSD (Arlington Heights, IL) http://mirror.esc7.net/pub/OpenBSD (Dallas, TX) ftp://mirror.esc7.net/pub/OpenBSD (Dallas, TX) http://openbsd.mirrorcatalogs.com/pub/OpenBSD (Denver, CO) http://mirrors.nycbug.org/pub/OpenBSD (New York City, NY) ftp://mirrors.nycbug.org/pub/OpenBSD (New York City, NY) http://mirrors.syringanetworks.net/pub/OpenBSD (Boise, ID) ftp://mirrors.syringanetworks.net/pub/OpenBSD (Boise, ID) http://mirror.jmu.edu/pub/OpenBSD (Harrisonburg, VA) ftp://mirror.jmu.edu/pub/OpenBSD (Harrisonburg, VA) Additionally, the file ftp://ftp.OpenBSD.org/pub/OpenBSD/ftplist contains a list which is continually updated. If you wish to become a distribution site for OpenBSD, contact . OpenBSD 5.3 Release Contents: ----------------------------- The OpenBSD 5.3 release is organized in the following way. In the .../5.3 directory, for each of the architectures having an OpenBSD 5.3 binary distribution, there is a sub-directory. The hp300-specific portion of the OpenBSD 5.3 release is found in the "hp300" subdirectory of the distribution. That subdirectory is laid out as follows: .../5.3/hp300/ INSTALL.hp300 Installation notes; this file. SHA256 Output of the sum(1) program using the option -a sha256, usable for verification of the correctness of downloaded files. *.tgz hp300 binary distribution sets; see below. bsd A stock GENERIC hp300 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. SYS_UBOOT Unified boot file, used for booting from disk or from the network. SYS_CDBOOT Simplified boot file, used for booting from CD-ROM. The OpenBSD/hp300 binary distribution sets contain the binaries which comprise the OpenBSD 5.3 release for hp300 systems. There are ten binary distribution sets. The binary distribution sets can be found in the "hp300" subdirectory of the OpenBSD 5.3 distribution tree, and are as follows: base53 The OpenBSD/hp300 5.3 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. [ 49.6 MB gzipped, 158.5 MB uncompressed ] comp53 The OpenBSD/hp300 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. [ 67.4 MB gzipped, 194.1 MB uncompressed ] etc53 This distribution set contains the system configuration files that reside in /etc and in several other places. This set MUST be installed if you are installing the system from scratch, but should NOT be used if you are upgrading. (If you are upgrading, it's recommended that you get a copy of this set and CAREFULLY upgrade your configuration files by hand; see the section named Upgrading a previously-installed OpenBSD System" below.) [ 511.8 KB gzipped, 1.5 MB uncompressed ] game53 This set includes the games and their manual pages. [ 2.4 MB gzipped, 5.5 MB uncompressed ] man53 This set includes all of the manual pages for the binaries and other software contained in the base set. Note that it does not include any of the manual pages that are included in the other sets. [ 9.1 MB gzipped, 35.0 MB uncompressed ] xbase53 This set includes the base X distribution. This includes programs, headers and libraries. [ 12.1 MB gzipped, 38.7 MB uncompressed ] xetc53 This set includes the X window system configuration files that reside in /etc. It's the equivalent of etc53 for X. [ 70.3 KB gzipped, 276.9 KB uncompressed ] xfont53 This set includes all of the X fonts. [ 37.5 MB gzipped, 48.5 MB uncompressed ] xserv53 This set includes all of the X servers. [ 2.7 MB gzipped, 8.2 MB uncompressed ] xshare53 This set includes all text files equivalent between all architectures. [ 3.2 MB gzipped, 17.6 MB uncompressed ] OpenBSD System Requirements and Supported Devices: -------------------------------------------------- OpenBSD/hp300 5.3 will run on most HP 9000/300- and 400-series machines. 12MB of RAM should be sufficient to boot and a minimal system can probably be squeezed onto a 250MB disk by installing only the `base' and `etc' sets. However, a minimum of 16MB is necessary for the system not to be swap-bound, with 32MB or more being recommended for serious usage of the system. The following HP hardware is supported: HP 9000/300 series 68030-based: 340, 345, 360, 362, 370 and 375. 68040-based: 380, 382 and 385. HP 9000/400 series 68030-based: 400(dl/s/t). 68040-based: 425(dl/e/s/t) and 433(dl/s/t). These machines are not supported when configured for Domain/OS; their ROMs need to be configured in `HP-UX mode'. SCSI controllers and peripherals 98658A built-in and add-on SCSI interface (spc). SCSI-1 disk drives (sd), cdrom drives (cd), tape drives (st) and tape changers (ch). SCSI-2 devices are known to work, but may require changing a jumper to restrict them to SCSI-1 behaviour. HP-IB/CS80 controller and peripherals 98624 built-in HP-IB interface (nhpib). 98625A and 98625B `fast' HP-IB interface (fhpib). Most HP disks, including: 7912, 7914, 7933, 7936, 7937, 7945, 7957, 7958, 7959, 2200, and 2203. Low-density cartridge drives: 7914, 7946, and 9144. High-density cartridge drives: 9145. 1/2" tape drives: 7974A, 7978A/B, 7979A, 7980A, and 7980XC. Serial ports 98644 built-in and add-on single port (dca). 98642 4-port (dcm). 98638 8-port (dcm). 400-series Apollo 3-port serial/keyboard mux (apci). [The first port being typically configured as a dca device, except on the 425e.] Ethernet interfaces 98643 built-in and add-on LAN cards (le). Frame buffers 98543, 98544, 98545 and 98547 color and monochrome Topcat (topcat). 98548, 98549 and 98550 color and monochrome Catseye (topcat). A1416A color Kathmandu (topcat). 98700 and 98710 Gatorbox (gbox). 98720 and 98721 Renaissance (rbox). 98730 and 98731 DaVinci (dvbox). A1096A monochrome Hyperion (hyper). 98705 ``Tigershark'' PersonalVRX (tvrx). VRX (362/382 on-board), EVRX (425e on-board) and other SGC frame buffers (sti). Input devices General interface supporting all HIL devices (hil): keyboard (hilkbd) 2 and 3 button mice(hilms) ID module (hilid) [Serial mice connected to a `HIL to quad' converter are also known to work] Apollo domain keyboards and mice (on 400 series) (dnkbd). Miscellaneous Digital audio on model 425e (arcofi) Battery-backed real-time clock (except on 425e). Printers and plotters on RS232 and HP-IB (ppi). Unsupported hardware mainly consists of: 68010 and 68020 based systems: 310, 318, 319, 320, 330 and 350. 68030 FPU-less systems: 332. parallel port on the 3x2 and 4xx models. 98765 TurboVRX, X-Genesis and Y-Genesis frame buffers. ISA slot on 4xx ``t'' models. EISA slots on 4xx ``s'' models. Getting the OpenBSD System onto Useful Media: --------------------------------------------- Installation is supported from several media types, including: CD-ROM FFS partitions Tape Remote NFS partition FTP HTTP The steps necessary to prepare the distribution sets for installation depend on which method of installation you choose. Some methods require a bit of setup first that is explained below. The installation allows installing OpenBSD directly from FTP mirror sites over the internet, however you must consider the speed and reliability of your internet connection for this option. It may save much time and frustration to use ftp get/reget to transfer the distribution sets to a local server or disk and perform the installation from there, rather than directly from the internet. The variety of options listed may seem confusing, but situations vary widely in terms of what peripherals and what sort of network arrangements a user has, the intent is to provide some way that will be practical. Creating an installation tape: While you won't be able to boot OpenBSD from a tape, you can use one to provide the installation sets. To do so, you need to make a tape that contains the distribution set files, each in "tar" format or in "gzipped tar format". First you will need to transfer the distribution sets to your local system, using ftp or by mounting the CD-ROM containing the release. Then you need to make a tape containing the files. If you're making the tape on a UN*X-like system, the easiest way to do so is make a shell script along the following lines, call it "/tmp/maketape". #! /bin/sh TAPE=${TAPE:-/dev/nrst0} mt -f ${TAPE} rewind for file in base etc comp game man xbase xetc xfont xserv xshare do dd if=${file}53.tgz of=${TAPE} obs=8k conv=osync done tar cf ${TAPE} bsd mt -f ${TAPE} offline # end of script And then: cd .../5.3/hp300 sh -x /tmp/maketape If you're using a system other than OpenBSD or SunOS, the tape name and other requirements may change. You can override the default device name (/dev/nrst0) with the TAPE environment variable. For example, under Solaris, you would probably run: TAPE=/dev/rmt/0n sh -x /tmp/maketape Note that, when installing, the tape can be write-protected (i.e. read-only). To install OpenBSD using a remote partition, mounted via NFS, you must do the following: NOTE: This method of installation is recommended only for those already familiar with using BSD network configuration and management commands. If you aren't, this documentation should help, but is not intended to be all-encompassing. Place the OpenBSD distribution sets you wish to install into a directory on an NFS server, and make that directory mountable by the machine on which you are installing or upgrading OpenBSD. This will probably require modifying the /etc/exports file of the NFS server and resetting its mount daemon (mountd). (Both of these actions will probably require superuser privileges on the server.) You need to know the numeric IP address of the NFS server, and, if the server is not on a network directly connected to the machine on which you're installing or upgrading OpenBSD, you need to know the numeric IP address of the router closest to the OpenBSD machine. Finally, you need to know the numeric IP address of the OpenBSD machine itself. Once the NFS server is set up properly and you have the information mentioned above, you can proceed to the next step in the installation or upgrade process. If you are upgrading OpenBSD, you also have the option of installing OpenBSD by putting the new distribution sets somewhere in your existing file system, and using them from there. To do that, do the following: Place the distribution sets you wish to upgrade somewhere in your current file system tree. At a bare minimum, you must upgrade the "base" binary distribution, and so must put the "base53" set somewhere in your file system. It is recommended that you upgrade the other sets, as well. Preparing your System for OpenBSD Installation: ----------------------------------------------- Most hp300 machines don't generally need any specific preparation. On series 400, you will wish to configure the PROM as ``HP-UX compatible'' before installing OpenBSD. To do so, at the PROM prompt, enter ``CF'', then ``2'' (Boot Mode Selection), then ``2'' (HP-UX Compatible). Choose to make this setting Permanent with ``P'', then validate your changes with ``E''. Your machine will restart in HP-UX mode. If you plan to use a serial console, you might have to flip a switch on series 300, or configure the RS-232 interface as ``remote'' from the Configuration menu, on series 400, except on the 425e where serial console is selected by setting the ``service/normal'' switch in the ``service'' position. Please refer to the OpenBSD/hp300 FAQ at http://www.OpenBSD.org/hp300/hp300faq.html for more information about this process. Installing the OpenBSD System: ------------------------------ Installing OpenBSD is a relatively complex process, but if you have this document in hand and are careful to read and remember the information which is presented to you by the install program, it shouldn't be too much trouble. If the disks connected to your machine are HP-IB disks, it is recommended that you know their geometry, i.e. the sector size (note that sector sizes other than 512 bytes are not currently supported), the number of sectors per track, the number of tracks per cylinder (also known as the number of heads), and the number of cylinders on the disk. The OpenBSD kernel will try to discover these parameters on its own, and if it can it will print them at boot time. If possible, you should use the parameters it prints. (You might not be able to because you're sharing your disk with another operating system, or because your disk is old enough that the kernel can't figure out its geometry.) The ramdisk kernel may be loaded from the network, from CD-ROM, or other SCSI devices (such as Zip(tm) disk). Note that loading from HP-IB or SCSI cartridge tape is possible, but not currently supported. Booting from CD-ROM installation media: You can burn a bootable CD-ROM and boot from it. To boot from SCSI CD-ROM, simply insert the CD into the drive before power up, then during the computer's self-test cycle, press the space bar. Shortly, you should see a menu of possible boot options appear. Select the option corresponding to SYS_CDBOOT. SYS_CDBOOT will then load and begin loading bsd.rd from the CD-ROM; depending on your ROM revision and hardware configuration, you may or may not see any messages on the console while this happens. Please note that booting from CD-ROM may not be supported by all models of hp300. You will also need a CD-ROM drive which uses 512-byte blocks; anything which shipped with an hp300 or is known to boot a SPARC or black NeXTStation should work. Modern CD-ROM drives jumpered to use 512-byte blocks should work as well. Booting from Network: If you wish to load the SYS_UBOOT program via the network, you need to either have another OpenBSD system on the network, or something else capable of running the rbootd(8) program. Source code may be found under usr.sbin/rbootd in the OpenBSD source tree, but requires the Berkeley Packet Filter (bpf) in order to function. It may be possible to use HP-UX, but it is not recommended (or documented here). For more information on diskless booting under OpenBSD, see the diskless(8) manual page. First of all, configure your rbootd to handle boot requests from the client. NOTE: OpenBSD's `rbootd' is slightly different from HP-UX's. To configure OpenBSD's `rbootd', create a file called `/etc/rbootd.conf' and place in it an entry like the following: 08:00:09:04:AA:33 SYS_UBOOT # thunder-egg The first column is the Ethernet address of the client's network interface. The second column is the program to send to the client, and anything after the `#' is a comment. Once you have rbootd running, copy the SYS_UBOOT program to the /usr/mdec/rbootd directory on your server. If this directory doesn't exist already, you will need to create it. Next, add the client to /etc/ethers on your server. For example: 08:00:09:04:AA:33 thunder-egg Then start `rarpd' on your server; `rarpd -a' should do the trick. Finally, you need to add an entry in /etc/bootparams. For example: thunder-egg root=myserver:/export/hp300 Where myserver is the name of your server machine and `/export/hp300' is the directory that holds the ramdisk kernel image (`bsd.rd'). Now run `rpc.bootparamd' and make sure that this directory is NFS exported to the client. See the manual pages on your server system if you need more information about exporting filesystems. If you run into problems you may wish to run `rpc.bootparamd' with the `-d' flag on your server to get extra debugging information. You are now ready to load SYS_UBOOT. During the client's self-test cycle, press the space bar. Shortly after, you should see a menu of possible boot options appear. Select the option corresponding to SYS_UBOOT. SYS_UBOOT will then load and prompt you for a kernel name. NFS file names should not have a leading '/' prepended to them; simply use `bsd.rd'. Installing using the CD-ROM 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 many information about your system setup as possible at the beginning, so that no human interaction is required as soon as the questions are over. The order of these questions might be quite disconcerting if you are used to other installation procedures, including older OpenBSD versions. If any question has a default answer, it will be displayed in brackets ("[]") after the question. If you wish to stop the installation, you may hit Control-C at any time, but if you do, you'll have to begin the installation process again from scratch. Using Control-Z to suspend the process may be a better option, or at any prompt enter `!' to get a shell, from which 'exit' will return you back to that prompt (no refresh of the prompt will occur, though). Boot your machine from the installation media as described above. When presented with the boot prompt, enter the path of your kernel (which is likely to be `bsd.rd'). It will take a while to load the kernel especially from a slow speed CD-ROM 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 is incorrect, or you may have a hardware or configuration problem. Once the kernel has loaded, you will be presented with the OpenBSD kernel boot messages. You will want to read them to determine your disks name and geometry. Its name will be something like "sd0" for SCSI drives, or "hd0" for HP-IB drives. As mentioned above, you will need your disks geometry (which will be printed on a line beginning with its name) when creating OpenBSD partitions. You will also need to know the device name to tell the install tools what disk to install on. If you cannot read the messages as they scroll by, do not worry -- you can get at this information later inside the install program. After the kernel is done initialization, you will be asked whether you wish to do an "(I)nstall" or an "(U)pgrade". Enter 'I' for a fresh install or 'U' to upgrade an existing installation. If you are connected with a serial console, you will next be asked for your terminal type. You should choose the terminal type from amongst those listed. (If your terminal type is xterm, just use vt220). If you are connected using a glass console, you will next be asked for your keyboard layout (the default being the US QWERTY layout). Depending on your keyboard type, not all international layouts may be supported; answering `?' (which, on QWERTY layouts, is the key to the left of the right `shift' key, shifted) will display a list of supported layouts. (If you do not need to change the keyboard layout, just press enter.) The first question you will be asked is the system hostname. Reply with the name of the system, without any domain part. You will now be given an opportunity to configure the network. The network configuration you enter (if any) can then be used to do the install from another system using HTTP or FTP, and will also be the configuration used by the system after the installation is complete. The install program will give you a list of network interfaces you can configure. For each network interface you select to configure, you will be asked for: - the symbolic host name to use (except for the first interface setup, which will reuse the host name entered at the beginning of the installation). - the IPv4 settings: address and netmask. If the IP address should be obtained from a DHCP server, simply enter ``dhcp'' when asked for the address. - the IPv6 settings (address, prefix length, and default router). You may enter ``rtsol'' when asked for the address for the interface to configure automatically via router solicitation messages. After all interfaces have been configured, if there have been any IPv4 interfaces setup, you will be asked for the IPv4 default route. This step is skipped if you only have one IPv4 interface setup, and it is configured with DHCP. The install program will also ask you for your DNS domain name, and the domain name servers, unless this information has already been obtained from a DHCP server during interface setup. You will also be presented with an opportunity to do more manual configuration. If you accept, you will be dropped to a shell; when you are done, enter `exit' to return to the installation program. You will then be asked to enter the initial root password of the system, twice. Although the install program will only check that the two passwords match, you should make sure to use a strong password. As a minimum, the password should be at least eight characters long and a mixture of both lower and uppercase letters, numbers and punctuation characters. You will then be asked whether you want to start sshd(8) by default, as well as ntpd(8). If you choose to start ntpd(8), you will be asked for your ntp server; if you don't have any preferred ntp server, press enter to confirm the default setting of using the pool.ntp.org servers. You will now be given the possibility to setup a user account on the forthcoming system. This user will be added to the `wheel' group. Enter the desired login name, or `n' if you do not want to add a user account at this point. Valid login names are sequences of digits and lowercase letters, and must start with a lowercase letter. If the login name matches this criteria, and doesn't conflict with any of the administrative user accounts (such as `root', `daemon' or `ftp'), you will be prompted with the users descriptive name, as well as its password, twice. As for the root password earlier, the install program will only check that the two passwords match, but you should make sure to use a strong password here as well. If you have chosen to setup a user account, and you had chosen to start sshd(8) on boot, you will be given the possibility to disable sshd(8) logins as root. The installation program will now tell you which disks it can install on, and ask you which it should use. Reply with the name of your root disk. You will the be asked if you want to use DUID notation in /etc/fstab, instead of traditional device names. You are strongly advised to use DUIDs, as they allow you to move your disks to different controllers, or change their bus identifiers, without having to modify /etc/fstab every time your configuration changes. Next the disk label which defines the layout of the OpenBSD partitions must be set up. Each file system you want will require a separate partition. You will be proposed a default partition layout, trying to set up separate partitions, disk size permitting. You will be given the possibility to either accept the proposed layout, or edit it, or create your own custom layout. These last two choices will invoke the disklabel(8) interactive editor, allowing you to create your desired layout. Within the editor, you will probably start out with only the 'c' partition of fstype 'unused' that represents the whole disk. This partition can not be modified. You must create partition 'a' as a native OpenBSD partition, i.e. one with "4.2BSD" as the fstype, to hold the root file system. In addition to partition 'a' you should create partition 'b' with fstype "swap", and native OpenBSD partitions to hold separate file systems such as /usr, /tmp, /var, and /home. You will need to provide a mount point for all partitions you define. Partitions without mount points, or not of 4.2BSD fstype, will neither be formatted nor mounted during the installation. For quick help while in the interactive editor, enter '?'. The `z' command (which deletes all partitions and starts with a clean label), the `A' command (which performs the automatic partition layout) and the `n' command (to change mount points) are of particular interest. Although the partitions position and size are written in exact sector values, you do not need a calculator to create your partitions! Human-friendly units can be specified by adding `k', `m' or `g' after any numbers to have them converted to kilobytes, megabytes or gigabytes. Or you may specify a percentage of the disk size using `%' as the suffix. Enter 'M' to view the entire manual page (see the info on the ``-E'' flag). To exit the editor enter 'q'. Since the target disk will become the boot disk for your new OpenBSD/hp300 installation, the disklabel program will restrict the available disk area to keep the first cylinder, which will contain the bootblock, safe from being overwritten. If you don't plan to install a bootblock on this disk, you can reclaim this space with the 'b' command. After the layout has been saved, new filesystems will be created on all partitions with mount points. This will DESTROY ALL EXISTING DATA on those partitions. After configuring your root disk, the installer will return to the list of available disks to configure. You can choose the other disks to use with OpenBSD in any order, and will get to setup their layout similarly to the root disk above. However, for non-root disks, you will not be proposed a default partition layout. When all your disks are configured, simply hit return at the disk prompt. After these preparatory steps have been completed, you will be able to extract the distribution sets onto your system. There are several install methods supported: FTP, HTTP, CD-ROM, tape, NFS, or a local disk partition. To install via FTP or HTTP: To begin an FTP or HTTP install you will need the following pieces of information: 1) Proxy server URL if you are using a URL-based FTP or HTTP proxy (squid, CERN FTP, Apache 1.2 or higher). You need to define a proxy if you are behind a firewall that blocks outgoing FTP or HTTP connections (assuming you have a proxy available to use). 2) The IP address (or hostname if you configured DNS servers earlier in the install) of an FTP or HTTP server carrying the OpenBSD 5.3 distribution. The installation program will try to fetch a list of such servers; depending on your network settings, this might fail. If the list could be fetched, it will be displayed, and you can choose an entry from the list (the first entries are expected to be the closest mirrors to your location). 3) The directory holding the distribution sets. The default value of pub/OpenBSD/5.3/hp300 is almost always correct on FTP servers; for HTTP servers there is no standard location for this. 4) For FTP installs only, the login and password for the FTP account. You will only be asked for a password for non-anonymous FTP. Then refer to the section named "installation set selection" below. To install from CD-ROM: When installing from a CD-ROM, you will be asked which device holds the distribution sets. This will typically be "cd0". If there is more than one partition on the CD-ROM, you will be asked which partition the distribution is to be loaded from. This is normally partition "a". You will also have to provide the relative path to the directory on the CD-ROM which holds the distribution, for the hp300 this is "5.3/hp300". Then refer to the section named "installation set selection" below. To install from an NFS mounted directory: When installing from an NFS-mounted directory, you must have completed network configuration above, and also set up the exported file system on the NFS server in advance. First you must identify the IP address of the NFS server to load the distribution from, and the file system the server expects you to mount. The install program will also ask whether or not TCP should be used for transport (the default is UDP). Note that TCP only works with newer NFS servers. You will also have to provide the relative path to the directory on the file system where the distribution sets are located. Note that this path should not be prefixed with a '/'. Then refer to the section named "installation set selection" below. To install from a local disk partition: When installing from a local disk partition, you will first have to identify which disk holds the distribution sets. This is normally "hdN" 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 name, or wildcards (e.g. `*.tgz' or `base*|comp*', or `all' to select all the sets (which is what most users will want to do). You may also enter `abort' to deselect everything and restart the selection from scratch, or unselect sets by entering their name prefixed with `-' (e.g. `-x*'). It is also possible to enter an arbitrary filename and have it treated as a file set. When you are done selecting distribution sets, enter `done'. The files will begin to extract. To install from tape: Unlike all other installation methods, there is no way to know the names of the files on tape. Because of this, it is impossible to check that the files on tape match the machine architecture and release of OpenBSD/hp300. Moreover, since tape filenames are not known, the file checksums can not be verified. Use this installation method only if there is no better option. In order to install from tape, the distribution sets to be installed must have been written to tape previously, either in tar format or gzip-compressed tar format. You will also have to identify the tape device where the distribution sets are to be extracted from. This will typically be "nrst0" (no-rewind, raw interface). Next you will have to specify how many files have to be skipped on the tape. This number is usually zero. The install program will not automatically detect whether an image has been compressed, so it will ask for that information before starting the extraction of each file. After the files have been extracted, you will be given the choice to select a new location from which to install distribution sets. If there have been errors extracting the sets from the previous location, or if some sets have been missing, this allows you to select a better source. Also, if the installation program complains that the distribution sets you have been using do not match their recorded checksums, you might want to check your installation source (although this can happen between releases, if a snapshot is being updated on an FTP or HTTP server with newer files while you are installing). The last thing you'll need to configure is the time zone your system will be using. For this to work properly, it is expected that you have installed at least the "base53", "etc53", 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. Finally, you will be asked whether you would like to install non-free firmware files (which can't be tightly integrated to the OpenBSD system) on first boot, by invoking fw_update(8) on the next boot. Congratulations, you have successfully installed OpenBSD 5.3. When you reboot into OpenBSD, you should log in as "root" at the login prompt. You should create yourself an account and protect it and the "root" account with good passwords. The install program leaves root an initial mail message. We recommend you read it, as it contains answers to basic questions you might have about OpenBSD, such as configuring your system, installing packages, getting more information about OpenBSD, sending in your dmesg output and more. To do this, run mail and then just enter "more 1" to get the first message. You quit mail by entering "q". Some of the files in the OpenBSD 5.3 distribution might need to be tailored for your site. We recommend you run: man afterboot which will tell you about a bunch of the files needing to be reviewed. If you are unfamiliar with UN*X-like system administration, it's recommended that you buy a book that discusses it. Upgrading a previously-installed OpenBSD System: ------------------------------------------------ Warning! Upgrades to OpenBSD 5.3 are currently only supported from the immediately previous release. The upgrade process will also work with older releases, but might not execute some migration tasks that would be necessary for a proper upgrade. The best solution, whenever possible, is to backup your data and reinstall from scratch. As a minimum, if the toolchain (the ``comp'' set) was installed, you should remove all files within /usr/include before attempting to upgrade. To upgrade OpenBSD 5.3 from a previous version, start with the general instructions in the section "Installing OpenBSD". IMPORTANT NOTE: if you intend to boot from bsd.rd, it is very likely that your boot blocks do not support ELF kernels. Before attempting to boot bsd.rd, upgrade the boot blocks by copying the provided ``SYS_UBOOT'' file to /usr/mdec/sdboot (or /usr/mdec/hdboot if your boot disk is an HP-IB disk), and run, as root: /sbin/disklabel -B sd0 (replacing `sd0' with the name of your boot disk). You will then be able to boot bsd.rd. Boot from bsd.rd. When prompted, select the (U)pgrade option rather than the (I)nstall option at the prompt in the install process. You will be presented with a welcome message and asked if you really wish to upgrade. The upgrade script will ask you for the existing root partition, and will use the existing filesystems defined in /etc/fstab to install the new system in. It will also use your existing network parameters. From then, the upgrade procedure is very close to the installation procedure described earlier in this document. Note that the upgrade procedure will not let you pick neither the ``etc53.tgz'' nor the ``xetc53.tgz'' sets, so as to preserve your files in `/etc' which you are likely to have customized since a previous installation. However, it is strongly advised that you unpack the etc53.tgz and xetc53.tgz sets in a temporary directory and merge changes by hand, or with the help of the sysmerge(8) helper script, since all components of your system may not function correctly until your files in `/etc' are updated. Getting source code for your OpenBSD System: -------------------------------------------- Now that your OpenBSD system is up and running, you probably want to get access to source code so that you can recompile pieces of the system. A few methods are provided. If you have an OpenBSD CD-ROM, the source code is provided. Otherwise, you can get the pieces over the Internet using anonymous CVS, CVSync or FTP. For more information, see http://www.OpenBSD.org/anoncvs.html http://www.OpenBSD.org/cvsync.html http://www.OpenBSD.org/ftp.html Using online OpenBSD documentation: ----------------------------------- Documentation is available if you first install the manual pages distribution set. Traditionally, the UN*X "man pages" (documentation) are denoted by 'name(section)'. Some examples of this are intro(1), man(1), apropos(1), passwd(1), passwd(5) and afterboot(8). The section numbers group the topics into several categories, but three are of primary interest: user commands are in section 1, file formats are in section 5, and administrative information is in section 8. The 'man' command is used to view the documentation on a topic, and is started by entering 'man [section] topic'. The brackets [] around the section should not be entered, but rather indicate that the section is optional. If you don't ask for a particular section, the topic with the least-numbered section name will be displayed. For instance, after logging in, enter man passwd to read the documentation for passwd(1). To view the documentation for passwd(5), enter man 5 passwd instead. If you are unsure of what man page you are looking for, enter apropos subject-word where "subject-word" is your topic of interest; a list of possibly related man pages will be displayed. Adding third party software; ``packages'' and ``ports'': -------------------------------------------------------- As complete as your OpenBSD system is, you may want to add any of several excellent third party software applications. There are several ways to do this. You can: 1) Use the OpenBSD ``package'' collection to grab a pre-compiled and tested version of the application for your hardware. 2) Use the OpenBSD ``ports'' collection to automatically get any needed source file, apply any required patches, create the application, and install it for you. 3) Obtain the source code and build the application based upon whatever installation procedures are provided with the application. If you purchased the OpenBSD CD-ROM set you already have several popular ``packages'', and the ``ports'' collection. Instructions for installing applications from the various sources using the different installation methods follow. You should also refer to the packages(7) manual page. Installing applications from the CD-ROM package collection: The OpenBSD CD-ROM ships with several applications pre-built for various hardware architectures. The number of applications vary according to available disk space. Check the directory 5.3/packages/m68k to see which packages are available for your hardware architecture. That directory will be on the same CD-ROM containing the OS installation files for your architecture. To install one or more of these packages you must: 1) become the superuser (root). 2) mount the appropriate CD-ROM. 3) use the ``pkg_add'' command to install the software. Example (in which we use su(1) to get superuser privileges, thus you have to be in group "wheel", see the manual page for su(1)). $ su Password: # mkdir -p /cdrom # mount /dev/cd0a /cdrom # pkg_add /cdrom/5.3/packages/m68k/ # # umount /cdrom Package names are usually the application name and version with .tgz appended, e.g. emacs-21.3.tgz Installing applications from the ftp.OpenBSD.org package collection: All available packages for your architecture have been placed on ftp.OpenBSD.org in the directory pub/OpenBSD/5.3/packages/m68k/ You may want to peruse this to see what packages are available. The packages are also on the OpenBSD FTP mirror sites. See http://www.OpenBSD.org/ftp.html for a list of current FTP mirror sites. Installation of a package is very easy. 1) become the superuser (root) 2) use the ``pkg_add'' command to install the software ``pkg_add'' is smart enough to know how to download the software from the OpenBSD FTP server. Example: $ su Password: # pkg_add \ ftp://ftp.OpenBSD.org/pub/OpenBSD/5.3/packages/m68k/emacs-21.3.tgz Installing applications from the CD-ROM ports collection: The CD-ROM ``ports'' collection is a set of Makefiles, patches, and other files used to control the building and installation of an application from source files. Creating an application from sources can require a lot of disk space, sometimes 50 megabytes or more. The first step is to determine which of your disks has enough room. Once you've made this determination, read the file PORTS located on the CD-ROM which contains the ports tree. To build an application you must: 1) become the superuser (root) 2) have network access, or obtain the actual source files by some other means. 3) cd to the ports directory containing the port you wish to build. To build samba, for example, where you'd previously copied the ports files into the /usr/ports directory: cd /usr/ports/net/samba 4) make 5) make install 6) make clean Installing applications from the OpenBSD ports collection: See http://www.OpenBSD.org/faq/ports/ports.html for current instructions on obtaining and installing OpenBSD ports. You should also refer to the ports(7) manual page. Installing other applications: If an OpenBSD package or port does not exist for an application you're pretty much on your own. The first thing to do is ask if anyone is working on a port -- there may be one in progress. If no such port exists, you might want to look at the FreeBSD ports or NetBSD pkgsrc for inspiration. If you can't find an existing port, try to make your own and feed it back to OpenBSD. That's how our ports collection grows. Some details can be found in the OpenBSD Porter's Handbook at http://www.openbsd.org/faq/ports/ with more help coming from the mailing list, . Administrivia: -------------- There are various mailing lists available via the mailing list server at . To get help on using the mailing list server, send mail to that address with an empty body, and it will reply with instructions. There are also two OpenBSD Usenet newsgroups, comp.unix.bsd.openbsd.announce for important announcements and comp.unix.bsd.openbsd.misc for general OpenBSD discussion. More information about the various OpenBSD mailing list and proper netiquette is available at http://www.OpenBSD.org/mail.html To report bugs, use the 'sendbug' command shipped with OpenBSD, and fill in as much information about the problem as you can. Good bug reports include lots of details. Additionally, bug reports can be sent by mail to: bugs@OpenBSD.org As a favor, please avoid mailing huge documents or files to the mailing lists. Instead, put the material you would have sent up for FTP somewhere, then mail the appropriate list about it, or, if you'd rather not do that, mail the list saying you'll send the data to those who want it. For more information about reporting bugs, see http://www.OpenBSD.org/report.html