1dnl $OpenBSD: install,v 1.43 2023/03/16 18:04:07 miod Exp $ 2OpenBSDInstallPrelude 3 4There are several ways to install OpenBSD onto a disk. The easiest way is 5to boot from the bootable CD-ROM mini image, then install from your favorite 6source. Network booting is supported through means of dhcpd(8) and tftpd(8). 7 8Booting from CD-ROM installation media: 9 10 At the SRM console prompt, enter 11 show device 12 to find the device ID of your CD-ROM drive (the device ID is 13 usually in the second column (``bootdev'') and should start 14 with DKA for a SCSI CD-ROM drive). If your drive shows up with 15 a drive number with trailing zeros, you will want to ignore them 16 (unless it is DKA0). For example, if your CD-ROM drive is listed 17 as DKA600, you want to use dka6 (device IDs are case 18 insensitive). 19 20 Insert the OpenBSD/MACHINE CD-ROM and enter 21 boot DEVICE 22 where DEVICE is the dka device name. 23 24 You should see info about the primary and secondary boot and then the 25 kernel should start to load. If the kernel fails to load or the 26 spinning cursor has stopped and nothing further has happened, you 27 either have a hardware problem or your MACHINE is not currently 28 supported by OpenBSD; try booting from the network instead if 29 possible. 30 31Booting from Network: 32 33 In order to bootstrap via the network, you must provide a second 34 system to act as a boot server. It is convenient if this is a second 35 OpenBSD machine as the necessary services are already installed, 36 although source code for such programs as dhcpd can be found in 37 OpenBSD's source tree, and should be reasonably portable to other 38 Unix-like operating systems. More information on diskless booting 39 can be found in the OpenBSD diskless(8) manual page. 40 41 Alpha systems can download their boot code over the network either 42 using the old DEC MOP protocol, or the common bootp protocol. 43 44 Older systems, such as the DEC 3000 systems, can only use the MOP 45 protocol. 46 47 Booting from a bootp or dhcp server: 48 49 You will need to set up dhcpd on the server, which can serve 50 bootp protocol requests. Start by editing the /etc/dhcpd.conf 51 on the bootserver, and declare an information block. Here is an 52 example: 53 54 subnet 10.0.0.0 netmask 255.0.0.0 { 55 host piper { 56 always-reply-rfc1048 "true"; 57 filename "netboot"; 58 option root-path "/alpha"; 59 hardware ethernet 08:00:2b:3d:28:2a; 60 fixed-address 10.42.42.42; 61 } 62 } 63 64 Do not forget to start dhcpd. 65 66 You will also need to start tftpd, for the system to download 67 the "netboot" file from the server in the /tftpboot directory. 68 69 Booting from a MOP server: 70 71 You will need to copy netboot.mop into 72 /tftpboot/mop/1a2b3c4d5e6f.SYS, where "1a2b3c4d5e6f" represents 73 the six octets of your Ethernet address, which can be obtained 74 with ``show dev'' at the SRM prompt. For example, the filename 75 for the machine in the dhcp example above would be 76 "08002b3d282a.SYS". Note that the MAC portion of the filename 77 must be lower case, but the "SYS" extension must be upper case. 78 79 Do not forget to start mopd. 80 81 Common netboot steps: 82 83 A few more services need to be enabled on the boot server. 84 85 First, add the Ethernet address to /etc/ethers file, as in: 86 87 08:00:2b:3d:28:2a piper 88 89 and start rarpd. 90 91 Second, you will need to export a directory for your new machine 92 to mount over NFS, in order to get its kernel. This is 93 accomplished by adding an entry to /etc/exports such as: 94 95 /alpha piper 96 97 The NFS server (which may be a different machine than the 98 MOP or dhcp server) will need to run nfsd, mountd, and the 99 rpc portmapper. See the exports(5) manpage for more 100 information. 101 102 Last, you will need to add an entry for your system in 103 /etc/bootparams, to point to the NFS server. For example: 104 105 piper root=myserver:/alpha 106 107 and start bootparamd. 108 109 Once loaded, the boot loader will mount /alpha over NFS and load 110 the kernel from there. 111 112Installing using the CD-ROM or Network procedure: 113 114OpenBSDInstallPart2 115 116 Boot your machine from the installation media as described above. 117 118 It will take a while to load the installation kernel, especially 119 from a slow network connection or a CD-ROM, most likely more than 120 a minute. 121 If some action doesn't eventually happen, or the spinning cursor 122 has stopped and nothing further has happened, either your boot 123 media is bad, your diskless setup is incorrect, or you may have 124 a hardware or configuration problem. 125 126OpenBSDInstallPart3 127 128OpenBSDInstallPart4 129 130OpenBSDInstallPart5 131 132OpenBSDInstallPart6({:-CD-ROM, -:}) 133 134OpenBSDURLInstall 135 136OpenBSDCDROMInstall 137 138OpenBSDDISKInstall({:-"wdN" or -:},{:-only -:}) 139 140OpenBSDCommonInstall 141 142OpenBSDInstallWrapup 143 144OpenBSDCongratulations 145 146 147 148OpenBSDUnattendedInstallation 149