1dnl $OpenBSD: install,v 1.4 2003/03/25 19:57:20 miod Exp $ 2dnl lots of texts coming from {mac68k,mvme68k,vax}/install initially 3OpenBSDInstallPrelude 4 5Currently, the only way to bootstrap the installation procedure is 6to boot the miniroot over the network. 7 8 9Booting from Network: 10 11In order to bootstrap via the network, you must provide a second system to 12act as a boot server. It is convenient if this is a second OpenBSD machine 13as the necessary services are already installed, although source code for 14such programs as mopd can be found in OpenBSD's source tree, and should be 15reasonably portable to other UN*X-like operating systems. More information 16on diskless booting can be found in the OpenBSD diskless(8) manual page. 17 18Your MACHINE expects to be able to download a so-called LIF (``Logical 19Interchange Format'') image, containing both the boot code and the kernel, 20via the HP rboot protocol, for older firmware, or via bootp or dhcp, for 21more recent firmware. 22 23Old firmware operation 24 25PDC ROM v1.4 and below are easily recognizable, as they will start with a 26text banner. There are two levels of interactive commands in this version. 27The first level is a short menu: 28 29 b) Boot from specified device 30 s) Search for bootable device 31 a) Enter Boot Administration mode 32 x) Exit and continue boot sequence 33 34 Select from menu: 35 36In this case, you will need to setup rbootd on the server. Start by creating 37an /etc/rbootd.conf file on the bootserver. The format of this file is the 38ethernet address followed by the LIF filename. Here is an example: 39 40 08:00:09:70:c4:11 lif{:--:}OSrev.fs 41 42Then start rbootd (or configure /etc/rc.conf to always start rbootd). Once 43rbootd is running, the server name will then appear on the MACHINE as part of 44the possible boot choices in a boot device search (``s'' command). 45 46Modern firmware operation 47 48PDC ROM 1.5 and above will start with a small graphics window at the screen 49center (unless you are using a serial console). There is only one interactive 50mode, with a BOOT_ADMIN> prompt, which provides both boot settings and 51commands. 52 53In this case, you will need to setup either bootpd or dhcpd on the server. 54Assuming a bootp setup, start by editing the /etc/bootptab on the bootserver, 55and declare an information block. Here is an example: 56 57 boron:\ 58 ha=08000970c411:\ 59 bf=lif{:--:}OSrev.fs:\ 60 hd=:\ 61 ht=ethernet:\ 62 ip=10.42.42.42:\ 63 rp=/export/MACHINE:\ 64 sm=255.0.0.0:\ 65 td=/tftpboot: 66 67Do not forget to enable bootpd, either as a standalone process, or via inetd. 68 69You will also need to enable tftpd, for the MACHINE to download the 70miniroot (bf entry) from the server in the /tftpboot (td entry) directory. 71 72Common operation 73 74You are now ready to bootstrap the miniroot. On your MACHINE, escape to a 75prompt and boot from the network by entering ``boot lan isl''. On old PDC 76firmware, you will need to enter administration mode first. 77 78 79Installing using the netboot procedure: 80 81OpenBSDInstallPart2 82 83 Boot your machine from the installation media as described above. 84 85dnl mention slow cdrom someday 86 It will take a while to load the miniroot image, especially from 87 a slow network connection, most likely more than a minute. 88 If some action doesn't eventually happen, or the spinning cursor 89 has stopped and nothing further has happened, either your boot 90 media is bad, your diskless setup is incorrect, or you may have 91 a hardware or configuration problem. 92 93 When presented with the boot prompt, simply press enter, or wait 94 for the kernel to autoboot after 5 seconds. 95 96OpenBSDBootMsgs 97 98 You will next be asked for your terminal type. If you are 99 installing from a non-serial console, the default of "vt100" 100 is correct. If you are installing from a serial console 101 you should choose the terminal type from amongst those listed. 102 (If your terminal type is xterm, just use vt100). 103 104OpenBSDInstallPart3 105 106OpenBSDInstallPart4 107 108 Since the target disk will become the boot disk for your new 109 OpenBSD/MACHINE installation, the disklabel program will restrict 110 the available disk area to keep the first cylinder, which will 111 contain the bootblock, safe from being overwritten. If you don't 112 plan to install a bootblock on this disk, you can reclaim this 113 space with the 'b' command. 114 115OpenBSDInstallPart5(sd0) 116 117OpenBSDInstallNet({:-CD-ROM, -:},nofloppy) 118 119OpenBSDFTPInstall 120 121OpenBSDHTTPInstall 122 123OpenBSDTAPEInstall 124 125OpenBSDCDROMInstall 126 127OpenBSDNFSInstall 128 129OpenBSDDISKInstall({:-"hdN" or -:},{:-only -:}) 130 131OpenBSDCommonFS 132 133OpenBSDCommonURL 134 135OpenBSDCongratulations 136