xfer revision 1.3
1Installation is supported from several media types, including:
2	* Tape
3	* NFS
4	* CD-ROM
5	* FTP
6
7Note that installing on a "bare" machine requires some bootable
8device; either a tape drive or Sun-compatible NFS server.
9
10The procedure for transferring the distribution sets onto
11installation media depends on the type of media.  Instructions
12for each type of media are given below.
13
14In order to create installation media, you will need all the 
15files in this directory:
16	.../NetBSD-_VER/sun3/
17
18* Creating boot/install tapes:
19
20Installing from tape is the simplest method of all.
21This method uses two tapes; one called the "boot"
22tape, and another called the "install" tape.
23
24The boot tape is created as follows:
25
26	cd .../NetBSD-_VER/sun3/installation/tapeimage
27	sh MakeBootTape /dev/nrst0
28
29The install tape is created as follows:
30
31	cd .../NetBSD-_VER/sun3/installation/tapeimage
32	sh MakeInstallTape /dev/nrst0
33
34If the tapes do not work as expected, you may need to explicitly
35set the EOF mark at the end of each tape segment.  It may also be
36necessary to use the `conv=osync' argument to dd(1).  Note that
37this argument is incompatible with the `bs=' argument.  Consult
38the tape-related manual pages on the system where the tapes are
39created for more details.
40
41* Boot/Install from NFS server:
42
43If your machine has a disk and network connection, but no tape drive,
44it may be convenient for you to install NetBSD over the network.  This
45involves temporarily booting your machine over NFS, just long enough
46so you can initialize its disk.  This method requires that you have
47access to an NFS server on your network so you can configure it to
48support diskless boot for your machine.  Configuring the NFS server
49is normally a task for a system administrator, and is not trivial.
50
51If you are using a NetBSD system as the boot-server, have a look at
52the diskless(8) manual page for guidelines on how to proceed with
53this.  If the server runs another operating system, consult the
54documentation that came with it (i.e. add_client(8) on SunOS).
55
56Your Sun3 expects to be able to download a second stage bootstrap
57program via TFTP after having acquired its IP address through RARP
58when instructed to boot "over the net".  It will look for a filename
59derived from the machine's IP address expressed in hexadecimal.  For
60example, a sun3 which has been assigned IP address 130.115.144.11
61will make an TFTP request for `8273900B'.  Normally, this file is a
62symbolic link to the NetBSD/sun3 "netboot" program, which should be
63located in a place where the TFTP daemon can find it (remember, many
64TFTP daemons run in a chroot'ed environment).  The netboot program
65may be found in the install directory of this distribution.
66
67The netboot program will query a bootparamd server to find the
68NFS server address and path name for its root, and then load a
69kernel from that location.  The server should have a copy of the
70netbsd-rd kernel in the root area for your client (no other files
71are needed in the client root) and /etc/bootparams on the server
72should have an entry for your client and its root directory.
73The client will need access to the miniroot image, which can be
74provided using NFS or remote shell.  If using NFS, miniroot.gz
75must be expanded on the server, because there is no gzip program
76in the RAMDISK image.  The unzipped miniroot takes 8MB of space.
77
78If you will be installing NetBSD on several clients, it may be useful
79to know that you can use a single NFS root for all the clients as long
80as they only use the netbsd-rd kernel.  There will be no conflict
81between clients because the RAM-disk kernel will not use the NFS root.
82No swap file is needed; the RAM-disk kernel does not use that either.
83
84* Install/Upgrade from CD-ROM:
85
86This method requires that you boot from another device (i.e. tape
87or network, as described above).  You may need to make a boot tape
88on another machine using the files provided on the CD-ROM.  Once
89you have booted netbsd-rd (the RAM-disk kernel) and loaded the
90miniroot, you can load any of the distribution sets directly from
91the CD-ROM.  The "install" program in the miniroot automates the
92work required to mount the CD-ROM and extract the files.
93
94* Install/Upgrade via FTP:
95
96This method requires that you boot from another device (i.e. tape
97or network, as described above).  You may need to make a boot tape
98on another machine using the files in .../install (which you get
99via FTP).  Once you have booted netbsd-rd (the RAM-disk kernel)
100and loaded the miniroot, you can load any of the distribution sets
101over the net using FTP.  The "install" program in the miniroot
102automates the work required to configure the network interface and
103transfer the files.
104
105The preparations for this installation/upgrade method are easy; all
106you make sure that there's some FTP site from which you can retrieve
107the NetBSD distribution when you're about to install or upgrade.  You
108need to know the numeric IP address of that site, and, if it's not on
109a network directly connected to the machine on which you're installing
110or upgrading NetBSD, you need to know the numeric IP address of the
111router closest to the NetBSD machine.  Finally, you need to know the
112numeric IP address of the NetBSD machine itself.
113