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
|
dnl $OpenBSD: xfer,v 1.33 2002/07/25 19:29:32 miod Exp $
Installation is supported from several media types, including:
CD-ROM
dnl put back after 3.2
dnl FFS partitions
Tape
Remote NFS partition
FTP
HTTP
Not all methods are supported on all Sparc Systems and some of them
work only with the floppy or the miniroot installation.
If you have the OpenBSD CD-ROM distribution (and a CD-ROM drive), you
may be able boot from it. Not all sparc systems support booting from
CD-ROM and the current boot image is only known to work on sun4c and
some sun4m architecture workstations. 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, tape, 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. If
you have the OpenBSD CD-ROM distribution you can either access the
CD-ROM directly from the bootable image or remotely mounted on another
system via NFS.
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 or NFS server, or copy them to a partition on
the target system's disk or onto a SCSI tape.
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 floppy
installation image "floppy{:--:}OSrev.fs" or 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 disklabel 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=floppy{:--:}OSrev.fs of=/dev/rsd0b bs=36b
- or -
dd if=miniroot{:--:}OSrev.fs of=/dev/rsd0b bs=36b
and under Solaris:
dd if=floppy{:--:}OSrev.fs of=/dev/rdsk/c0t0d0s1 bs=36b
- or -
dd if=miniroot{:--:}OSrev.fs of=/dev/rdsk/c0t0d0s1 bs=36b
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 Sparc, but it 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.
The floppy image is used only for booting, and can be placed in
a partition that will be overwritten during the install process,
since it actually runs off a ram-disk image in the kernel. In
contrast the miniroot is a normal unix root filesystem and you
must place in a partition that will not be overwritten until you've
completed the installation process.
To copy the floppy image to the whole disk, overwriting labels:
Under SunOS:
dd if=floppy{:--:}OSrev.fs of=/dev/rsdXc bs=36b
and under Solaris:
dd if=floppy{:--:}OSrev.fs of=/dev/rdsk/c0tXd0s2 bs=36b
Two notes - X should be replaced by the unit number of the target
disk, which is most likely *not* the disk/partition that's your
current root partition. Again names may vary depending on the
OS involved. Second, after doing this, the disklabel will be one
that would be appropriate for a floppy, i.e. one partition of 2880
block, and you'll probably want to change that later on.
If you're starting with a virgin disk and trying to do this under
SunOS or Solaris, use format(8/1M) and newfs(8/1M) 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.
To copy the floppy image to the hard disk, preserving SunOS,
Solaris, NetBSD or OpenBSD labels:
Under SunOS:
dd if=floppy{:--:}OSrev.fs of=/dev/rsdXc bs=1b skip=1 seek=1
and Solaris:
dd if=floppy{:--:}OSrev.fs of=/dev/rdsk/c0tXd0s2 \
bs=1b skip=1 seek=1
You need to be sure that your version of dd(1) supports the
skip and seek operands, otherwise you can try a technique like:
dd if=/dev/rsdXc of=/tmp/label bs=1b count=1
dd if=floppy{:--:}OSrev.fs of=/dev/rsdXc bs=36b
dd if=/tmp/label of=/dev/rsdXc bs=1b count=1
In either case, you've created a situation where the disklabel
and the filesystem information don't agree about the partition
size and geometry, however the results will be usable.
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.
OpenBSDXferPrelude
OpenBSDXferBootTape(xbase xfont xserv xshare,bsd.rd obs=8k conv=sync,boot obs=8k conv=sync)
dnl OpenBSDXferNFS
OpenBSDXferNFS(noupgrade)
dnl put back after 3.2
dnl
dnl OpenBSDXferFFS
|
