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
|
dnl $OpenBSD: xfer,v 1.24 2005/03/18 13:30:53 miod Exp $
Installation is supported from several media types, including:
CD-ROM (NOT supported if booting from floppy)
FFS partitions (for upgrades only)
Tape
FTP
HTTP
If you have the OpenBSD CD-ROM distribution (and a CD-ROM drive), you may be
able to boot from it, or from the supplied bootable CD-ROM mini image. If you
can boot from the CD-ROM, you are home free and can proceed to the
installation steps. If not, you will need to do some setup work to prepare
a bootable image, either a floppy, hard drive, or compatible net boot
server.
In addition to the bootable image, you also need to consider how to
access the binary distribution sets to actually install the system.
Although you can access the distribution sets directly from the CD-ROM or
from one of the FTP mirrors over the internet, you may wish to transfer
the sets to a local FTP server, or copy them to a partition on the target
system's disk.
OpenBSDXferFloppyFromDOS
OpenBSDXferFloppyFromUNIX
Creating a bootable hard disk using SunOS, Solaris or other Un*x-like system:
If you don't have a floppy drive you can copy the mini-root
"miniroot{:--:}OSrev.fs" onto the hard disk you intend to boot on.
Traditionally, the way to do this is to use dd(1) to place the
bootable filesystem image in the "swap" partition of the disk
(while running in single user mode), and then booting from that
partition.
Using the "b" partition allows you to boot without overwriting
any useful parts of the disk; you can also use another partition,
but don't used the "a" or "c" partition without understanding
the disk label issues described below under "incompatible systems".
This requires that you be running SunOS, Solaris, OpenBSD, or NetBSD,
which have a compatible view of SunOS disk labels and partitions.
Use the dd(1) utility to copy the file to the hard drive.
The command would likely be, under SunOS:
dd if=miniroot{:--:}OSrev.fs of=/dev/rsd0b bs=64b
and under Solaris:
dd if=miniroot{:--:}OSrev.fs of=/dev/rdsk/c0t0d0s1 bs=64b
The blocksize is arbitrary as long as it's a multiple of 512-bytes
and within the maximum supported by the driver, i.e. bs=126b may
not work for all cases. Again, device/partition names may vary,
depending on the OS involved.
If you are preparing the hard drive on an incompatible system or
don't care about the hard disk contents, you can also install the
bootable image starting at the beginning of the disk. This lets
you prepare a bootable hard-drive even if don't have a working
operating system on your machine, but it is important to understand
that the bootable image installed this way includes a "disk label"
which can wipe out any pre-existing disklabels or partitioning for
the drive.
If you're starting with a virgin disk and trying to do this under
SunOS, use format(8) and newfs(8) to set up the partitions and
mark the intended partition as an normal partition type. If you're
using OpenBSD, perhaps on another architecture, OpenBSD will
create a "fictitious label" that will let you access the whole
disk.
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 (rpc.bootparamd) information and make the OpenBSD
bootblock, kernel/miniroot partition, and a swap file available
as required by the netboot setup.
OpenBSDXferPrelude
OpenBSDXferBareTape(xbase xetc xfont xserv xshare)
OpenBSDXferFFS
|
