1dnl $OpenBSD: install,v 1.23 2013/02/25 20:34:07 miod Exp $ 2dnl lots of texts coming from {mvme68k,vax}/install initially 3OpenBSDInstallPrelude 4 5Bootstrapping the installation ramdisk kernel is supported 6from either network, tape or CD-ROM. 7 8 9Booting from Tape or CD-ROM installation media: 10 11 You can burn a bootable CD-ROM and boot from it or you can prepare an 12 installation tape as described in the "Creating an installation tape" 13 section earlier. 14 To boot from SCSI CD-ROM, simply insert the CD into the drive before power 15 up, then during the computer's self-test cycle, press the space bar. 16 Subsequently at the PROM prompt issue a command: 17 18 BOOT_ADMIN> search 19 20 to initiate a search for all bootable devices available. This procedure 21 may take a few minutes and should you have configured network boot services 22 present may find those too. A sample output might be: 23 24 Path Number Device Path Device Type 25 ----------- ----------------- ----------- 26 P0 SESCSI.2.0 TOSHIBA CD-ROM XM-6201TA 27 P1 LAN.10.0.0.5.3.254 boron 28 P2 FWSCSI.5.0 IBM DDRS-34560WS 29 P3 FWSCSI.0.0 SEAGATE ST318436LW 30 P4 SESCSI.6.0 HP HP35480A 31 32 To boot from your CD-ROM type: 33 34 BOOT_ADMIN> boot p0 35 36 To boot from your tape type: 37 38 BOOT_ADMIN> boot p4 39 40 41Booting from Network: 42 43 In order to bootstrap via the network, you must provide a second system to 44 act as a boot server. It is convenient if this is a second OpenBSD machine 45 as the necessary services are already installed, although source code for 46 such programs as dhcpd can be found in OpenBSD's source tree, and should be 47 reasonably portable to other UN*X-like operating systems. More information 48 on diskless booting can be found in the OpenBSD diskless(8) manual page. 49 50 Your MACHINE expects to be able to download a so-called LIF (``Logical 51 Interchange Format'') image, containing both the boot code and the kernel, 52 via the HP rboot protocol, for older firmware, or via the bootp protocol, 53 for more recent firmware. 54 55 Old firmware operation 56 57 Most of the 7xx models (except the 712, the second generation of 715, i.e. 58 715/64/80/100/100XC, and the 74x) have an older version of PDC. There are 59 two levels of interactive commands in this version. 60 The first level is a short menu: 61 62 b) Boot from specified device 63 s) Search for bootable device 64 a) Enter Boot Administration mode 65 x) Exit and continue boot sequence 66 67 Select from menu: 68 69 In this case, you will need to setup rbootd on the server. Start by 70 creating an /etc/rbootd.conf file on the bootserver. The format of this 71 file is the ethernet address followed by the LIF filename. Here is an 72 example: 73 74 08:00:09:70:c4:11 lif{:--:}OSrev.fs 75 76 Then start rbootd (or configure /etc/rc.conf to always start rbootd). Once 77 rbootd is running, the server name will then appear on the MACHINE as part 78 of the possible boot choices in a boot device search (``s'' command). 79 80 Modern firmware operation 81 82 More recent machines mostly those based on the 7100LC, 7200 and 7300LC CPU 83 types have a different PDC version. There is only one interactive mode, 84 with a BOOT_ADMIN> prompt, which provides both boot settings and commands. 85 86 In this case, you will need to set up dhcpd on the server, which can 87 serve bootp protocol requests. Start by editing the /etc/dhcpd.conf on 88 the bootserver, and declare an information block. Here is an example: 89 90 subnet 10.0.0.0 netmask 255.0.0.0 { 91 host boron { 92 filename "lif{:--:}OSrev.fs"; 93 hardware ethernet 08:00:09:70:c4:11; 94 fixed-address 10.42.42.42; 95 } 96 } 97 98 Do not forget to enable dhcpd. 99 100 You will also need to enable tftpd, for the MACHINE to download the 101 installation kernel (`filename' entry) from the server in its tftp 102 directory. 103 104 Common operation 105 106 You are now ready to bootstrap the installation kernel. On your machine, 107 escape to a prompt and boot from the network by entering ``boot lan isl''. 108 On old PDC firmware, you will need to enter administration mode first. 109 110 111Installing using the netboot procedure: 112 113OpenBSDInstallPart2 114 115 Boot your machine from the installation media as described above. 116 117 It will take a while to load the installation kernel, especially from 118 a slow network connection or a CD-ROM, most likely more than a minute. 119 If some action doesn't eventually happen, or the spinning cursor 120 has stopped and nothing further has happened, either your boot 121 media is bad, your diskless setup is incorrect, or you may have 122 a hardware or configuration problem. 123 124OpenBSDInstallPart3(,"sd0") 125 126OpenBSDInstallPart4 127 128OpenBSDInstallPart5(,{:- 129 Due to prom limitations, you should make sure the whole 'a' 130 partition is CONTAINED WITHIN THE FIRST 2GB of the disk if 131 you intend to boot from it.-:}) 132 133 Since the target disk will become the boot disk for your new 134 OpenBSD/MACHINE installation, the disklabel program will restrict 135 the available disk area to keep the first cylinder, which will 136 contain the bootblock, safe from being overwritten. If you don't 137 plan to install a bootblock on this disk, you can reclaim this 138 space with the 'b' command. 139 140OpenBSDInstallPart6({:-CD-ROM, tape, -:}) 141 142OpenBSDURLInstall 143 144OpenBSDCDROMInstall 145 146OpenBSDNFSInstall 147 148OpenBSDDISKInstall(,{:-only -:}) 149 150OpenBSDCommonInstall 151 152OpenBSDTAPEInstall 153 154OpenBSDInstallWrapup 155 156OpenBSDCongratulations 157