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
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
|
OpenBSDInstallPrelude
OpenBSDInstallPart2
If you are using the floppy{:--:}OSrev.fs floppy, type "boot dva0"
and hit return when presented with the SRM console prompt.
You should see info about the primary and secondary boot
and then the kernel should start to load. It will take a
while to load the kernel from the floppy, 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 floppy is bad or you are having
hardware problems. Either you have a bad boot floppy (in
which case you should try another) or your alpha is not
currently supported by OpenBSD.
If you are booting from the CD-ROM, type "show device" and
hit return when presented with the SRM console prompt.
You should see a list of devices; the SCSI devices will
start with "DKA". Find the SCSI device that is your CD-ROM
and enter "boot dka4 -fi OSREV/alpha/bsd", assuming that your
CD-ROM was listed as DKA4* (substitute the SCSI id of your
CD-ROM for the "4"). You should see info about the primary
and secondary boot and then the kernel should start to
load. If the kernel fails to load or the spinning cursor
has stopped and nothing further has happened, you either
have a hardware problem or your alpha is not currently
supported by OpenBSD; try booting from a floppy instead.
OpenBSDBootMsgs
While booting, you will probably see several warnings. You
should be warned that the kernel can't figure out what device
it booted from and that no swap space is present. Do not be
alarmed, these are completely normal. The first warning
occurs because while OpenBSD/alpha can boot from the floppy
drive, the kernel itself lacks a floppy driver. When you reach
the prompt asking you for a shell name, just hit return.
You will next be asked for your terminal type. If you are
installing from a non-serial console, the default of "sun"
if 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). After
entering the terminal type you will be asked whether you
wish to do an "install" or an "upgrade". Enter 'i' for a
fresh install or 'u' to upgrade an existing installation.
You will be presented with a welcome message and asked if
you really wish to install (or upgrade). Assuming you
answered yes, the install program will then tell you which
disks of that type it can install on, and ask you which it
should use. The name of the disk is typically "sd0" for
SCSI drives or "wd0" for IDE drives. Reply with the name
of your disk.
Next the disk label which defines the layout of the OpenBSD
file systems must be set up. The installation script will
invoke an interactive editor allowing you to do this. Note
that partition 'c' inside this disk label should ALWAYS
reflect the entire disk, including any non-OpenBSD portions.
If you are labeling a new disk, you will probably start
out with an 'a' partition that spans the disk. In this
case You should delete 'a' before adding new partitions.
The root file system should be in partition 'a', and swap
is usually in partition 'b'. It is recommended that you
create separate partitions for /usr and /var, and if you
have room for it, one for /home. For help in the disk
label editor, enter '?' or 'M' to view the manual page (see
the info on the ``-E'' flag).
The swap partition (usually 'b') should have a type of "swap", all
other native OpenBSD partitions should have a type of "4.2BSD".
Block and fragment sizes are usually 8192 and 1024 bytes, but can
also be 16384 and 2048 bytes.
The install program will now label your disk and ask which file
systems should be created on which partitions. It will auto-
matically select the 'a' partition to be the root file system.
Next it will ask for which disk and partition you want a file
system created on. This will be the same as the disk name (eg.
"sd0") with the letter identifying the partition (eg. "d")
appended (eg. "sd0d"). Then it will ask where this partition is
to be mounted, eg. /usr. This process will be repeated until
you enter "done".
At this point you will be asked to confirm that the file system
information you have entered is correct, and given an opportunity
to change the file system table. Next it will create the new file
systems as specified, OVERWRITING ANY EXISTING DATA. This is the
point of no return.
After all your file systems have been created, the install program
will give you an opportunity to configure the network. The network
configuration you enter (if any) can then be used to do the install
from another system using NFS, HTTP or FTP, and will also be the
configuration used by the system after the installation is complete.
If you select to configure the network, the install program will
ask you for a name of your system and the DNS domain name to use.
Note that the host name should be without the domain part, and that
the domain name should NOT {:-include-:} the host name part.
Next the system will give you a list of network interfaces you can
configure. For each network interface you select to configure, it
will ask for the IP address to use, the symbolic host name to use,
the netmask to use and any interface-specific flags to set. The
interface-specific flags are usually used to determine which media
the network card is to use. The flags usually carry the following
meaning:
-link0 -link1 Use BNC (coaxial) port [default]
link0 -link1 Use AUI port
link0 link1 Use UTP (twisted pair) port
After all network interfaces has been configured the install pro-
gram will ask for a default route and IP address of the primary
name server to use. You will also be presented with an opportunity
to edit the host table.
At this point you will be allowed to edit the file system table
that will be used for the remainder of the installation and that
will be used by the finished system, following which the new file
systems will be mounted to complete the installation.
After these preparatory steps has been completed, you will be
able to extract the distribution sets onto your system. There
are several install methods supported; FTP, HTTP, tape, CD-ROM, NFS
or a local disk partition. To install from a tape, the distrib-
ution sets must have been written to tape prior to running the
installation program, either as tar images or as gzipped tar
images. Note that installation from floppies is not currently
supported.
OpenBSDFTPInstall
OpenBSDHTTPInstall
OpenBSDTAPEInstall
OpenBSDCDROMInstall
OpenBSDNFSInstall
OpenBSDDISKInstall({:-"wdN" or -:},{:-only -:})
OpenBSDCommonFS
OpenBSDCommonURL
OpenBSDCongratulations
|
