installation-guide-amd64 20160121ubuntu4 / usr / share / doc / installation-guide-amd64 / en / ch04s05.html

This file is indexed.

/usr/share/doc/installation-guide-amd64/en/ch04s05.html is in installation-guide-amd64 20160121ubuntu4.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below. 

  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
339
340
341
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>4.5. Preparing Files for TFTP Net Booting</title>
<link rel="stylesheet" type="text/css" href="install.css">
<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="index.html" title="Ubuntu Installation Guide">
<link rel="up" href="ch04.html" title="Chapter 4. Obtaining System Installation Media">
<link rel="prev" href="ch04s04.html" title="4.4. Preparing Files for Hard Disk Booting">
<link rel="next" href="ch04s06.html" title="4.6. Automatic Installation">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<div class="navheader">
<table width="100%" summary="Navigation header">
<tr><th colspan="3" align="center">4.5. Preparing Files for TFTP Net Booting</th></tr>
<tr>
<td width="20%" align="left">
<a accesskey="p" href="ch04s04.html"><img src="images/prev.png" alt="Prev"></a> </td>
<th width="60%" align="center">Chapter 4. Obtaining System Installation Media</th>
<td width="20%" align="right"> <a accesskey="n" href="ch04s06.html"><img src="images/next.png" alt="Next"></a>
</td>
</tr>
</table>
<hr>
</div>
<div class="sect1">
<div class="titlepage"><div><div><h2 class="title">
<a name="install-tftp"></a>4.5. Preparing Files for TFTP Net Booting</h2></div></div></div>
<p>

If your machine is connected to a local area network, you may be able
to boot it over the network from another machine, using TFTP. If you
intend to boot the installation system from another machine, the
boot files will need to be placed in specific locations on that machine,
and the machine configured to support booting of your specific machine.

</p>
<p>

You need to set up a TFTP server, and for many machines a DHCP 
server<span class="phrase">, or BOOTP
server</span>.

</p>
<p>



<span class="phrase">BOOTP is an IP protocol that
informs a computer of its IP address and where on the network to obtain
a boot image.</span>

The DHCP (Dynamic Host Configuration Protocol) is a more flexible,
backwards-compatible extension of BOOTP.
Some systems can only be configured via DHCP.

</p>
<p>

The Trivial File Transfer Protocol (TFTP) is used to serve the boot
image to the client.  Theoretically, any server, on any platform,
which implements these protocols, may be used.  In the examples in
this section, we shall provide commands for SunOS 4.x, SunOS 5.x
(a.k.a. Solaris), and GNU/Linux.

</p>
<div class="note"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.png"></td>
<th align="left">Note</th>
</tr>
<tr><td align="left" valign="top"><p>

For an Ubuntu or Debian server we recommend
<code class="classname">tftpd-hpa</code>.
It's written by the same author as the <code class="classname">syslinux</code>
bootloader and is therefore least likely to cause issues.
A good alternative is <code class="classname">atftpd</code>.

</p></td></tr>
</table></div>
<p>

</p>
<div class="sect2">
<div class="titlepage"><div><div><h3 class="title">
<a name="dhcpd"></a>4.5.1. Setting up a DHCP server</h3></div></div></div>
<p>

One free software DHCP server is ISC <span class="command"><strong>dhcpd</strong></span>.
For Ubuntu, the <code class="classname">isc-dhcp-server</code> package is
recommended.  Here is a sample configuration file for it (see
<code class="filename">/etc/dhcp/dhcpd.conf</code>):

</p>
<div class="informalexample"><pre class="screen">
option domain-name "example.com";
option domain-name-servers ns1.example.com;
option subnet-mask 255.255.255.0;
default-lease-time 600;
max-lease-time 7200;
server-name "servername";

subnet 192.168.1.0 netmask 255.255.255.0 {
  range 192.168.1.200 192.168.1.253;
  option routers 192.168.1.1;
}

host clientname {
  filename "/tftpboot.img";
  server-name "servername";
  next-server servername;
  hardware ethernet 01:23:45:67:89:AB;
  fixed-address 192.168.1.90;
}
</pre></div>
<p>

</p>
<p>

