/[gentoo]/xml/htdocs/doc/en/gentoo-sparc-netboot-howto.xml
Gentoo

Diff of /xml/htdocs/doc/en/gentoo-sparc-netboot-howto.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.11 Revision 1.12
1<?xml version='1.0' encoding="UTF-8"?> 1<?xml version='1.0' encoding="UTF-8"?>
2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-sparc-netboot-howto.xml,v 1.11 2009/12/14 21:35:05 nightmorph Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-sparc-netboot-howto.xml,v 1.12 2010/03/03 01:37:41 nightmorph Exp $ -->
4 4
5<guide> 5<guide>
6<title>Gentoo Linux based Netboot HOWTO</title> 6<title>Gentoo Linux based Netboot HOWTO</title>
7 7
8<author title="SPARC Developer"> 8<author title="SPARC Developer">
9 <mail link="weeve"/> 9 <mail link="weeve"/>
10</author>
11<author title="Editor">
12 <mail link="nightmorph"/>
10</author> 13</author>
11 14
12<abstract> 15<abstract>
13Guide for setting up a netboot server for use with the Gentoo/SPARC netboot 16Guide for setting up a netboot server for use with the Gentoo/SPARC netboot
14installation images. 17installation images.
16 19
17<!-- The content of this document is licensed under the CC-BY-SA license --> 20<!-- The content of this document is licensed under the CC-BY-SA license -->
18<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> 21<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
19<license/> 22<license/>
20 23
21<version>1.3</version> 24<version>1.4</version>
22<date>2009-12-14</date> 25<date>2010-03-02</date>
23 26
24<chapter> 27<chapter>
25<title>Introduction</title> 28<title>Introduction</title>
26<section> 29<section>
27<body> 30<body>
53 Client machine sends out a reverse ARP (RARP) request to get an IP address 56 Client machine sends out a reverse ARP (RARP) request to get an IP address
54 </li> 57 </li>
55 <li>A server machine returns a response to the client with the IP address</li> 58 <li>A server machine returns a response to the client with the IP address</li>
56 <li> 59 <li>
57 The client then attempts to download a boot image from the RARP server 60 The client then attempts to download a boot image from the RARP server
58 using the tftp protocol 61 using the TFTP protocol
59 </li> 62 </li>
60 <li>Once the image is downloaded, the netboot client then boots the image</li> 63 <li>Once the image is downloaded, the netboot client then boots the image</li>
61</ol> 64</ol>
62 65
63<p> 66<p>
64Based on this overview, we will need to install software for a reverse ARP 67Based on this overview, we will need to install software for a reverse ARP
65daemon and a tftp daemon. 68daemon and a TFTP daemon.
66</p> 69</p>
67 70
68</body> 71</body>
69</section> 72</section>
70</chapter> 73</chapter>
75<title>The Reverse ARP Daemon</title> 78<title>The Reverse ARP Daemon</title>
76<body> 79<body>
77 80
78<p> 81<p>
79Currently, there are two choices for a reverse ARP daemon. They are 82Currently, there are two choices for a reverse ARP daemon. They are
80net-misc/iputils (installed as part of the system profile) and net-misc/rarpd. 83<c>net-misc/iputils</c> (installed as part of the system profile) and
84<c>net-misc/rarpd</c>.
81</p> 85</p>
82 86
83<note> 87<note>
84Installing net-misc/rarpd will overwrite the rarpd and rarpd manpage from 88Installing <c>net-misc/rarpd</c> will overwrite the <c>rarpd</c> and
85net-misc/iputils 89<c>rarpd</c> manpage from <c>net-misc/iputils</c>.
86</note> 90</note>
87 91
88<p> 92<p>
89<b>Setting up common rarpd elements</b>: <path>/etc/ethers</path> 93<b>Setting up common rarpd elements</b>: <path>/etc/ethers</path>
90</p> 94</p>
91 95
92<p> 96<p>
93No matter which rarpd you choose to use, you will need to setup the 97No matter which <c>rarpd</c> you choose to use, you will need to setup the
94<path>/etc/ethers</path> file. This file indicates which hosts rarpd should 98<path>/etc/ethers</path> file. This file indicates which hosts <c>rarpd</c>
95respond to when a request is seen, and what address to reply with. 99should respond to when a request is seen, and what address to reply with.
96</p> 100</p>
97 101
98<p> 102<p>
99The format of <path>/etc/ethers</path> is the MAC address of the NIC the 103The format of <path>/etc/ethers</path> is the MAC address of the NIC the
100machine will be netbooting and its hostname. Whitespace delimits the MAC 104machine will be netbooting and its hostname. Whitespace delimits the MAC
111to omit the first 0 (i.e. 08:00:20:77:1f:3e becomes 8:0:20:77:1f:3e). 115to omit the first 0 (i.e. 08:00:20:77:1f:3e becomes 8:0:20:77:1f:3e).
112</note> 116</note>
113 117
114<p> 118<p>
115If you desire to add additional hosts to <path>/etc/ethers</path>, you do not 119If you desire to add additional hosts to <path>/etc/ethers</path>, you do not
116need to restart the rarpd services as the file is checked each time a request 120need to restart the <c>rarpd</c> services as the file is checked each time a
117is received. 121request is received.
118</p> 122</p>
119 123
120<p> 124<p>
121<b>Resolving hostnames</b>: <path>/etc/hosts</path> 125<b>Resolving hostnames</b>: <path>/etc/hosts</path>
122</p> 126</p>
162<p> 166<p>
163<b>Setting up net-misc/iputils rarpd</b> 167<b>Setting up net-misc/iputils rarpd</b>
164</p> 168</p>
165 169
166<p> 170<p>
167First, we will need to determine the options to use for rarpd. While there are 171First, we will need to determine the options to use for <c>rarpd</c>. While
168more options than we'll cover here, these options should get you started As 172there are more options than we'll cover here, these options should get you
169there is currently no init.d script for net-misc/iputils version of rarpd, an 173started As there is currently no <path>init.d</path> script for the
170entry will need to be added to <path>/etc/conf.d/local.start</path> if you want 174<c>net-misc/iputils</c> version of <c>rarpd</c>, an entry will need to be added
175to <path>/etc/conf.d/local.start</path> if you want to enable <c>rarpd</c>
171to enable rarpd servies at boot time. A sample entry is as follows; 176services at boot time. A sample entry is as follows:
172</p> 177</p>
173 178
174<pre caption="/etc/conf.d/local.start"> 179<pre caption="/etc/conf.d/local.start">
175/usr/sbin/rarpd -v -e eth0 180/usr/sbin/rarpd -v -e eth0
176</pre> 181</pre>
177 182
178<p> 183<p>
179An explanation of the above rarpd options (as taken from the man page): 184An explanation of the above <c>rarpd</c> options (as taken from the man page):
180</p> 185</p>
181 186
182<ul> 187<ul>
183 <li>-v Be verbose</li> 188 <li><c>-v</c> Be verbose</li>
184 <li>
185 -e Do not check for the presence of a boot image, reply if MAC address
186 resolves to a valid IP address using /etc/ethers database and DNS
187 </li> 189 <li>
190 <c>-e</c> Do not check for the presence of a boot image, reply if MAC
191 address resolves to a valid IP address using <path>/etc/ethers</path>
192 database and DNS
193 </li>
188 <li>eth0 represents the interface rarpd should bind to</li> 194 <li>eth0 represents the interface <c>rarpd</c> should bind to</li>
189</ul> 195</ul>
190 196
191<p> 197<p>
192For more options, consult the section 8 man page on rarpd. 198For more options, consult <c>man 8 rarpd</c>.
193</p> 199</p>
194 200
195<p> 201<p>
196<b>Setting up net-misc/rarpd</b> 202<b>Setting up net-misc/rarpd</b>
197</p> 203</p>
198 204
199<p> 205<p>
200Firstly, we'll need to install rarpd with the following command: 206Firstly, we'll need to install <c>rarpd</c> with the following command:
201</p> 207</p>
202 208
203<pre caption="Installing rarpd"> 209<pre caption="Installing rarpd">
204# <i>emerge net-misc/rarpd</i> 210# <i>emerge net-misc/rarpd</i>
205</pre> 211</pre>
206 212
207<p> 213<p>
208Next, options for rarpd will need to be set in <path>/etc/conf.d/rarpd</path>. 214Next, options for <c>rarpd</c> will need to be set in
209For an equivalent configuration as the one used above for net-misc/iputils 215<path>/etc/conf.d/rarpd</path>. For an equivalent configuration as the one used
216above for the <c>net-misc/iputils</c> <c>rarpd</c>, adjust
210rarpd, adjust <path>/etc/conf.d/rarpd</path> to look like the following 217<path>/etc/conf.d/rarpd</path> to look like the following
211</p> 218</p>
212 219
213<pre caption="/etc/conf.d/rarpd"> 220<pre caption="/etc/conf.d/rarpd">
214RARPD_OPTS="-v -i eth0" 221RARPD_OPTS="-v -i eth0"
215</pre> 222</pre>
221<ul> 228<ul>
222 <li> 229 <li>
223 <c>-v</c> Be verbose. Show requests which the daemon is responding to 230 <c>-v</c> Be verbose. Show requests which the daemon is responding to
224 </li> 231 </li>
225 <li> 232 <li>
226 <c>-i</c> Bind to the named interface. By default rarpd binds to the 233 <c>-i</c> Bind to the named interface. By default <c>rarpd</c> binds to the
227 default interface for the local system type, if available 234 default interface for the local system type, if available
228 </li> 235 </li>
229</ul> 236</ul>
230 237
231<p> 238<p>
232For more options, consult the section 8 man page on rarpd and rarpd --help. 239For more options, consult <c>man 8 rarpd</c> and <c>rarpd --help</c>.
233</p> 240</p>
234 241
235</body> 242</body>
236</section> 243</section>
237<section> 244<section>
238<title>The tftpd Daemon</title> 245<title>The tftpd Daemon</title>
239<body> 246<body>
240 247
241<p> 248<p>
242Here there are three options for a tftp daemon, net-misc/atftp, 249Here there are three options for a TFTP daemon, <c>net-misc/atftp</c>,
243net-misc/netkit-tftp and net-misc/tftp-hpa. You only need to install one of the 250<c>net-misc/netkit-tftp</c> and <c>net-misc/tftp-hpa</c>. You only need to
244tftp daemons for proper operation. 251install one of the TFTP daemons for proper operation.
245</p> 252</p>
246 253
247<p> 254<p>
248<b>Setting up common tftpd elements</b> 255<b>Setting up common tftpd elements</b>
249</p> 256</p>
250 257
251<p> 258<p>
252Each tftp daemon will need a directory from which to serve files to tftp 259Each TFTP daemon will need a directory from which to serve files to tftp
253clients. The directory we will use for this howto will be /tftpboot. This will 260clients. The directory we will use for this howto will be
254appear as the root (<path>/</path>) directory to the clients when requests are 261<path>/tftpboot</path>. This will appear as the root (<path>/</path>) directory
255received. Additionally, we'll setup the system to run the tftp daemon with the 262to the clients when requests are received. Additionally, we'll setup the system
256user and group nobody. 263to run the TFTP daemon with the user and group <c>nobody</c>.
257</p> 264</p>
258 265
259<p> 266<p>
260If the directory you have chosen does not currently exist, it will need to be 267If the directory you have chosen does not currently exist, it will need to be
261created with the mkdir command. The command for the example /tftpboot is; 268created with the <c>mkdir</c> command. The command for the example
269<path>/tftpboot</path> is:
262</p> 270</p>
263 271
264<pre caption="Creating /tftpboot"> 272<pre caption="Creating /tftpboot">
265# <i>/bin/mkdir /tftpboot</i> 273# <i>/bin/mkdir /tftpboot</i>
266</pre> 274</pre>
267 275
268<p> 276<p>
269Then we will need to change the owner of <path>/tftpboot</path> so that it is 277Then we will need to change the owner of <path>/tftpboot</path> so that it is
270owned by user nobody and group nobody; 278owned by user nobody and group <c>nobody</c>:
271</p> 279</p>
272 280
273<pre caption="Changing ownership"> 281<pre caption="Changing ownership">
274# <i>chown nobody:nobody /tftpboot</i> 282# <i>chown nobody:nobody /tftpboot</i>
275</pre> 283</pre>
279<section> 287<section>
280<title>The atftp Daemon</title> 288<title>The atftp Daemon</title>
281<body> 289<body>
282 290
283<p> 291<p>
284First, install the net-misc/atftp package as follows; 292First, install the <c>net-misc/atftp</c> package as follows;
285</p> 293</p>
286 294
287<pre caption="Installing atftp"> 295<pre caption="Installing atftp">
288# <i>emerge net-misc/atftp</i> 296# <i>emerge net-misc/atftp</i>
289</pre> 297</pre>
290 298
291<p> 299<p>
292After the net-misc/atftp package has been installed, it will need to be 300After the <c>net-misc/atftp</c> package has been installed, it will need to be
293configured. If tftpd services are desired at boot time, an entry to 301configured. If tftpd services are desired at boot time, an entry to
294<path>/etc/conf.d/local.start</path> will need to be added as atftp has no 302<path>/etc/conf.d/local.start</path> will need to be added as <c>atftp</c> has
295init.d, inetd or xinetd scripts of its own. If you want to use inetd or xinetd 303no <path>init.d</path>, <c>inetd</c> or <c>xinetd</c> scripts of its own. If you
296for controlling the tftpd service, please see their respective man pages. 304want to use <c>inetd</c> or <c>xinetd</c> for controlling the tftpd service,
297</p> 305please see their respective man pages.
298
299<p> 306</p>
300Below is an example entry for atftpd in <path>/etc/conf.d/local.start</path>; 307
308<p>
309Below is an example entry for <c>atftpd</c> in
310<path>/etc/conf.d/local.start</path>.
301</p> 311</p>
302 312
303<pre caption="/etc/conf.d/local.start"> 313<pre caption="/etc/conf.d/local.start">
304/usr/sbin/in.tftpd -v --daemon /tftpboot 314/usr/sbin/in.tftpd -v --daemon /tftpboot
305</pre> 315</pre>
306 316
307<p> 317<p>
308An explanation of the above rarpd options (as taken from the man page); 318An explanation of the above <c>rarpd</c> options (as taken from the man page);
309</p> 319</p>
310 320
311<ul> 321<ul>
312 <li> 322 <li>
313 <c>-v</c> Increase or set the logging level. No args will increase by one 323 <c>-v</c> Increase or set the logging level. No args will increase by one
319 started by inetd. 329 started by inetd.
320 </li> 330 </li>
321</ul> 331</ul>
322 332
323<p> 333<p>
324For more options, consult the section 8 man page on atftpd. 334For more options, consult <c>man 8 atftpd</c>.
325</p> 335</p>
326 336
327</body> 337</body>
328</section> 338</section>
329<section> 339<section>
330<title>The netkit-tftp Daemon</title> 340<title>The netkit-tftp Daemon</title>
331<body> 341<body>
332 342
333<p> 343<p>
334First, install the net-misc/netkit-tftp package as follows; 344First, install the <c>net-misc/netkit-tftp</c> package:
335</p> 345</p>
336 346
337<pre caption="Installing netkit-tftp"> 347<pre caption="Installing netkit-tftp">
338# <i>emerge net-misc/netkit-tftp</i> 348# <i>emerge net-misc/netkit-tftp</i>
339</pre> 349</pre>
340 350
341<p> 351<p>
342Secondly, install sys-apps/xinetd if it is not currently present; After the 352Second, install <c>sys-apps/xinetd</c> if it is not currently present. After
343net-misc/netkit-tftp and sys-apps/xinetd packages have been installed, 353the <c>net-misc/netkit-tftp</c> and <c>sys-apps/xinetd</c> packages have been
344netkit-tftp will need to be configured. netkit-tftp needs to be run from 354installed, <c>netkit-tftp</c> will need to be configured. <c>netkit-tftp</c>
345xinetd, however it does not provide example scripts of its own. A sample xinetd 355needs to be run from <c>xinetd</c>, however it does not provide example scripts
346file is provided below; 356of its own. A sample <c>xinetd</c> file is provided below:
347</p> 357</p>
348 358
349<pre caption="Sample /etc/xinetd.d/tftp file"> 359<pre caption="Sample /etc/xinetd.d/tftp file">
350service tftp 360service tftp
351{ 361{
361 disable = no 371 disable = no
362} 372}
363</pre> 373</pre>
364 374
365<note> 375<note>
366This sample xinetd configuration file for tftp uses the line "disable = no", 376This sample <c>xinetd</c> configuration file for tftp uses the line <c>disable =
367which enables the service by default. This is opposite of the default way 377no</c>, which enables the service by default. This is opposite of the default
368packages in Gentoo provide their respective xinetd configuration files, which 378way packages in Gentoo provide their respective <c>xinetd</c> configuration
369have disable set to yes. 379files, which have <c>disable</c> set to <c>yes</c>.
370</note> 380</note>
371 381
372<p> 382<p>
373An explanation of the above options which can be changed; 383An explanation of the above options which can be changed:
374user user in.tftpd requests are handled as
375group group in.tftpd requests are handled as
376server_args root directory for tftp daemon to serve files from
377only_from tells xinetd what hosts to allow tftp connections from
378</p>
379
380<p> 384</p>
385
386<ul>
387 <li><b>user</b>: the user in.tftpd requests are handled as</li>
388 <li><b>group</b>: the group in.tftpd requests are handled as</li>
389 <li>
390 <b>server_args</b>: the root directory for the TFTP daemon to serve files
391 from
392 </li>
393 <li>
394 <b>only_from</b>: tells xinetd which hosts to allow TFTP connections from
395 </li>
396</ul>
397
398<p>
381Additional information on xinetd configuration files can be found in the 399Additional information on <c>xinetd</c> configuration files can be found in
382section 5 manpage on xinetd.conf 400<c>man 5 xinetd.conf</c>.
383</p>
384
385<p> 401</p>
402
403<p>
386If xinetd is running, you can send it the HUP signal to have it re-read its 404If <c>xinetd</c> is running, you can send it the HUP signal to have it re-read
387configuration files; 405its configuration files:
388</p> 406</p>
389 407
390<pre caption="Sending HUP signal to xinetd"> 408<pre caption="Sending HUP signal to xinetd">
391# <i>/bin/killall -HUP xinetd</i> 409# <i>/bin/killall -HUP xinetd</i>
392</pre> 410</pre>
393 411
394<p> 412<p>
395If xinetd is not running, start it with the init.d command; 413If <c>xinetd</c> is not running, start it with the init.d command:
396</p> 414</p>
397 415
398<pre caption="Starting xinetd"> 416<pre caption="Starting xinetd">
399# <i>/etc/init.d/xinetd start</i> 417# <i>/etc/init.d/xinetd start</i>
400</pre> 418</pre>
401 419
402<p> 420<p>
403For more information, consult the section 8 man page on in.tftpd 421For more information, consult <c>man 8 in.tftpd</c>.
404</p> 422</p>
405 423
406</body> 424</body>
407</section> 425</section>
408<section> 426<section>
409<title>The tftp-hpa Daemon</title> 427<title>The tftp-hpa Daemon</title>
410<body> 428<body>
411 429
412<p> 430<p>
413First, install the tftp-hpa package using the following command; 431First, install the <c>tftp-hpa</c> package:
414</p> 432</p>
415 433
416<pre caption="Installing tftp-hpa"> 434<pre caption="Installing tftp-hpa">
417# <i>emerge net-misc/tftp-hpa</i> 435# <i>emerge net-misc/tftp-hpa</i>
418</pre> 436</pre>
419 437
420<p> 438<p>
421tftp-hpa comes with an init.d and the accompanying conf.d configuration file. 439<c>tftp-hpa</c> comes with an <path>init.d</path> and the accompanying
422Check to make sure that INIITFTPD_PATH and INITFTP_OPTS in 440<path>conf.d</path> configuration file. Check to make sure that INTFTPD_PATH
423<path>/etc/conf.d/in.tftpd</path> match those below; 441and INTFTP_OPTS in <path>/etc/conf.d/in.tftpd</path> match those below:
424</p> 442</p>
425 443
426<pre caption="/etc/conf.d/in.tftpd"> 444<pre caption="/etc/conf.d/in.tftpd">
427INTFTPD_PATH="/tftpboot" 445INTFTPD_PATH="/tftpboot"
428INTFTPD_OPTS="-s -v -l ${INTFTPD_PATH}" 446INTFTPD_OPTS="-s -v -l ${INTFTPD_PATH}"
429</pre> 447</pre>
430 448
431<p> 449<p>
432The tftp daemon can then be started via the init.d script; 450The TFTP daemon can then be started via the <path>init.d</path> script:
433</p> 451</p>
434 452
435<pre caption="Starting in.tftpd"> 453<pre caption="Starting in.tftpd">
436# <i>/etc/init.d/in.tftpd start</i> 454# <i>/etc/init.d/in.tftpd start</i>
437</pre> 455</pre>
438 456
439<p> 457<p>
440For more options, consult the section 8 man page on tftpd. 458For more options, consult <c>man 8 tftpd</c>.
441</p> 459</p>
442 460
443</body> 461</body>
444</section> 462</section>
445</chapter> 463</chapter>
448<title>Preparing a tftpboot image for use by a client</title> 466<title>Preparing a tftpboot image for use by a client</title>
449<section> 467<section>
450<body> 468<body>
451 469
452<p> 470<p>
453Make sure you have an image you want to use for netbooting. For a sparc or 471Make sure you have an image you want to use for netbooting. Please check your
454sparc64 netboot image, please check your local Gentoo distfiles mirror under 472<uri link="/main/en/mirrors.xml">local</uri> Gentoo <uri
455<path>experimental/sparc/tftpboot</path> for the appropriate image. We'll 473link="http://distfiles.gentoo.org/experimental/sparc/tftpboot/sparc64/">distfiles
456assume you are planning to boot a sparc64 host using the 474mirror</uri> for the appropriate image. We'll assume you are planning to boot
457<path>gentoo-sparc64-1.4_rc4-20040102.tftpboot</path> image. 475using the <path>gentoo-sparc64-20100128.tftpboot</path> image.
458</p>
459
460<p> 476</p>
477
478<p>
461Once you have an image, copy the image into <path>/tftpboot</path>; 479Once you have an image, copy the image into <path>/tftpboot</path>:
462</p> 480</p>
463 481
464<pre caption="Copying the image"> 482<pre caption="Copying the image">
465# <i>cp gentoo-sparc64-1.4_rc4-20040102.tftpboot /tftpboot</i> 483# <i>cp gentoo-sparc64-20100128.tftpboot /tftpboot</i>
484# <i>chmod 644 /tftpboot/gentoo-sparc64-20100128.tftpboot</i>
466</pre> 485</pre>
467 486
468<p> 487<p>
469Now, when the netboot client makes a tftp request, it looks for a file that is 488Now, when the netboot client makes a TFTP request, it looks for a file that is
470the hexadecimal number of its current IP address, and on some platforms an 489the hexadecimal number of its current IP address, and on some platforms an
471<path>.ARCH</path> suffix. The hexadecimal number should use <e>capital</e> 490<path>.ARCH</path> suffix. The hexadecimal number should use <e>capital</e>
472characters. 491characters.
473</p> 492</p>
474 493
476So for our example IP address, 10.0.1.15, let's look at its hexadecimal 495So for our example IP address, 10.0.1.15, let's look at its hexadecimal
477equivalent: 496equivalent:
478</p> 497</p>
479 498
480<pre caption="Convert to hexadecimal"> 499<pre caption="Convert to hexadecimal">
481# <i>printf "%.2x%.2x%.2x%.2x\n" 10 0 1 15</i> 500# <i>printf "%.2X%.2X%.2X%.2X\n" 10 0 1 15</i>
482</pre> 501</pre>
483 502
484<pre caption="Example IP address"> 503<pre caption="Example IP address">
485decimal 10 0 1 15 504decimal 10 0 1 15
486hexadecimal 0A 00 01 0F 505hexadecimal 0A 00 01 0F
487</pre> 506</pre>
488 507
489<p> 508<p>
490So for the example sparc64 netboot client, it would look for a file named 509So for the example netboot client, it would look for a file named
4910A00010F when it tftpboots. 510<path>0A00010F</path> when it tftpboots.
492</p>
493
494<p> 511</p>
495On sparc however, the file would be 0A00010F.SUN4M, 0A00010F.SUN4C or 512
4960A00010F.SUN4D depending on what type of sparc system.
497</p> 513<p>
498
499<p>
500Additionally, if you are really really lazy (like me), you can netboot the host 514Iif you are really, really lazy (like me), you can netboot the host to get the
501to get the filename the client is looking for from the netboot server logs. 515filename the client is looking for from the netboot server logs.
502</p>
503
504<p> 516</p>
517
518<p>
505Make sure that both the rarpd and tftpd daemon you've chosen are currently 519Make sure that both the <c>rarpd</c> and TFTP daemon you've chosen are currently
506running, then boot the host as described below in "Netbooting the client". 520running, then boot the host as described below in <uri
521link="#netbootingclient">Netbooting the client</uri>.
507</p> 522</p>
508 523
509<p> 524<p>
510The client will appear to hang after the boot net command is issued. Then on 525The client will appear to hang after the boot net command is issued. Then on
511the netboot server, check the system logs for an entry for in.tftpd. 526the netboot server, check the system logs for an entry for <c>in.tftpd</c>.
512</p>
513
514<p> 527</p>
528
529<p>
515An example entry from a netboot server running sysklogd and tftp-hpa looks 530An example entry from a netboot server running <c>sysklogd</c> and
516like; 531<c>tftp-hpa</c> looks like:
517</p> 532</p>
518 533
519<pre caption="Log entry for netboot server"> 534<pre caption="Log entry for netboot server">
520Jan 3 22:48:59 stargazer in.tftpd[8368]: RRQ from 10.0.1.15 filename 0A00010F 535Jan 3 22:48:59 stargazer in.tftpd[8368]: RRQ from 10.0.1.15 filename 0A00010F
521</pre> 536</pre>
522 537
523<p> 538<p>
524The filename is shown above after "filename" in the log entry, which in this 539The filename is shown above after "filename" in the log entry, which in this
525case is 0A00010F. 540case is <path>0A00010F</path>.
526</p> 541</p>
527 542
528<p> 543<p>
529As a way to keep track of what netboot image you are using, and to allow 544As a way to keep track of what netboot image you are using, and to allow
530multiple machines to use the same netboot image, you can use a soft link to 545multiple machines to use the same netboot image, you can use a soft link to
531create the file with the hexadecimal value. To create this using our sample 546create the file with the hexadecimal value. To create this using our sample
532sparc64 host and the <path>gentoo-sparc64-1.4_rc4-20040102.tftpboot</path>, use 547sparc64 host and the <path>gentoo-sparc64-20100128.tftpboot</path>, use
533the following command; 548the following command:
534</p> 549</p>
535 550
536<pre caption="Linking the image files"> 551<pre caption="Linking the image files">
537# <i>/bin/ln -s /tftpboot/gentoo-sparc64-1.4_rc4-20040102.tftpboot \ 552# <i>/bin/ln -s /tftpboot/gentoo-sparc64-20100128.tftpboot \
538/tftpboot/0A00010F</i> 553/tftpboot/0A00010F</i>
539</pre> 554</pre>
540 555
541<p> 556<p>
542Now everything should be set for netbooting! 557Now everything should be set for netbooting!
544 559
545</body> 560</body>
546</section> 561</section>
547</chapter> 562</chapter>
548 563
549<chapter> 564<chapter id="netbootingclient">
550<title>Netbooting the client</title> 565<title>Netbooting the client</title>
551
552<section> 566<section>
553<body> 567<body>
554 568
555<p> 569<p>
556From OpenBoot PROM (OBP) on the SPARC, enter the command; 570From OpenBoot PROM (OBP) on the SPARC, enter the command;
596<p> 610<p>
597<b>Building the prerequisite software</b> 611<b>Building the prerequisite software</b>
598</p> 612</p>
599 613
600<p> 614<p>
601If the netboot server is a Gentoo/LINUX system and experiences problems 615If the netboot server is a Gentoo Linux system and experiences problems after
602installing the rarpd and tftpd packages, please search 616installing the rarpd and tftpd packages, please search the <uri
603<uri>http://forums.gentoo.org</uri> and <uri>http://bugs.gentoo.org</uri> to 617link="http://forums.gentoo.org">Gentoo Forums</uri> and <uri
604see if this problem has been encountered by anyone else. If it has not, or the 618link="http://bugs.gentoo.org">Gentoo Bugzilla</uri> to see if this problem has
605solutions found do not work, then please open a new bug at 619been encountered by anyone else. If it has not, or the solutions found do not
606<uri>http://bugs.gentoo.org</uri> 620work, then please open a new bug.
607</p> 621</p>
608 622
609<p> 623<p>
610<b>I've issued the boot net command but it appears to hang.</b> 624<b>I've issued the boot net command but it appears to hang.</b>
611</p> 625</p>
612 626
613<p> 627<p>
614This is presumably because the file your system is trying to load from the 628This is presumably because the file your system is trying to load from the
615tftpboot server is not available. On a SPARC system, you would probably see the 629tftpboot server is not available. On a SPARC system, you would probably see the
616following; 630following:
617</p> 631</p>
618 632
619<pre caption="Booting appears to hang"> 633<pre caption="Booting appears to hang">
620Rebooting with command: boot 634Rebooting with command: boot
621Boot device: net File and args: 635Boot device: net File and args:
673 </li> 687 </li>
674</ol> 688</ol>
675 689
676<p> 690<p>
677To change the value of tpe-link-test? from an OBP prompt, issue the following 691To change the value of tpe-link-test? from an OBP prompt, issue the following
678command; 692command:
679</p> 693</p>
680 694
681<pre caption="Changing tpe-link-test value"> 695<pre caption="Changing tpe-link-test value">
682ok <i>setenv tpe-link-test? true</i> 696ok <i>setenv tpe-link-test? true</i>
683tpe-link-test? = true 697tpe-link-test? = true

Legend:
Removed from v.1.11  
changed lines
  Added in v.1.12

  ViewVC Help
Powered by ViewVC 1.1.20