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