In this example, there is one server
<em class="replaceable"><code>servername</code></em> which performs all of the work
of DHCP server, TFTP server, and network gateway.  You will almost
certainly need to change the domain-name options, as well as the
server name and client hardware address.  The
<em class="replaceable"><code>filename</code></em> option should be the name of the
file which will be retrieved via TFTP.

</p>
<p>

After you have edited the <span class="command"><strong>dhcpd</strong></span> configuration file,
restart it with <strong class="userinput"><code>/etc/init.d/isc-dhcp-server restart</code></strong>.

</p>
<div class="sect3">
<div class="titlepage"><div><div><h4 class="title">
<a name="idm913"></a>4.5.1.1. Enabling PXE Booting in the DHCP configuration</h4></div></div></div>
<p>
Here is another example for a <code class="filename">dhcp.conf</code> using the
Pre-boot Execution Environment (PXE) method of TFTP.

</p>
<div class="informalexample"><pre class="screen">
option domain-name "example.com";

default-lease-time 600;
max-lease-time 7200;

allow booting;
allow bootp;

# The next paragraph needs to be modified to fit your case
subnet 192.168.1.0 netmask 255.255.255.0 {
  range 192.168.1.200 192.168.1.253;
  option broadcast-address 192.168.1.255;
# the gateway address which can be different
# (access to the internet for instance)
  option routers 192.168.1.1;
# indicate the dns you want to use
  option domain-name-servers 192.168.1.3;
}

group {
  next-server 192.168.1.3;
  host tftpclient {
# tftp client hardware address
  hardware ethernet  00:10:DC:27:6C:15;
  filename "pxelinux.0";
 }
}
</pre></div>
<p>

Note that for PXE booting, the client filename <code class="filename">pxelinux.0</code>
is a boot loader, not a kernel image (see <a class="xref" href="ch04s05.html#tftp-images" title="4.5.4. Move TFTP Images Into Place">Section 4.5.4, “Move TFTP Images Into Place”</a>
below).

</p>
</div>
</div>
<div class="sect2">
<div class="titlepage"><div><div><h3 class="title">
<a name="tftp-bootp"></a>4.5.2. Setting up a BOOTP server</h3></div></div></div>
<p>

There are two BOOTP servers available for GNU/Linux. The first is CMU
<span class="command"><strong>bootpd</strong></span>. The other is actually a DHCP server: ISC
<span class="command"><strong>dhcpd</strong></span>. In Ubuntu these are contained in the
<code class="classname">bootp</code> and <code class="classname">isc-dhcp-server</code>
packages respectively.

</p>
<p>

To use CMU <span class="command"><strong>bootpd</strong></span>, you must first uncomment (or
add) the relevant line in <code class="filename">/etc/inetd.conf</code>.  On
Debian or Ubuntu, you can run <strong class="userinput"><code>update-inetd --enable
bootps</code></strong>, then <strong class="userinput"><code>/etc/init.d/inetd
reload</code></strong> to do so. Just in case your BOOTP server does not
run Debian or Ubuntu, the line in question should look like:

</p>
<div class="informalexample"><pre class="screen">
bootps  dgram  udp  wait  root  /usr/sbin/bootpd  bootpd -i -t 120
</pre></div>
<p>

Now, you must create an <code class="filename">/etc/bootptab</code> file.  This
has the same sort of familiar and cryptic format as the good old BSD
<code class="filename">printcap</code>, <code class="filename">termcap</code>, and
<code class="filename">disktab</code> files.  See the
<code class="filename">bootptab</code> manual page for more information.  For
CMU <span class="command"><strong>bootpd</strong></span>, you will need to know the hardware
(MAC) address of the client.  Here is an example
<code class="filename">/etc/bootptab</code>:

</p>
<div class="informalexample"><pre class="screen">
client:\
  hd=/tftpboot:\
  bf=tftpboot.img:\
  ip=192.168.1.90:\
  sm=255.255.255.0:\
  sa=192.168.1.1:\
  ha=0123456789AB:
</pre></div>
<p>

You will need to change at least the <span class="quote">“<span class="quote">ha</span>”</span> option, which
specifies the hardware address of the client.  The <span class="quote">“<span class="quote">bf</span>”</span>
option specifies the file a client should retrieve via TFTP; see
<a class="xref" href="ch04s05.html#tftp-images" title="4.5.4. Move TFTP Images Into Place">Section 4.5.4, “Move TFTP Images Into Place”</a> for more details.



