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
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
|
Installation is supported from several media types, including:
FFS partitions
Remote NFS partition
CD-ROM
FTP
HTTP
Not all methods are supported on all Sparc Systems and some of them
work only with the floppy or the miniroot installation.
dnl XXX uncomment when cd-rom distribution available
dnl If you have the OpenBSD CD-ROM distribution (and a CD-ROM drive), you
dnl may be able boot from it. If you can boot from the CD-ROM,
dnl you are home free and can proceed to the installation steps. If not,
dnl you will need to do some setup work to prepare a bootable image, either
dnl a floppy, hard drive, or compatible net boot server.
dnl
In addition to the bootable image, you also need to consider how to
access the binary distribution sets to actually install the system.
dnl XXX uncomment when cd-rom distribution available
dnl If you have the OpenBSD CD-ROM distribution you can either access the
dnl CD-ROM directly from the bootable image or remotely mounted on another
dnl system via NFS.
dnl
dnl Although you can access the distribution sets directly from the CD-ROM or
dnl from one of the FTP mirrors over the internet, you may wish to transfer
dnl the sets to a local FTP or NFS server, or copy them to a partition on
dnl the target system's disk.
The variety of options listed may seem confusing, but situations vary
widely in terms of what peripherals and what sort of network arrangements
a user has, the intent is to provide some way that will be practical.
dnl
dnl XXX no floppy available yet
dnl Creating a bootable floppy disk using DOS/Windows:
dnl
dnl First you need to get access to the OpenBSD Bootable floppy
dnl images. If you can access the CD-ROM distribution under DOS
dnl the bootable disks are in the OSREV/MACHINE directory, otherwise
dnl you you will have to download them from one of the OpenBSD
dnl ftp or http mirror sites, using ftp or a web-viewer. In either
dnl case, take care to do "binary" transfers, since these are
dnl images files and any DOS cr/lf translations or control/z EOF
dnl interpretations will result in corrupted transfers.
dnl
dnl You will also need to go to the "tools" directory and grab a
dnl copy of the rawrite.exe utility and its documentation. This
dnl program is needed to correctly copy the bootable filesystem
dnl image to the floppy, since it's an image of a unix partition
dnl containing a ffs filesystem, not a MSDOS format diskette.
dnl
dnl Once you have installed rawrite.exe, just run it and specify the
dnl name of the bootable image, such as "floppy.fs" and the name of
dnl the floppy drive, such as "a:". Be sure to use good quality HD
dnl (1.44MB) floppies, formatted on the system you're using. The
dnl image copy and boot process is not especially tolerant of read
dnl errors.
dnl
dnl Note that if you are using NT to write the images to disk, you
dnl will need to use ntrw.exe instead. It is also available in the
dnl "tools" directory. Grab it and run in with the correct
dnl arguments like this "ntrw <image> <drive>:"
dnl
dnl Note that, when installing, the boot floppy can be write-protected
dnl (i.e. read-only).
dnl
dnl
dnl Creating a bootable floppy disk using SunOS or other Un*x-like system:
dnl
dnl First, you will need obtain a local copy of the bootable filesystem
dnl image as described above. If possible use cksum or md5 to verify
dnl the checksums of the images vs. the values in the CKSUM or MD5
dnl files on the mirror site.
dnl
dnl Next, use the dd(1) utility to copy the file to the floppy drive.
dnl Under SunOS, the command would be:
dnl
dnl dd if=floppy{:--:}OSrev.fs of=/dev/rfd0c bs=36b
dnl
dnl If you are using something other than SunOS, you may have to adapt
dnl this to conform to local naming conventions for the floppy and
dnl options suitable for copying to a "raw" floppy image. The key
dnl issue is that the device name used for the floppy *must* be one
dnl that refers to the whole 2880 block image, not a partition or
dnl compatibility mode, and the copy command needs to be compatible
dnl with the requirement that writes to a raw device must be in
dnl multiples of 512-byte blocks. The variations are endless and
dnl beyond the scope of this document.
dnl
dnl If you're doing this on the system you intend to boot the floppy on,
dnl copying the floppy back to a file and doing a compare or checksum
dnl is a good way to verify that the floppy is readable and free of
dnl read/write errors.
dnl
dnl
dnl XXX uncomment when floppy or miniroot available
dnl XXX make sure to adapt text, especially examples, if only floppy
dnl XXX or miniroot is available, but not both.
dnl Creating a bootable hard disk using SunOS or other Un*x-like system:
dnl
dnl If you don't have a floppy drive you can copy the floppy
dnl installation image "floppy{:--:}OSrev.fs" or the mini-root "miniroot{:--:}OSrev.fs"
dnl onto the hard disk you intend to boot on. Traditionally, the
dnl way to do this is to use dd(1) to place the bootable filesystem
dnl image in the "swap" partition of the disk (while running in
dnl single user mode), and then booting from that partition.
dnl
dnl Using the "b" partition allows you to boot without overwriting
dnl any useful parts of the disk, you can also use another partition,
dnl but don't used the "a" or "c" partition without understanding
dnl the disklabel issues described below under "incompatible systems".
dnl
dnl This requires that you be running SunOS, Solaris, OpenBSD or NetBSD
dnl which have a compatible view of SunOS disk labels and partitions.
dnl
dnl Use the dd(1) utility to copy the file to the hard drive.
dnl Under SunOS, the command would be:
dnl
dnl dd if=floppy{:--:}OSrev.fs of=/dev/rsd0b bs=36b
dnl - or -
dnl dd if=miniroot{:--:}OSrev.fs of=/dev/rsd0b bs=36b
dnl
dnl The blocksize is arbitrary as long as it's a multiple of 512-bytes
dnl and within the maximum supported by the driver, i.e. bs=126b may
dnl not work for all cases. Again, device/partition names may vary,
dnl depending on the OS involved.
dnl
dnl If you are preparing the hard drive on an incompatible system or
dnl don't care about the hard disk contents, you can also install the
dnl bootable image starting at the beginning of the disk. This lets
dnl you prepare a bootable hard-drive even if don't have a working
dnl operating system on your Sparc, but it important to understand
dnl that the bootable image installed this way includes a "disk label"
dnl which can wipe out any pre-existing disklabels or partitioning for
dnl the drive.
dnl
dnl The floppy image is used only for booting, and can be placed in
dnl a partition that will be overwritten during the install process,
dnl since it actually runs off a ram-disk image in the kernel. In
dnl contrast the miniroot is a normal unix root filesystem and you
dnl must place in a partition that will not be overwritten until you've
dnl completed the installation process.
dnl
dnl To copy the floppy image to the whole disk, overwriting labels:
dnl
dnl dd if=floppy{:--:}OSrev.fs of=/dev/rsdXc bs=36b
dnl
dnl Two notes - X should be replaced by the unit number of the target
dnl disk, which is most likely *not* the disk/partition that's your
dnl current root partition. Again names may vary depending on the
dnl OS involved. Second, after doing this, the disklabel will be one
dnl that would be appropriate for a floppy, i.e. one partition of 2880
dnl block, and you'll probably want to change that later on.
dnl
dnl If you're starting with a virgin disk and trying to do this under
dnl SunOS, use format(8) and newfs(8) to set up the partitions and
dnl mark the intended partition as an normal partition type. If you're
dnl using OpenBSD, perhaps on another architecture, OpenBSD will
dnl create a "fictitious label" that will let you access the whole
dnl disk.
dnl
dnl To copy the floppy image to the hard disk, preserving SunOS,
dnl Solaris, NetBSD or OpenBSD labels:
dnl
dnl dd if=floppy{:--:}OSrev.fs of=/dev/rsdXc bs=1b skip=1 seek=1
dnl
dnl You need to be sure that your version of dd(1) supports the
dnl skip and seek operands, otherwise you can try a technique like:
dnl
dnl dd if=/dev/rsdXc of=/tmp/label bs=1b count=1
dnl dd if=floppy{:--:}OSrev.fs of=/dev/rsdXc bs=36b
dnl dd if=/tmp/label of=/dev/rsdXc bs=1b count=1
dnl
dnl In either case, you've created a situation where the disklabel
dnl and the filesystem information don't agree about the partition
dnl size and geometry, however the results will be usable.
dnl
Creating a network bootable setup using SunOS or other Un*x-like system:
The details of setting up a network bootable environment vary
considerably, depending on the network's host. Extract the
OpenBSD diskless(8) man page from the man{:--:}OSrev.tgz distribution
set or see the copy on the OpenBSD web page. You will also
need to reference the relevant man pages or administrators guide
for the host system.
Basically, you will need to set up reverse-arp (rarpd) and boot
parameter (bootpd) information and make the OpenBSD bootblock,
kernel/miniroot partition, and a swap file available as required
by the netboot setup.
The steps necessary to prepare the distribution sets for installation
depend on which method of installation you choose. Some methods
require a bit of setup first that is explained below.
dnl XXX uncomment when floppy available
dnl The floppy installation allows installing OpenBSD directly from FTP
dnl mirror sites over the internet, however you must consider the speed and
dnl reliability of your internet connection for this option. It may save
dnl much time and frustration to use ftp get/reget to transfer the
dnl distribution sets to a local server or disk and perform the installation
dnl from there, rather than directly on the internet.
dnl
To install OpenBSD using a remote partition, mounted via
NFS, you must do the following:
NOTE: This method of installation is recommended only for
those already familiar with using BSD network
configuration and management commands. If you aren't,
this documentation should help, but is not intended to
be all-encompassing.
Place the OpenBSD distribution sets you wish to install into a
directory on an NFS server, and make that directory mountable
by the machine on which you are installing or upgrading OpenBSD.
This will probably require modifying the /etc/exports file on
of the NFS server and resetting its mount daemon (mountd).
(Both of these actions will probably require superuser
privileges on the server.)
You need to know the numeric IP address of the NFS server,
and, if the server is not on a network directly connected to
the machine on which you're installing or upgrading OpenBSD,
you need to know the numeric IP address of the router closest
to the OpenBSD machine. Finally, you need to know the numeric
IP address of the OpenBSD machine itself.
Once the NFS server is set up properly and you have the
information mentioned above, you can proceed to the next step
in the installation or upgrade process. If you're installing
OpenBSD from scratch, go to the section on preparing your hard
disk, below. If you're upgrading an existing installation, go
directly to the section on upgrading.
If you are upgrading OpenBSD, you also have the option of installing
OpenBSD by putting the new distribution sets somewhere in your existing
file system, and using them from there. To do that, you must do the
following:
Place the distribution sets you wish to upgrade somewhere in
your current file system tree. At a bare minimum, you must
upgrade the "base" binary distribution, and so must put the
"base{:--:}OSrev" set somewhere in your file system. If you wish,
you can do the other sets, as well, but you should NOT upgrade
the "etc" distribution; the "etc" distribution contains system
configuration files that you should review and update by hand.
Once you have done this, you can proceed to the next step in
the upgrade process, actually upgrading your system.
|
