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

gentoo-sparc-netboot-howto.xml.path.patch (text/plain), 7.31 KB, created by Łukasz Damentko (RETIRED) on 2005-08-07 09:04:02 UTC

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 15:54:51 -0000
@@ -113,7 +113,7 @@
 </note>
 
 <p>
-If you desire to add additional hosts to /etc/ethers, you do not need to
+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.
 </p>
@@ -123,16 +123,16 @@
 </p>
 
 <p>
-Since each entry in /etc/ethers has a hostname, the netboot server needs to
+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, /etc/hosts or the nameserver the netboot server uses.
+ways, <path>/etc/hosts</path> or the nameserver the netboot server uses.
 </p>
 
 <p>
-An /etc/hosts entry for resolving a hostname will look very similar to the one
+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 /etc/hosts entry would look like;
+address of 10.0.1.15.  So the <path>/etc/hosts</path> entry would look like;
 </p>
 
 <pre caption="/etc/hosts">
@@ -155,9 +155,9 @@
 </p>
 
 <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>
 
 <p>
@@ -167,7 +167,7 @@
 <p>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
+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;
 </p>
 
@@ -207,9 +207,9 @@
 </pre>
 
 <p>
-Next, options for rarpd will need to be set in /etc/conf.d/rarpd.  For an
+Next, options for rarpd will need to be set in <path>/etc/conf.d/rarpd</path>.  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
 </p>
 
 <pre caption="/etc/conf.d/rarpd">
@@ -253,7 +253,7 @@
 <p>
 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 
+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.
 </p>
@@ -268,7 +268,7 @@
 </pre>
 
 <p>
-Then we will need to change the owner of /tftpboot so that it is owned by user
+Then we will need to change the owner of <path>/tftpboot</path> so that it is owned by user
 nobody and group nobody;
 </p>
 
@@ -293,13 +293,13 @@
 <p>
 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
+<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.
 </p>
 
 <p>
-Below is an example entry for atftpd in /etc/conf.d/local.start;
+Below is an example entry for atftpd in <path>/etc/conf.d/local.start</path>;
 </p>
 
 <pre caption="/etc/conf.d/local.start">
@@ -420,7 +420,7 @@
 
 <p>
 tftp-hpa comes with an init.d and the accompanying conf.d configuration file.
-Check to make sure that INIITFTPD_PATH and INITFTP_OPTS in /etc/conf.d/in.tftpd
+Check to make sure that INIITFTPD_PATH and INITFTP_OPTS in <path>/etc/conf.d/in.tftpd</path>
 match those below;
 </p>
 
@@ -453,13 +453,13 @@
 <p>
 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
+<path>experimental/sparc/tftpboot</path> 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>gentoo-sparc64-1.4_rc4-20040102.tftpboot</path> image.
 </p>
 
 <p>
-Once you have an image, copy the image into /tftpboot;
+Once you have an image, copy the image into <path>/tftpboot</path>;
 </p>
 
 <pre caption="Copying the image">
@@ -469,7 +469,7 @@
 <p>
 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.
+<path>.ARCH</path> suffix. The hexidecimal number should use <e>capital</e> characters.
 </p>
 
 <p>
@@ -539,7 +539,7 @@
 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
+sparc64 host and the <path>gentoo-sparc64-1.4_rc4-20040102.tftpboot</path>, use the
 following command;
 </p>
 
@@ -609,7 +609,7 @@
 
 <p>
 If the netboot server is a Gentoo/LINUX system and experiences problems
-installing the rarpd and tftpd packages, please search http://forums.gentoo.org
+installing the rarpd and tftpd packages, please search <uri>http://forums.gentoo.org</uri>
 and <uri>http://bugs.gentoo.org</uri> to see if this problem has been
 encountered by anyone else.  If it has not, or the solutions found do not work,
 then please open a new bug at <uri>http://bugs.gentoo.org</uri>
@@ -631,7 +631,7 @@
 </pre>
 
 <p>
-Double check that the file the client needs does exist in /tftpboot.  You can
+Double check that the file the client needs does exist in <path>/tftpboot</path>.  You can
 confirm the filename it is requesting by looking in the system logs.  Also,
 once this file exists, the client will try to load it.  Sometimes, when
 the file is missing originally, it will freeze downloading the file once it
@@ -652,7 +652,7 @@
 
 <ol>
   <li>
-    Make sure the entry in /etc/ethers exists for the client in question.  If
+    Make sure the entry in <path>/etc/ethers</path> exists for the client in question.  If
     the MAC address is incorrect and/or the netboot server cannot resolve the
     hostname for the client, it cannot respond with the needed information.
   </li>