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
|
dnl $OpenBSD: install,v 1.19 2010/03/16 17:23:09 miod Exp $
OpenBSDInstallPrelude
There are several ways to install OpenBSD onto a disk. The easiest way
in terms of preliminary setup is to use the OpenBSD ramdisk kernel that
can be booted via BOOTP. The normal way is to use the bootable CD-ROM
mini image.
Booting over the network:
dnl XXX provide more details!!!
First, a bootp or dhcpd server needs to be set up. The bootpd(8) or
dhcpd(8) manual page on your server should provide detailed information
on how to set up the server.
The PROM, by default, will configure itself to use the IP address set in
the `netaddr' environment variable. To force the PROM to always get an
address from a bootp or dhcp server, clear the variable (`unsetenv netaddr')
before attempting to boot from the network. Alternatively, you may want to
make sure the value of this variable is correct.
Note that, if the `netaddr' variable is unset, the PROM will initialize it
to the address obtained from the bootp or dhcp server.
The bootp or dhcp server needs to know the ethernet address of the
system. On O2 systems, this address can be found by using the ``printenv''
command in the Maintenance Console, looking for the ``eaddr'' variable.
On other systems, this address is ususally written on a factory sticker
on the back of the machine.
The server should also provide a tftp location, where the proper bsd.rd
file should be available.
Once the server is set up, boot with the following command in the
Maintenance Console:
> bootp()/bsd.rd.IP32
(replacing `IP32' by the family name suitable for your machine).
Booting from CD-ROM installation media:
(Note: this boot method only works on IP32 systems at the moment).
From the System Maintenance Menu, select '2' (or click on the
appropriate icon if in graphics console) to Install System Software.
If necessary, select the proper CD-ROM drive, and press enter to
confirm your choice. Insert the installation CD-ROM (if you did not
do so already) and press enter to boot the system.
If the boot is successful, you will get a loader version message,
executable sizes, and then the kernel copyright and device probe
messages. Boot failure modes are typically a lot of CD-ROM drive
activity, but no messages or complaints about magic numbers,
checksums or formats.
Installing the system:
OpenBSDInstallPart2
Boot your machine from the installation media as described above.
It will take a while to load the kernel 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 isn't correct, or you may have a hardware or
configuration problem.
OpenBSDInstallPart3(,"sd0")
OpenBSDInstallPart4
OpenBSDInstallPart5
No partitions should overlap with the SGI Volume Header, which by
default will use the first 3134 sectors. Additionally, the 'a'
partition must be the first partition on the disk, immediately
following the SGI Volume Header. If the default Volume Header size is
used, the 'a' partition should be located at offset 3135. If the 'a'
partition is not located immediately after the Volume Header the boot
loader will not be able to locate and load the kernel.
dnl XXX Note that this is a #$%@ boot blocks limitation which should be fixed
dnl XXX by reading the real label in the boot blocks.
OpenBSDInstallPart6({:-CD-ROM, tape, NFS -:})
OpenBSDURLInstall
OpenBSDCDROMInstall
OpenBSDNFSInstall
OpenBSDDISKInstall(,{:-only -:})
OpenBSDCommonInstall
OpenBSDTAPEInstall
OpenBSDInstallWrapup
OpenBSDCongratulations
|
