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
|
dnl $OpenBSD: install,v 1.21 2008/08/05 22:58:01 miod Exp $
OpenBSDInstallPrelude({:-MSCP or other non-SCSI disks-:})
For most systems, the easiest way to install OpenBSD/MACHINE OSREV is via
diskless booting over an Ethernet network. You will need both the
"boot.mop" image and the "bsd.rd" kernel to boot. You will also need a
machine configured as a rarp, MOP, bootparam, and NFS server.
However, should your VAX support local storage, we provide a floppy sized
image that can be written onto a disk in another machine, and when booted
on the VAX will present you with the standard install prompt. If you used
this method you can skip ahead to the "ready to install OpenBSD" section.
Booting from Network:
In order to bootstrap via the network, you must provide a second system to
act as a boot server. It is convenient if this is a second OpenBSD machine
as the necessary services are already installed, although source code for
such programs as mopd can be found in OpenBSD's source tree, and should be
reasonably portable to other UN*X-like operating systems. More information
on diskless booting can be found in the OpenBSD diskless(8) manual page.
When you turn on your VAX, it will run an extensive and model specific set
of self-diagnostic ROM routines. When it is done, you should see a >>>
prompt (also called the chevron prompt) on the console. Typing "show dev"
or "show ethernet" to get the VAX Ethernet device's MAC address usually
works; also try "TEST 50" on MicroVAXen 2000 and 3100.
You will need to create an /etc/ethers file on the bootserver. This file
will be used by rarpd to answer rarp (Ethernet address->IP address) requests.
The format of this file is the Ethernet address followed by the machine
name or address. Here is an example:
08:00:2b:24:72:00 quickvax
Note that the server must be able to resolve "quickvax" to the IP address
you intend to use for your new vax system. This can be accomplished by an
entry in /etc/hosts.
Then start rarpd (or configure /etc/rc.conf to always start rarpd).
Copy boot.mop into /tftpboot/mop/1a2b3c4d5e6f.SYS, where "1a2b3c4d5e6f"
represents the six octets of your Ethernet address. For example, the
filename for the machine described above would be "08002b247200.SYS".
Note that all non alphanumeric characters must be stripped and the
MAC portion must be lower case, the extension upper. Start mopd by
typing "mopd -a", if you've not configured it to run by default.
Next you need to export a directory for your new machine to mount over
NFS. This is accomplished by adding an entry to /etc/exports such as:
/export/MACHINE -maproot=root quickvax
In a typical NFS install, the directory `/export/MACHINE' will contain
the ramdisk kernel image `bsd.rd', although it is possible to populate
it with a full VAX filesystem to act as a true NFS root. Ensure that your
server is configured to export NFS properly, and is running nfsd, mountd,
and the rpc portmapper. See the exports(5) manpage for more information.
Finally, you need to add an entry for your MACHINE in /etc/bootparams.
For example:
quickvax root=myserver:/export/MACHINE
Enable rpc.bootparamd either by turning it on in /etc/rc.conf and rebooting,
or by running it manually.
You are now ready to mopboot your MACHINE.
Typing "B <DEVICE>", where <DEVICE> is your VAX's Ethernet device, at the
chevron prompt should then load the OpenBSD booter.
Installing using the netboot procedure:
OpenBSDInstallPart2
Boot your machine from the installation media as described above.
The OpenBSD bootloader will appear, and a countdown should begin;
type any key on the console to interrupt and type
boot bsd.rd
It will take a while to load the kernel especially on a slow
machine, or 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 diskless setup is incorrect, or you may have a
hardware or configuration problem.
OpenBSDBootMsgs(the quick brown vax jumped over the lazy pdp,"sd0" for SCSI drives,{:-"ra0" for MSCP
drives-:}, or "hd0" for MFM drives)
You will next be asked for your terminal type. If you are
installing from a non-serial console, the default of "vt220"
is 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 vt220.)
OpenBSDInstallPart3
OpenBSDInstallPart4
OpenBSDInstallPart5(sd0)
OpenBSDInstallNet({:-CD-ROM, NFS, -:})
OpenBSDFTPInstall
OpenBSDHTTPInstall
OpenBSDTAPEInstall
OpenBSDCDROMInstall
OpenBSDNFSInstall
OpenBSDDISKInstall(,{:-only -:})
OpenBSDCommonFS(NFS)
OpenBSDCommonURL
OpenBSDInstallWrapup
OpenBSDInstallWrapupPart2
OpenBSDCongratulations
|
