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