/[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.6 Revision 1.7
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.6 2005/06/26 12:23:21 smithj Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-sparc-netboot-howto.xml,v 1.7 2005/08/18 13:59:23 neysx Exp $ -->
4 4
5<guide link="/doc/en/gentoo-sparc-netboot-howto.xml"> 5<guide link="/doc/en/gentoo-sparc-netboot-howto.xml">
6<title>Gentoo Linux based Netboot HOWTO</title> 6<title>Gentoo Linux based Netboot HOWTO</title>
7<author title="SPARC Developer"> 7<author title="SPARC Developer">
8 <mail link="weeve@gentoo.org">Jason Wever</mail> 8 <mail link="weeve@gentoo.org">Jason Wever</mail>
9</author> 9</author>
10<abstract> 10<abstract>
11Guide for setting up a netboot server for use with the Gentoo/SPARC netboot installation images. 11Guide for setting up a netboot server for use with the Gentoo/SPARC netboot installation images.
12</abstract> 12</abstract>
13<!-- The content of this document is licensed under the CC-BY-SA license --> 13<!-- The content of this document is licensed under the CC-BY-SA license -->
14<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> 14<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
15<license/> 15<license/>
16 16
17<version>1.1</version> 17<version>1.2</version>
18<date>2005-06-25</date> 18<date>2005-08-18</date>
19 19
20<chapter> 20<chapter>
21<title>Introduction</title> 21<title>Introduction</title>
22<section> 22<section>
23<body> 23<body>
111If a given hexidecimal number in the MAC address starts or is 0, you can 111If a given hexidecimal number in the MAC address starts or is 0, you can
112chose to omit the first 0 (i.e. 08:00:20:77:1f:3e becomes 8:0:20:77:1f:3e). 112chose to omit the first 0 (i.e. 08:00:20:77:1f:3e becomes 8:0:20:77:1f:3e).
113</note> 113</note>
114 114
115<p> 115<p>
116If you desire to add additional hosts to /etc/ethers, you do not need to 116If you desire to add additional hosts to <path>/etc/ethers</path>, you do not need to
117restart the rarpd services as the file is checked each time a request is 117restart the rarpd services as the file is checked each time a request is
118received. 118received.
119</p> 119</p>
120 120
121<p> 121<p>
122<b>Resolving hostnames</b>: <path>/etc/hosts</path> 122<b>Resolving hostnames</b>: <path>/etc/hosts</path>
123</p> 123</p>
124 124
125<p> 125<p>
126Since each entry in /etc/ethers has a hostname, the netboot server needs to 126Since each entry in <path>/etc/ethers</path> has a hostname, the netboot server needs to
127be able to resolve the hostname into its IP address. This can be done two 127be able to resolve the hostname into its IP address. This can be done two
128ways, /etc/hosts or the nameserver the netboot server uses. 128ways, <path>/etc/hosts</path> or the nameserver the netboot server uses.
129</p>
130
131<p> 129</p>
130
131<p>
132An /etc/hosts entry for resolving a hostname will look very similar to the one 132An <path>/etc/hosts</path> entry for resolving a hostname will look very similar to the one
133that probably exists from when you installed Gentoo on the netboot server. 133that probably exists from when you installed Gentoo on the netboot server.
134For our example host, sparc-netboot.gentoo.org, we'll assume that it has an IP 134For our example host, sparc-netboot.gentoo.org, we'll assume that it has an IP
135address of 10.0.1.15. So the /etc/hosts entry would look like; 135address of 10.0.1.15. So the <path>/etc/hosts</path> entry would look like;
136</p> 136</p>
137 137
138<pre caption="/etc/hosts"> 138<pre caption="/etc/hosts">
13910.0.1.15 sparc-netboot.gentoo.org 13910.0.1.15 sparc-netboot.gentoo.org
140</pre> 140</pre>
153Please consult your DNS server administrator and/or the documentation for the 153Please consult your DNS server administrator and/or the documentation for the
154DNS server's DNS software for how to add the entry. 154DNS server's DNS software for how to add the entry.
155</p> 155</p>
156 156
157<note> 157<note>
158If both /etc/hosts and the nameserver have an entry for the host to be 158If both <path>/etc/hosts</path> and the nameserver have an entry for the host to be
159netbooted, /etc/hosts will be used first (granted the order of 159netbooted, <path>/etc/hosts</path> will be used first (granted the order of
160/etc/nsswitch.conf has not been changed from the default). 160<path>/etc/nsswitch.conf</path> has not been changed from the default).
161</note> 161</note>
162 162
163<p> 163<p>
164<b>Setting up net-misc/iputils rarpd</b> 164<b>Setting up net-misc/iputils rarpd</b>
165</p> 165</p>
166 166
167<p>First, we will need to determine the options to use for rarpd. While there 167<p>First, we will need to determine the options to use for rarpd. While there
168are more options than we'll cover here, these options should get you started 168are more options than we'll cover here, these options should get you started
169As there is currently no init.d script for net-misc/iputils version of rarpd, 169As there is currently no init.d script for net-misc/iputils version of rarpd,
170an entry will need to be added to /etc/conf.d/local.start if you want to enable 170an entry will need to be added to <path>/etc/conf.d/local.start</path> if you want to enable
171rarpd servies at boot time. A sample entry is as follows; 171rarpd servies at boot time. A sample entry is as follows;
172</p> 172</p>
173 173
174<pre caption="/etc/conf.d/local.start"> 174<pre caption="/etc/conf.d/local.start">
175/usr/sbin/rarpd -v -e eth0 175/usr/sbin/rarpd -v -e eth0
205<pre caption="Installing rarpd"> 205<pre caption="Installing rarpd">
206# <i>emerge net-misc/rarpd</i> 206# <i>emerge net-misc/rarpd</i>
207</pre> 207</pre>
208 208
209<p> 209<p>
210Next, options for rarpd will need to be set in /etc/conf.d/rarpd. For an 210Next, options for rarpd will need to be set in <path>/etc/conf.d/rarpd</path>. For an
211equivalent configuration as the one used above for net-misc/iputils rarpd, 211equivalent configuration as the one used above for net-misc/iputils rarpd,
212adjust /etc/conf.d/rarpd to look like the following 212adjust <path>/etc/conf.d/rarpd</path> to look like the following
213</p> 213</p>
214 214
215<pre caption="/etc/conf.d/rarpd"> 215<pre caption="/etc/conf.d/rarpd">
216RARPD_OPTS="-v -i eth0" 216RARPD_OPTS="-v -i eth0"
217</pre> 217</pre>
251</p> 251</p>
252 252
253<p> 253<p>
254Each tftp daemon will need a directory from which to serve files to tftp 254Each tftp daemon will need a directory from which to serve files to tftp
255clients. The directory we will use for this howto will be /tftpboot. This 255clients. The directory we will use for this howto will be /tftpboot. This
256will appear as the root (/) directory to the clients when requests are 256will appear as the root (<path>/</path>) directory to the clients when requests are
257received. Additionally, we'll setup the system to run the tftp daemon with the 257received. Additionally, we'll setup the system to run the tftp daemon with the
258user and group nobody. 258user and group nobody.
259</p> 259</p>
260 260
261<p> 261<p>
266<pre caption="Creating /tftpboot"> 266<pre caption="Creating /tftpboot">
267# <i>/bin/mkdir /tftpboot</i> 267# <i>/bin/mkdir /tftpboot</i>
268</pre> 268</pre>
269 269
270<p> 270<p>
271Then we will need to change the owner of /tftpboot so that it is owned by user 271Then we will need to change the owner of <path>/tftpboot</path> so that it is owned by user
272nobody and group nobody; 272nobody and group nobody;
273</p> 273</p>
274 274
275<pre caption="Changing ownership"> 275<pre caption="Changing ownership">
276# <i>chown nobody:nobody /tftpboot</i> 276# <i>chown nobody:nobody /tftpboot</i>
291</pre> 291</pre>
292 292
293<p> 293<p>
294After the net-misc/atftp package has been installed, it will need to be 294After the net-misc/atftp package has been installed, it will need to be
295configured. If tftpd services are desired at boot time, an entry to 295configured. If tftpd services are desired at boot time, an entry to
296/etc/conf.d/local.start will need to be added as atftp has no init.d, inetd or 296<path>/etc/conf.d/local.start</path> will need to be added as atftp has no init.d, inetd or
297xinetd scripts of its own. If you want to use inetd or xinetd for controlling 297xinetd scripts of its own. If you want to use inetd or xinetd for controlling
298the tftpd service, please see their respective man pages. 298the tftpd service, please see their respective man pages.
299</p> 299</p>
300 300
301<p> 301<p>
302Below is an example entry for atftpd in /etc/conf.d/local.start; 302Below is an example entry for atftpd in <path>/etc/conf.d/local.start</path>;
303</p> 303</p>
304 304
305<pre caption="/etc/conf.d/local.start"> 305<pre caption="/etc/conf.d/local.start">
306/usr/sbin/in.tftpd -v --daemon /tftpboot 306/usr/sbin/in.tftpd -v --daemon /tftpboot
307</pre> 307</pre>
418# <i>emerge net-misc/tftp-hpa</i> 418# <i>emerge net-misc/tftp-hpa</i>
419</pre> 419</pre>
420 420
421<p> 421<p>
422tftp-hpa comes with an init.d and the accompanying conf.d configuration file. 422tftp-hpa comes with an init.d and the accompanying conf.d configuration file.
423Check to make sure that INIITFTPD_PATH and INITFTP_OPTS in /etc/conf.d/in.tftpd 423Check to make sure that INIITFTPD_PATH and INITFTP_OPTS in <path>/etc/conf.d/in.tftpd</path>
424match those below; 424match those below;
425</p> 425</p>
426 426
427<pre caption="/etc/conf.d/in.tftpd"> 427<pre caption="/etc/conf.d/in.tftpd">
428INTFTPD_PATH="/tftpboot" 428INTFTPD_PATH="/tftpboot"
451<body> 451<body>
452 452
453<p> 453<p>
454Make sure you have an image you want to use for netbooting. For a sparc or 454Make sure you have an image you want to use for netbooting. For a sparc or
455sparc64 netboot image, please check your local Gentoo distfiles mirror under 455sparc64 netboot image, please check your local Gentoo distfiles mirror under
456experimental/sparc/tftpboot for the appropriate image. We'll assume you are 456<path>experimental/sparc/tftpboot</path> for the appropriate image. We'll assume you are
457planning to boot a sparc64 host using the 457planning to boot a sparc64 host using the
458gentoo-sparc64-1.4_rc4-20040102.tftpboot image. 458<path>gentoo-sparc64-1.4_rc4-20040102.tftpboot</path> image.
459</p>
460
461<p> 459</p>
460
461<p>
462Once you have an image, copy the image into /tftpboot; 462Once you have an image, copy the image into <path>/tftpboot</path>;
463</p> 463</p>
464 464
465<pre caption="Copying the image"> 465<pre caption="Copying the image">
466# <i>cp gentoo-sparc64-1.4_rc4-20040102.tftpboot /tftpboot</i> 466# <i>cp gentoo-sparc64-1.4_rc4-20040102.tftpboot /tftpboot</i>
467</pre> 467</pre>
468 468
469<p> 469<p>
470Now, when the netboot client makes a tftp request, it looks for a file that is 470Now, when the netboot client makes a tftp request, it looks for a file that is
471the hexidecimal number of its current IP address, and on some platforms an 471the hexidecimal number of its current IP address, and on some platforms an
472.ARCH suffix. The hexidecimal number should use <e>capital</e> characters. 472<path>.ARCH</path> suffix. The hexidecimal number should use <e>capital</e> characters.
473</p> 473</p>
474 474
475<p> 475<p>
476A guide on how to convert decimal to hexidecimal is available at 476A guide on how to convert decimal to hexidecimal is available at
477<uri>http://www.permadi.com/tutorial/numDecToHex/</uri> 477<uri>http://www.permadi.com/tutorial/numDecToHex/</uri>
537 537
538<p> 538<p>
539As a way to keep track of what netboot image you are using, and to allow 539As a way to keep track of what netboot image you are using, and to allow
540multiple machines to use the same netboot image, you can use a soft link to 540multiple machines to use the same netboot image, you can use a soft link to
541create the file with the hexidecimal value. To create this using our sample 541create the file with the hexidecimal value. To create this using our sample
542sparc64 host and the gentoo-sparc64-1.4_rc4-20040102.tftpboot, use the 542sparc64 host and the <path>gentoo-sparc64-1.4_rc4-20040102.tftpboot</path>, use the
543following command; 543following command;
544</p> 544</p>
545 545
546<pre caption="Linking the image files"> 546<pre caption="Linking the image files">
547# <i>/bin/ln -s /tftpboot/gentoo-sparc64-1.4_rc4-20040102.tftpboot \ 547# <i>/bin/ln -s /tftpboot/gentoo-sparc64-1.4_rc4-20040102.tftpboot \
607<b>Building the prerequisite software</b> 607<b>Building the prerequisite software</b>
608</p> 608</p>
609 609
610<p> 610<p>
611If the netboot server is a Gentoo/LINUX system and experiences problems 611If the netboot server is a Gentoo/LINUX system and experiences problems
612installing the rarpd and tftpd packages, please search http://forums.gentoo.org 612installing the rarpd and tftpd packages, please search <uri>http://forums.gentoo.org</uri>
613and <uri>http://bugs.gentoo.org</uri> to see if this problem has been 613and <uri>http://bugs.gentoo.org</uri> to see if this problem has been
614encountered by anyone else. If it has not, or the solutions found do not work, 614encountered by anyone else. If it has not, or the solutions found do not work,
615then please open a new bug at <uri>http://bugs.gentoo.org</uri> 615then please open a new bug at <uri>http://bugs.gentoo.org</uri>
616</p> 616</p>
617 617
629Rebooting with command: boot 629Rebooting with command: boot
630Boot device: net File and args: 630Boot device: net File and args:
631</pre> 631</pre>
632 632
633<p> 633<p>
634Double check that the file the client needs does exist in /tftpboot. You can 634Double check that the file the client needs does exist in <path>/tftpboot</path>. You can
635confirm the filename it is requesting by looking in the system logs. Also, 635confirm the filename it is requesting by looking in the system logs. Also,
636once this file exists, the client will try to load it. Sometimes, when 636once this file exists, the client will try to load it. Sometimes, when
637the file is missing originally, it will freeze downloading the file once it 637the file is missing originally, it will freeze downloading the file once it
638appears. To resolve this, just get back to an OBP prompt, and issue the 638appears. To resolve this, just get back to an OBP prompt, and issue the
639"boot net" command again. The host should then start downloading the tftpboot 639"boot net" command again. The host should then start downloading the tftpboot
650This could be due to a few different problems; 650This could be due to a few different problems;
651</p> 651</p>
652 652
653<ol> 653<ol>
654 <li> 654 <li>
655 Make sure the entry in /etc/ethers exists for the client in question. If 655 Make sure the entry in <path>/etc/ethers</path> exists for the client in question. If
656 the MAC address is incorrect and/or the netboot server cannot resolve the 656 the MAC address is incorrect and/or the netboot server cannot resolve the
657 hostname for the client, it cannot respond with the needed information. 657 hostname for the client, it cannot respond with the needed information.
658 </li> 658 </li>
659 <li> 659 <li>
660 Verify that the network hub or switch the netboot server and client are 660 Verify that the network hub or switch the netboot server and client are

Legend:
Removed from v.1.6  
changed lines
  Added in v.1.7

  ViewVC Help
Powered by ViewVC 1.1.20