| blob | eba84f928eae676248c95f9923158d1cfe364d73 |
1 .\" $NetBSD: xfer,v 1.16 2006/11/25 22:53:35 mishka Exp $
2 .
3 Installation is supported from several media types, including:
4 .(bullet
5 Tape
6 .It
7 NFS
8 .It
9 CD-ROM
10 .It
11 FTP
12 .bullet)
13 .Pp
14 Note that installing on a
15 .Sq bare
16 machine requires either a bootable
17 tape drive or an ethernet to a compatible NFS server.
18 MVME147 may also need to be booted over an RS232 connection.
19 .Pp
20 The procedure for transferring the distribution sets onto installation
21 media depends on the type of media.
22 Instructions for each type of media are given below.
23 .Pp
24 In order to create installation media, you will need all the files and
25 subdirectories in these two directories:
26 .Pp
27 .(item -offset indent
28 .Pa \&.../NetBSD-\*V/\*M/installation
29 .It
30 .Pa \&.../NetBSD-\*V/\*M/binary
31 .item)
32 .
33 .Ss2 Creating boot/install tapes
34 .
35 Installing from tape is the simplest method of all.
36 This method uses two tapes, one containing a bootable ramdisk and miniroot,
37 the other containing the installation sets.
38 .Pp
39 The boot tape is created as follows:
40 .Pp
41 .Dl # Ic "cd .../NetBSD-\*V/\*M/installation"
42 .Dl # Ic "set T = /dev/nrst0"
43 .Dl # Ic "mt -f $T rewind"
44 .Dl # Ic "dd if=tapeimage/stboot of=$T obs=8k conv=osync"
45 .Dl # Ic "dd if=tapeimage/bootst of=$T obs=8k conv=osync"
46 .Dl # Ic "gzip -dc tapeimage/netbsd-RAMDISK.gz | dd of=$T obs=8k conv=osync"
47 .Dl # Ic "gzip -dc miniroot/miniroot.fs.gz | dd of=$T obs=8k conv=osync"
48 .Dl # Ic "mt -f $T rewind"
49 .Pp
50 The installation set tape is created as follows:
51 .Pp
52 .Dl # Ic "cd .../NetBSD-\*V/\*M/binary/sets"
53 .Dl # Ic "set T = /dev/nrst0"
54 .Dl # Ic "mt -f $T rewind"
55 .Dl # Ic "for f in base etc comp games man misc text; do"
56 .Dl Ic "\ \ \ \ gzip -d \*[Lt] $f.tgz | dd of=$T bs=8k conv=osync"
57 .Dl # Ic "done"
58 .Dl # Ic "mt -f $T rewind"
59 .Pp
60 If the tape does not work as expected, you may need to explicitly
61 set the EOF mark at the end of each tape segment.
62 Consult the tape-related manual pages on the system where the tapes
63 are created for more details.
64 .
65 .Ss2 Boot/Install from NFS server
66 .
67 If your machine has a disk and network connection, but no tape drive,
68 it may be convenient for you to install
69 .Nx
70 over the network.
71 This involves temporarily booting your machine over NFS, just long enough
72 so you can initialize its disk.
73 This method requires that you have access to an NFS server on your
74 network so you can configure it to support diskless boot for your machine.
75 Configuring the NFS server is normally a task for a system administrator,
76 and is not trivial.
77 .Pp
78 If you are using a
79 .Nx
80 system as the boot-server, have a look at
81 the
82 .Xr diskless 8
83 manual page for guidelines on how to proceed with this.
84 If the server runs another operating system, consult the
85 documentation that came with it (i.e.
86 .Xr add_client 8
87 on
88 .Tn SunOS ) .
89 .Pp
90 Booting an MVME147 from ethernet is not possible without first downloading
91 a small bootstrap program (sboot) via RS232.
92 See the section entitled
93 .Sx "Installing from NFS"
94 for details on how to accomplish this.
95 .Pp
96 sboot expects to be able to download a second stage bootstrap
97 program via TFTP after having acquired its IP address through RARP
98 It will look for a filename derived from the machine's IP address
99 expressed in hexadecimal, with an extension of
100 .Sq Pa .147 .
101 For example, an MVME147 with IP address 130.115.144.11 will make an TFTP
102 request for
103 .Pa 8273900B.147 .
104 Normally, this file is just a symbolic link to the
105 .Nx*M
106 .Pa netboot
107 program, which should be located in a place
108 where the TFTP daemon can find it (remember, many TFTP daemons run in
109 a chroot'ed environment).
110 The netboot program may be found in the install directory of this distribution.
111 .Pp
112 The
113 .Tn MVME162
114 ,
115 .Tn MVME167
116 ,
117 .Tn MVME172
118 ,
119 and
120 .Tn MVME177
121 boot ROMs have code builtin to boot over ethernet from a TFTP server.
122 You should configure it to download the same
123 .Pa netboot
124 program as is used for
125 .Tn MVME147 .
126 .Pp
127 The netboot program will query a bootparamd server to find the NFS
128 server address and path name for its root, and then load a kernel from
129 that location.
130 The server should have a copy of the netbsd-RAMDISK kernel in
131 the root area for your client (no other files are needed in the client
132 root, although it might be a convenient place to put the uncompressed
133 miniroot image) and
134 .Pa /etc/bootparams
135 on the server should have an entry for your client and its root directory.
136 Note that you should rename the
137 .Pa netbsd-RAMDISK
138 kernel to just
139 .Pa netbsd
140 in the client's root directory before trying to netboot the client.
141 .Pp
142 The client will need access to the miniroot image, which can be
143 provided using NFS or remote shell.
144 If using NFS, miniroot.fs.gz should be expanded on the server,
145 because doing so from the RAMDISK shell is not so easy.
146 The unzipped miniroot takes about 7.5 MB of space.
147 .Pp
148 If you will be installing
149 .Nx
150 on several clients, it may be useful
151 to know that you can use a single NFS root for all the clients as long
152 as they only use the netbsd-RAMDISK kernel.
153 There will be no conflict between clients because the RAM-disk kernel
154 will not use the NFS root.
155 No swap file is needed; the RAM-disk kernel does not use that either.
156 .
157 .Ss2 Install/Upgrade from CD-ROM
158 .
159 This method requires that you boot from another device
160 (i.e. tape or network, as described above).
161 You may need to make a boot tape on another machine using the files
162 provided on the CD-ROM.
163 Once you have booted netbsd-RAMDISK (the RAMDISK kernel) and loaded the
164 miniroot, you can load any of the distribution sets directly from the CD-ROM.
165 The
166 .Ic install
167 program in the miniroot automates the
168 work required to mount the CD-ROM and extract the files.
169 .
170 .Ss2 Install/Upgrade via FTP
171 .
172 This method requires that you boot from another device
173 (i.e. tape or network, as described above).
174 You may need to make a boot tape on another machine using the files
175 in .../install (which you get via FTP).
176 Once you have booted netbsd-RAMDISK (the RAM-disk kernel) and loaded the
177 miniroot, you can load any of the distribution sets over the net using FTP.
178 The
179 .Ic install
180 program in the miniroot
181 automates the work required to configure the network interface and
182 transfer the files.
183 .Pp
184 This method, of course, requires network access to an FTP server.
185 This might be a local system, or it might even be ftp.NetBSD.org itself.
186 If you wish to use ftp.NetBSD.org as your FTP file
187 server, you may want to keep the following information handy:
188 .Pp
189 .(disp
190 No IP Address: ftp.NetBSD.org
191 Login: anonymous
192 Password: \*[Lt]your e-mail address\*[Gt]
193 Server path: /pub/NetBSD/NetBSD-\*V/\*M/binary
194 .disp)
195 .(Note
196 If you're not using a nameserver during installation,
197 you might find 204.152.184.75 handy; it's the IP address of
198 ftp.NetBSD.org as of October, 2000.
199 .Note)