</p>
<p>

By contrast, setting up BOOTP with ISC <span class="command"><strong>dhcpd</strong></span> is
really easy, because it treats BOOTP clients as a moderately special
case of DHCP clients.  Some architectures require a complex
configuration for booting clients via BOOTP.  If yours is one of
those, read the section <a class="xref" href="ch04s05.html#dhcpd" title="4.5.1. Setting up a DHCP server">Section 4.5.1, “Setting up a DHCP server”</a>.  Otherwise you
will probably be able to get away with simply adding the
<strong class="userinput"><code>allow bootp</code></strong> directive to the configuration
block for the subnet containing the client in
<code class="filename">/etc/dhcp/dhcpd.conf</code>, and restart
<span class="command"><strong>dhcpd</strong></span> with <strong class="userinput"><code>/etc/init.d/isc-dhcp-server
restart</code></strong>.

</p>
</div>
<div class="sect2">
<div class="titlepage"><div><div><h3 class="title">
<a name="tftpd"></a>4.5.3. Enabling the TFTP Server</h3></div></div></div>
<p>

To get the TFTP server ready to go, you should first make sure that
<span class="command"><strong>tftpd</strong></span> is enabled.

</p>
<p>

In the case of <code class="classname">tftpd-hpa</code> there are two ways the
service can be run. It can be started on demand by the system's
<code class="classname">inetd</code> daemon, or it can be set up to run as an
independent daemon. Which of these methods is used is selected when the
package is installed and can be changed by reconfiguring the package.

</p>
<div class="note"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.png"></td>
<th align="left">Note</th>
</tr>
<tr><td align="left" valign="top"><p>

Historically, TFTP servers used <code class="filename">/tftpboot</code> as directory
to serve images from. However, Ubuntu packages may use other directories
to comply with the <a class="ulink" href="http://www.pathname.com/fhs/" target="_top">Filesystem Hierarchy
Standard</a>. For example, <code class="classname">tftpd-hpa</code> by default
uses <code class="filename">/srv/tftp</code>. You may have to adjust the
configuration examples in this section accordingly.

</p></td></tr>
</table></div>
<p>

All <span class="command"><strong>in.tftpd</strong></span> alternatives available in Ubuntu should
log TFTP requests to the system logs by default. Some of them support a
<strong class="userinput"><code>-v</code></strong> argument to increase verbosity.
It is recommended to check these log messages in case of boot problems
as they are a good starting point for diagnosing the cause of errors.

</p>
</div>
<div class="sect2">
<div class="titlepage"><div><div><h3 class="title">
<a name="tftp-images"></a>4.5.4. Move TFTP Images Into Place</h3></div></div></div>
<p>

Next, place the TFTP boot image you need, as found in
<a class="xref" href="ch04s02.html#where-files" title="4.2.1. Where to Find Installation Images">Section 4.2.1, “Where to Find Installation Images”</a>, in the <span class="command"><strong>tftpd</strong></span>
boot image directory.  You may have to make a link from that
file to the file which <span class="command"><strong>tftpd</strong></span> will use for booting a
particular client.  Unfortunately, the file name is determined by the
TFTP client, and there are no strong standards.

</p>
<p>

For PXE booting, everything you should need is set up in the
<code class="filename">netboot/netboot.tar.gz</code> tarball. Simply extract this
tarball into the <span class="command"><strong>tftpd</strong></span> boot image directory. Make sure
your dhcp server is configured to pass <code class="filename">pxelinux.0</code>
to <span class="command"><strong>tftpd</strong></span> as the filename to boot.

</p>
</div>
</div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left">
<a accesskey="p" href="ch04s04.html"><img src="images/prev.png" alt="Prev"></a> </td>
<td width="20%" align="center"><a accesskey="u" href="ch04.html"><img src="images/up.png" alt="Up"></a></td>
<td width="40%" align="right"> <a accesskey="n" href="ch04s06.html"><img src="images/next.png" alt="Next"></a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">4.4. Preparing Files for Hard Disk Booting </td>
<td width="20%" align="center"><a accesskey="h" href="index.html"><img src="images/home.png" alt="Home"></a></td>
<td width="40%" align="right" valign="top"> 4.6. Automatic Installation</td>
</tr>
</table>
</div>
</body>
</html>

APT Browse - Built by Thomas Orozco.