summaryrefslogtreecommitdiff
path: root/distrib/notes/amiga/install
blob: 0c4063776d2b97477936c1d4d28b2f35c856d654 (plain)
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
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
Installing OpenBSD is a relatively complex process, but, if you have
this document in hand and are careful to read and remember the
information which is presented to you by the install program, it
shouldn't be too much trouble.

Before you begin, you must have already prepared your hard disk as
detailed in the section on preparing your system for install.

The following is a walk-through of the steps necessary to get OpenBSD
installed on your hard disk.  If you wish to stop the installation,
you may hit Control-C at any prompt, but if you do, you'll have to
begin again from scratch.

	If you have a small machine (less than 6MB of fast RAM) you'll
	have to setup a miniroot filesystem in the swap partition, as
	described in the "Preparing your System for OpenBSD Installation"
	section above.  If your machine has 6MB or more we strongly
	recommend using the ramdisk kernel instead.  This way you don't
	need to setup any root image beforehand.

	You then need to have "ixemul.library" in your LIBS: directory
	on AmigaDOS.  You also need to have the "loadbsd" program
	in your command path.  If AmigaDOS complains about loadbsd
	not being an executable file, be sure that the "Execute"
	protection bit is set.  If not, set it with the command:
		Protect loadbsd add e

	Next you need to get yourself into OpenBSD by loading the
	kernel from AmigaDOS with loadbsd like so:

		loadbsd bsd.rd

	or, if you are doing a miniroot install:

		loadbsd -b bsd


	If you have an AGA machine, and your monitor will handle
	the dblNTSC mode, you may also include the "-A" option to
	enable the dblNTSC display mode.

	You should see the screen clear and some information about
	your system as the kernel configures the hardware.  Note which
	hard disk device(s) are configured (sd0, sd1, etc).  You will
	be asked for disknames later during the install.  If you cannot
	read the messages as they scroll by, do not worry -- you can get
	at this information later inside the install program.  If you
	are doing the miniroot install you will be prompted for a root
	device.  At this time type 'sd0*', where '0' is the device which
	holds the miniroot-containing swap partition you created during
	the hard disk preparation.  If the system should hang after
	entering the root device, try again with

		loadbsd -I ff -b bsd

	This disables synchronous transfer on all SCSI devices.  For
	ramdisk installations this kind of hang might occur later during
	the install when accessing the SCSI disk for the first time.  If
	such a hang occurs, try again with:

		loadbsd -I ff bsd.rd

	While booting, you will probably see several warnings.  You
	should be warned that no swap space is present, and that
	init(8) cannot find /etc/rc.  Do not be alarmed, these are
	completely normal.  When you reach the prompt asking you for a
	shell name, just hit return.

	You will be asked which terminal type to use, you should just
	hit return to select the default (vt220).

	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 the
	A4000 IDE drives or "wd0" for ISA-connected IDE drives.  Reply
	with the name of your disk.

	The install program will now ask which file systems should be
	created on which partitions.  It will automatically 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
	just hit return.

	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.

	The install program will now make the filesystems you specified.
	There should be only one error in this section of the installation.
	It will look like this:

		newfs: ioctl (WDINFO): Invalid argument
		newfs: /dev/rsd0a: can't rewrite disk label

	If there are any others, restart from the the beginning of
	the installation process.  This error is ok as the Amiga
	does not write disklabels currently.  You should expect
	this error whenever using newfs.

	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 are not currently
	supported.

	To install via FTP:
		To begin an FTP install you will need the following
		pieces of information.  Don't be daunted by this list;
		the defaults are sufficient for most people.
		    1) Proxy server URL if you are using a URL-based
		       ftp proxy (squid, CERN ftp, Apache 1.2 or higher).
		       You need to define a proxy if you are behind a
		       firewall that blocks outgoing ftp (assuming you
		       have a proxy available to use).
		    2) Do you need to use passive mode ftp?  Most modern
		       ftp servers are capable of dealing with passive
		       ftp connections.  You only need to enable this
		       option if you are behind a firewall that allows
		       outgoing ftp but blocks incoming tcp ports > 1023.
		       If in doubt say yes to this option.
		       Note that you will not be asked about passive
		       ftp if you are using a proxy.
		    3) The IP address (or hostname if you enabled
		       DNS earlier in the install) of an ftp server
		       carrying the OpenBSD 2.2 distribution.
		       If you don't know, just hit return when
		       asked if you want to see a list of such hosts.
		    4) The ftp directory holding the distribution sets.
		       The default value of pub/OpenBSD/2.2/amiga
		       is almost always correct.
		    5) The login and password for the ftp account.
		       The default will be correct unless you are
		       doing non-anonymous ftp.

		For instructions on how to complete the installation via
		ftp, see the section named "Common URL installations" below.

	To install via HTTP:
		To begin an HTTP install you will need the following
		pieces of information:
		    1) Proxy server URL if you are using a URL-based
		       http proxy (squid, CERN ftp, Apache 1.2 or higher).
		       You need to define a proxy if you are behind a
		       firewall that blocks outgoing http connections
		       (assuming you have a proxy available to use).
		    3) The IP address (or hostname if you enabled
		       DNS earlier in the install) of an http server
		       carrying the OpenBSD 2.2 distribution.
		       If you don't know, just hit return when
		       asked if you want to see a list of such hosts.
		    4) The directory holding the distribution sets.
		       There is no standard location for this;
		       You should use the directory specified
		       along with the server in the list of official
		       http mirror sites that you received in step 3.

		For instructions on how to complete the installation via
		http, see the section named "Common URL installations" below.

	To install from tape:
		In order to install from tape, the distribution sets to be
		installed must have been written to tape previously, either
		in tar format or gzip-compressed tar format.

		You will also have to identify the tape device where the
		distribution sets are to be extracted from.  This will
		typically be "nrst0" (no-rewind, raw interface).

		Next you will have to provide the file number of the set
		that is to be extracted.  Note that the file number starts
		at 1, which is the first file written to the tape.

		The install program will not automatically detect whether
		an image has been compressed, so it will ask for that
		information before starting the extraction.

	To install from CD-ROM:
		When installing from a CD-ROM, you will be asked which
		device holds the distribution sets.  This will typically
		be either "cd0" or "acd0".  Next you will be asked which
		partition on the CD-ROM the distribution is to be loaded
		from.  This is normally partition "a".

		Next you will have to identify the file system type that
		has been used to create the distribution on the CD-ROM,
		this can be either FFS or ISO CD9660.  The OpenBSD CD
		distribution uses the CD9660 format.

		You will also have to provide the relative path to the
		directory on the CD which holds the distribution, for the
		amiga this is "2.2/amiga".

		For instructions on how to complete the installation from
		the CD-ROM distribution, see the section named "Common
		file system installations" below.
		
	To install from a NFS mounted directory:
		When installing from a NFS-mounted directory, you must
		have completed network configuration above, and also
		set up the exported file system on the NFS server in
		advance.

		First you must identify the IP address of the NFS server
		to load the distribution from, and the file system the
		server expects you to mount.

		The install program will also ask whether or not TCP
		should be used for transport (the default is UDP).  Note
		that TCP only works with newer NFS servers.

		You will also have to provide the relative path to the
		directory on the file system where the distribution sets
		are located.  Note that this path should not be prefixed
		with a '/'.

		For instructions on how to complete the installation from
		the CD-ROM distribution, see the section named "Common
		file system installations" below.

	To install from a local disk partition:
		When installing from a local disk partition, you will
		first have to identify which disk holds the distribution
		sets.  This is normally "sdN" or "wdN" where N is a
		number 0 through 9.  Next you will have to identify the
		partition within that disk that holds the distribution,
		this is a single letter between 'a' and 'p'.

		You will also have to identify the type of file system
		residing in the partition identified.  Currently you can
		install from partitions that has been formatted as
		Berkeley fast file system (ffs) or AmigaDOS FFS (ados).

		You will also have to provide the relative path to the
		directory on the file system where the distribution sets
		are located.  Note that this path should not be prefixed
		with a '/'.

		For instructions on how to complete the installation from
		the a local disk partition, see the next section.
		
	Common file system installations:
		The following instructions are common to installations
		from local disk partitions, NFS mounted directories and
		CD-ROMs.

		A list of available distribution sets will be listed.  If
		any sets has already been extracted, those will be marked
		with an X.  Enter the name of one distribution set at a
		time, until all desired distribution sets has been
		installed on your system.

	Common URL installations:
		Once you have entered the required information, the
		install program will fetch a file list and present
		a list of all the distribution sets that were found
		in the specified directory.  (If no valid sets were found,
		you will be notified and given the option of unpacking
		any gzipped tar files found or getting a file list if
		none were found.)

		At this point you may individually select distribution
		sets to install or enter "all" to install all of
		the sets (which is what most users will want to do).
		You may also enter "list" to get a file list or
		"done" when you are done selecting distribution sets.
		(It is also possible to enter an arbitrary filename
		and have it treated as a file set).

		Once you have selected the file sets you want to install
		and entered "done" you will be prompted to verify that
		you really do want to download and install the files.
		Assuming you acquiesce, the files will begin to download
		and unpack.  If not, you will be given the option of
		installing sets via one of the other install methods.


	When all the selected distribution sets has been extracted, you
	will be allowed to select which time zone your system will be
	using, all the device nodes needed by the installed system will
	be created for you and the file systems will be unmounted.  For
	this to work properly, it is expected that you have installed
	at least the "base22" and "etc22" distribution sets.


Congratulations, you have successfully installed OpenBSD 2.2.  When you
reboot into OpenBSD, you should log in as "root" at the login prompt.
There is no initial password, but if you're using the machine in a
networked environment, you should create yourself an account and
protect it and the "root" account with good passwords.

Some of the files in the OpenBSD 2.2 distribution might need to be
tailored for your site.  In particular, the /etc/sendmail.cf file will
almost definitely need to be adjusted, and other files in /etc will
probably need to be modified, as well.  If you are unfamiliar with
UN*X-like system administration, it's recommended that you buy a book
that discusses it.