Attachment 65308 Details for Bug 101641 – gentoo-sparc-netboot-howto.xml.patch

[patch] gentoo-sparc-netboot-howto.xml.patch

gentoo-sparc-netboot-howto.xml.patch (text/plain), 12.96 KB, created by Łukasz Damentko (RETIRED) on 2005-08-07 06:46:46 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Łukasz Damentko (RETIRED)

Created: 2005-08-07 06:46:46 UTC

Size: 12.96 KB

patch

obsolete

>Index: gentoo-sparc-netboot-howto.xml
>===================================================================
>RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-sparc-netboot-howto.xml,v
>retrieving revision 1.6
>diff -u -u -r1.6 gentoo-sparc-netboot-howto.xml
>--- gentoo-sparc-netboot-howto.xml	26 Jun 2005 12:23:21 -0000	1.6
>+++ gentoo-sparc-netboot-howto.xml	7 Aug 2005 13:41:59 -0000
>@@ -10,12 +10,13 @@
> <abstract>
> Guide for setting up a netboot server for use with the Gentoo/SPARC netboot installation images.
> </abstract>
>+
> 
>-
>+
> <license/>
> 
>-<version>1.1</version>
>-<date>2005-06-25</date>
>+<version>1.2</version>
>+<date>2005-08-07</date>
> 
> <chapter>
> <title>Introduction</title>
>@@ -23,21 +24,20 @@
> <body>
> 
> <note>
>-This howto is currently very SPARC-centric and expecting that you will be 
>+This howto is currently very SPARC-centric and expecting that you will be
> setting up your netboot server on an existing Gentoo Linux machine.
> </note>
> 
> 
>-This document will describe how to setup a network booting environment for a 
>-Sun Microsystems SPARC or UltraSPARC based computer. The document assumes that
>-you have an existing Gentoo Linux computer available to act as the netboot
>-server.
>+This document will describe how to setup a network booting environment for a Sun
>+Microsystems SPARC or UltraSPARC based computer. The document assumes that you
>+have an existing Gentoo Linux computer available to act as the netboot server.
> 
> 
> 
>-Both the netboot server and netboot client will need to be on the same
>-network subnet, as the ARP protocol is typically not forwarded across
>-different network subnets.
>+Both the netboot server and netboot client will need to be on the same network
>+subnet, as the ARP protocol is typically not forwarded across different network
>+subnets.
> 
> 
> 
>@@ -77,7 +77,7 @@
> 
> 
> 
>-Currently, there are two choices for a reverse ARP daemon. They are
>+Currently, there are two choices for a reverse ARP daemon. They are
> net-misc/iputils (installed as part of the system profile) and net-misc/rarpd.
> 
> 
>@@ -92,7 +92,7 @@
> 
> 
> No matter which rarpd you choose to use, you will need to setup the 
>-<path>/etc/ethers</path> file. This file indicates which hosts rarpd should 
>+<path>/etc/ethers</path> file. This file indicates which hosts rarpd should
> respond to when a request is seen, and what address to reply with.
> 
> 
>@@ -113,8 +113,8 @@
> </note>
> 
> 
>-If you desire to add additional hosts to /etc/ethers, you do not need to
>-restart the rarpd services as the file is checked each time a request is
>+If you desire to add additional hosts to <path>/etc/ethers</path>, you do not
>+need to restart the rarpd services as the file is checked each time a request is
> received.
> 
> 
>@@ -123,16 +123,17 @@
> 
> 
> 
>-Since each entry in /etc/ethers has a hostname, the netboot server needs to
>-be able to resolve the hostname into its IP address. This can be done two
>-ways, /etc/hosts or the nameserver the netboot server uses.
>+Since each entry in <path>/etc/ethers</path> has a hostname, the netboot server
>+needs to be able to resolve the hostname into its IP address. This can be done
>+two ways, <path>/etc/hosts</path> or the nameserver the netboot server uses.
> 
> 
> 
>-An /etc/hosts entry for resolving a hostname will look very similar to the one
>-that probably exists from when you installed Gentoo on the netboot server.
>-For our example host, sparc-netboot.gentoo.org, we'll assume that it has an IP
>-address of 10.0.1.15. So the /etc/hosts entry would look like;
>+An <path>/etc/hosts</path> entry for resolving a hostname will look very similar
>+to the one that probably exists from when you installed Gentoo on the netboot
>+server. For our example host, sparc-netboot.gentoo.org, we'll assume that it
>+has an IP address of 10.0.1.15. So the <path>/etc/hosts</path> entry would look
>+like;
> 
> 
> <pre caption="/etc/hosts">
>@@ -147,17 +148,16 @@
> </note>
> 
> 
>-If you use a nameserver, then the DNS server administrator will need to add a 
>-record for the hostname, in our example sparc-netboot.gentoo.org, to point to 
>-the appropriate IP address.
>-Please consult your DNS server administrator and/or the documentation for the
>-DNS server's DNS software for how to add the entry.
>+If you use a nameserver, then the DNS server administrator will need to add a
>+record for the hostname, in our example sparc-netboot.gentoo.org, to point to
>+the appropriate IP address. Please consult your DNS server administrator and/or
>+the documentation for the DNS server's DNS software for how to add the entry.
> 
> 
> <note>
>-If both /etc/hosts and the nameserver have an entry for the host to be
>-netbooted, /etc/hosts will be used first (granted the order of
>-/etc/nsswitch.conf has not been changed from the default).
>+If both <path>/etc/hosts</path> and the nameserver have an entry for the host to
>+be netbooted, <path>/etc/hosts</path> will be used first (granted the order of
>+<path>/etc/nsswitch.conf</path> has not been changed from the default).
> </note>
> 
> 
>@@ -167,8 +167,8 @@
> First, we will need to determine the options to use for rarpd. While there
> are more options than we'll cover here, these options should get you started
> As there is currently no init.d script for net-misc/iputils version of rarpd,
>-an entry will need to be added to /etc/conf.d/local.start if you want to enable
>-rarpd servies at boot time. A sample entry is as follows;
>+an entry will need to be added to <path>/etc/conf.d/local.start</path> if you
>+want to enable rarpd servies at boot time. A sample entry is as follows;
> 
> 
> <pre caption="/etc/conf.d/local.start">
>@@ -183,7 +183,8 @@
> <li>-v Be verbose</li>
> <li>
> -e Do not check for the presence of a boot image, reply if MAC address 
>- resolves to a valid IP address using /etc/ethers database and DNS
>+ resolves to a valid IP address using <path>/etc/ethers</path> database and
>+ DNS
> </li>
> <li>
> eth0 represents the interface rarpd should bind to
>@@ -209,7 +210,7 @@
> 
> Next, options for rarpd will need to be set in /etc/conf.d/rarpd. For an
> equivalent configuration as the one used above for net-misc/iputils rarpd,
>-adjust /etc/conf.d/rarpd to look like the following
>+adjust <path>/etc/conf.d/rarpd</path> to look like the following:
> 
> 
> <pre caption="/etc/conf.d/rarpd">
>@@ -242,8 +243,8 @@
> 
> 
> Here there are three options for a tftp daemon, net-misc/atftp,
>-net-misc/netkit-tftp and net-misc/tftp-hpa. You only need to install one of
>-the tftp daemons for proper operation.
>+net-misc/netkit-tftp and net-misc/tftp-hpa. You only need to install one of the
>+tftp daemons for proper operation.
> 
> 
> 
>@@ -253,14 +254,15 @@
> 
> Each tftp daemon will need a directory from which to serve files to tftp
> clients. The directory we will use for this howto will be /tftpboot. This
>-will appear as the root (/) directory to the clients when requests are 
>-received. Additionally, we'll setup the system to run the tftp daemon with the
>-user and group nobody.
>+will appear as the root (<path>/</path>) directory to the clients when requests
>+are received. Additionally, we'll setup the system to run the tftp daemon with
>+the user and group nobody.
> 
> 
> 
> If the directory you have chosen does not currently exist, it will need to be
>-created with the mkdir command. The command for the example /tftpboot is;
>+created with the mkdir command. The command for the example
>+<path>/tftpboot</path> is;
> 
> 
> <pre caption="Creating /tftpboot">
>@@ -268,8 +270,8 @@
> </pre>
> 
> 
>-Then we will need to change the owner of /tftpboot so that it is owned by user
>-nobody and group nobody;
>+Then we will need to change the owner of <path>/tftpboot</path> so that it is
>+owned by user nobody and group nobody;
> 
> 
> <pre caption="Changing ownership">
>@@ -292,10 +294,10 @@
> 
> 
> After the net-misc/atftp package has been installed, it will need to be
>-configured. If tftpd services are desired at boot time, an entry to
>-/etc/conf.d/local.start will need to be added as atftp has no init.d, inetd or
>-xinetd scripts of its own. If you want to use inetd or xinetd for controlling
>-the tftpd service, please see their respective man pages.
>+configured. If tftpd services are desired at boot time, an entry to
>+<path>/etc/conf.d/local.start</path> will need to be added as atftp has no
>+init.d, inetd or xinetd scripts of its own. If you want to use inetd or xinetd
>+for controlling the tftpd service, please see their respective man pages.
> 
> 
> 
>@@ -410,6 +412,7 @@
> <section>
> <title>The tftp-hpa Daemon</title>
> <body>
>+
> 
> First, install the tftp-hpa package using the following command;
> 
>@@ -453,13 +456,13 @@
> 
> Make sure you have an image you want to use for netbooting. For a sparc or
> sparc64 netboot image, please check your local Gentoo distfiles mirror under
>-experimental/sparc/tftpboot for the appropriate image. We'll assume you are
>-planning to boot a sparc64 host using the
>-gentoo-sparc64-1.4_rc4-20040102.tftpboot image.
>+<path>experimental/sparc/tftpboot</path> for the appropriate image. We'll
>+assume you are planning to boot a sparc64 host using the
>+<path>gentoo-sparc64-1.4_rc4-20040102.tftpboot</path> image.
> 
> 
> 
>-Once you have an image, copy the image into /tftpboot;
>+Once you have an image, copy the image into <path>/tftpboot</path>;
> 
> 
> <pre caption="Copying the image">
>@@ -468,8 +471,8 @@
> 
> 
> Now, when the netboot client makes a tftp request, it looks for a file that is
>-the hexidecimal number of its current IP address, and on some platforms an
>-.ARCH suffix. The hexidecimal number should use <e>capital</e> characters.
>+the hexidecimal number of its current IP address, and on some platforms an .ARCH
>+suffix. The hexidecimal number should use <e>capital</e> characters.
> 
> 
> 
>@@ -483,12 +486,14 @@
> 
> 
> <note>
>-For each octet in the IP address (the 10 in 10.0.1.15 for instance), you
>-will need to convert it to hexidecimal, rather than converting the IP address asa singular number.
>+For each octet in the IP address (the 10 in 10.0.1.15 for instance), you will
>+need to convert it to hexidecimal, rather than converting the IP address asa
>+singular number.
> </note>
> 
>-So for our example IP address, 10.0.1.15, let's look at its hexidecimal
>-equivalent;
>+
>+So for our example IP address, 10.0.1.15, let's look at its hexidecimal
>+equivalent:
> 
> 
> <pre caption="Example IP address">
>@@ -539,8 +544,8 @@
> As a way to keep track of what netboot image you are using, and to allow
> multiple machines to use the same netboot image, you can use a soft link to
> create the file with the hexidecimal value. To create this using our sample
>-sparc64 host and the gentoo-sparc64-1.4_rc4-20040102.tftpboot, use the
>-following command;
>+sparc64 host and the <path>gentoo-sparc64-1.4_rc4-20040102.tftpboot</path>, use
>+the following command;
> 
> 
> <pre caption="Linking the image files">
>@@ -642,8 +647,7 @@
> 
> 
> I'm trying to netboot, but all I see are "Timeout waiting for 
>-ARP/RARP packet" messages.
>-
>+ARP/RARP packet" messages.
> 
> 
> 
>@@ -666,18 +670,17 @@
> Verify that the rarpd service is up and running.
> </li>
> <li>
>- The client does not think its NIC has a link to the network hub/switch
>- it is plugged into. Check to see if the NIC and the port on the network
>- hub or switch has a link light. If the link light is on, check
>- to see what the setting of tpe-link-test? is in OBP with the command;
>- <c>printenv tpe-link-test?</c>. You should receive something like 
>- <path>tpe-link-test? false true</path>.
>- The first column represents the parameter name, the second column shows the
>- current value for the the parameter, and the third column shows the default
>- value for the parameter. In the example above, we can see that the current
>- value is false, which means that the client is not checking to see if the
>- client and network hub or switch can establish a link before issuing its
>- RARP request. Often times this can cause the problem.
>+ The client does not think its NIC has a link to the network hub/switch it is
>+ plugged into. Check to see if the NIC and the port on the network hub or
>+ switch has a link light. If the link light is on, check to see what the
>+ setting of tpe-link-test? is in OBP with the command; <c>printenv
>+ tpe-link-test?</c>. You should receive something like <path>tpe-link-test?
>+ false true</path>. The first column represents the parameter name, the
>+ second column shows the current value for the the parameter, and the third
>+ column shows the default value for the parameter. In the example above, we
>+ can see that the current value is false, which means that the client is not
>+ checking to see if the client and network hub or switch can establish a link
>+ before issuing its RARP request. Often times this can cause the problem.
> </li>
> </ol>
> 
>@@ -701,4 +704,3 @@
> </chapter>
> 
> </guide>
>-

Actions: View | Diff

Attachments on bug 101641: 65308 | 65316 | 65319 | 65320