1 |
neysx 05/08/18 13:59:23 |
2 |
|
3 |
Modified: xml/htdocs/doc/en gentoo-sparc-netboot-howto.xml |
4 |
Log: |
5 |
#101641 Add missing <path> tags |
6 |
|
7 |
Revision Changes Path |
8 |
1.7 +28 -28 xml/htdocs/doc/en/gentoo-sparc-netboot-howto.xml |
9 |
|
10 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gentoo-sparc-netboot-howto.xml?rev=1.7&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
11 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gentoo-sparc-netboot-howto.xml?rev=1.7&content-type=text/plain&cvsroot=gentoo |
12 |
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gentoo-sparc-netboot-howto.xml.diff?r1=1.6&r2=1.7&cvsroot=gentoo |
13 |
|
14 |
Index: gentoo-sparc-netboot-howto.xml |
15 |
=================================================================== |
16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-sparc-netboot-howto.xml,v |
17 |
retrieving revision 1.6 |
18 |
retrieving revision 1.7 |
19 |
diff -u -r1.6 -r1.7 |
20 |
--- gentoo-sparc-netboot-howto.xml 26 Jun 2005 12:23:21 -0000 1.6 |
21 |
+++ gentoo-sparc-netboot-howto.xml 18 Aug 2005 13:59:23 -0000 1.7 |
22 |
@@ -1,6 +1,6 @@ |
23 |
<?xml version='1.0' encoding="UTF-8"?> |
24 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
25 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-sparc-netboot-howto.xml,v 1.6 2005/06/26 12:23:21 smithj Exp $ --> |
26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-sparc-netboot-howto.xml,v 1.7 2005/08/18 13:59:23 neysx Exp $ --> |
27 |
|
28 |
<guide link="/doc/en/gentoo-sparc-netboot-howto.xml"> |
29 |
<title>Gentoo Linux based Netboot HOWTO</title> |
30 |
@@ -11,11 +11,11 @@ |
31 |
Guide for setting up a netboot server for use with the Gentoo/SPARC netboot installation images. |
32 |
</abstract> |
33 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
34 |
-<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
35 |
+<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
36 |
<license/> |
37 |
|
38 |
-<version>1.1</version> |
39 |
-<date>2005-06-25</date> |
40 |
+<version>1.2</version> |
41 |
+<date>2005-08-18</date> |
42 |
|
43 |
<chapter> |
44 |
<title>Introduction</title> |
45 |
@@ -113,7 +113,7 @@ |
46 |
</note> |
47 |
|
48 |
<p> |
49 |
-If you desire to add additional hosts to /etc/ethers, you do not need to |
50 |
+If you desire to add additional hosts to <path>/etc/ethers</path>, you do not need to |
51 |
restart the rarpd services as the file is checked each time a request is |
52 |
received. |
53 |
</p> |
54 |
@@ -123,16 +123,16 @@ |
55 |
</p> |
56 |
|
57 |
<p> |
58 |
-Since each entry in /etc/ethers has a hostname, the netboot server needs to |
59 |
+Since each entry in <path>/etc/ethers</path> has a hostname, the netboot server needs to |
60 |
be able to resolve the hostname into its IP address. This can be done two |
61 |
-ways, /etc/hosts or the nameserver the netboot server uses. |
62 |
+ways, <path>/etc/hosts</path> or the nameserver the netboot server uses. |
63 |
</p> |
64 |
|
65 |
<p> |
66 |
-An /etc/hosts entry for resolving a hostname will look very similar to the one |
67 |
+An <path>/etc/hosts</path> entry for resolving a hostname will look very similar to the one |
68 |
that probably exists from when you installed Gentoo on the netboot server. |
69 |
For our example host, sparc-netboot.gentoo.org, we'll assume that it has an IP |
70 |
-address of 10.0.1.15. So the /etc/hosts entry would look like; |
71 |
+address of 10.0.1.15. So the <path>/etc/hosts</path> entry would look like; |
72 |
</p> |
73 |
|
74 |
<pre caption="/etc/hosts"> |
75 |
@@ -155,9 +155,9 @@ |
76 |
</p> |
77 |
|
78 |
<note> |
79 |
-If both /etc/hosts and the nameserver have an entry for the host to be |
80 |
-netbooted, /etc/hosts will be used first (granted the order of |
81 |
-/etc/nsswitch.conf has not been changed from the default). |
82 |
+If both <path>/etc/hosts</path> and the nameserver have an entry for the host to be |
83 |
+netbooted, <path>/etc/hosts</path> will be used first (granted the order of |
84 |
+<path>/etc/nsswitch.conf</path> has not been changed from the default). |
85 |
</note> |
86 |
|
87 |
<p> |
88 |
@@ -167,7 +167,7 @@ |
89 |
<p>First, we will need to determine the options to use for rarpd. While there |
90 |
are more options than we'll cover here, these options should get you started |
91 |
As there is currently no init.d script for net-misc/iputils version of rarpd, |
92 |
-an entry will need to be added to /etc/conf.d/local.start if you want to enable |
93 |
+an entry will need to be added to <path>/etc/conf.d/local.start</path> if you want to enable |
94 |
rarpd servies at boot time. A sample entry is as follows; |
95 |
</p> |
96 |
|
97 |
@@ -207,9 +207,9 @@ |
98 |
</pre> |
99 |
|
100 |
<p> |
101 |
-Next, options for rarpd will need to be set in /etc/conf.d/rarpd. For an |
102 |
+Next, options for rarpd will need to be set in <path>/etc/conf.d/rarpd</path>. For an |
103 |
equivalent configuration as the one used above for net-misc/iputils rarpd, |
104 |
-adjust /etc/conf.d/rarpd to look like the following |
105 |
+adjust <path>/etc/conf.d/rarpd</path> to look like the following |
106 |
</p> |
107 |
|
108 |
<pre caption="/etc/conf.d/rarpd"> |
109 |
@@ -253,7 +253,7 @@ |
110 |
<p> |
111 |
Each tftp daemon will need a directory from which to serve files to tftp |
112 |
clients. The directory we will use for this howto will be /tftpboot. This |
113 |
-will appear as the root (/) directory to the clients when requests are |
114 |
+will appear as the root (<path>/</path>) directory to the clients when requests are |
115 |
received. Additionally, we'll setup the system to run the tftp daemon with the |
116 |
user and group nobody. |
117 |
</p> |
118 |
@@ -268,7 +268,7 @@ |
119 |
</pre> |
120 |
|
121 |
<p> |
122 |
-Then we will need to change the owner of /tftpboot so that it is owned by user |
123 |
+Then we will need to change the owner of <path>/tftpboot</path> so that it is owned by user |
124 |
nobody and group nobody; |
125 |
</p> |
126 |
|
127 |
@@ -293,13 +293,13 @@ |
128 |
<p> |
129 |
After the net-misc/atftp package has been installed, it will need to be |
130 |
configured. If tftpd services are desired at boot time, an entry to |
131 |
-/etc/conf.d/local.start will need to be added as atftp has no init.d, inetd or |
132 |
+<path>/etc/conf.d/local.start</path> will need to be added as atftp has no init.d, inetd or |
133 |
xinetd scripts of its own. If you want to use inetd or xinetd for controlling |
134 |
the tftpd service, please see their respective man pages. |
135 |
</p> |
136 |
|
137 |
<p> |
138 |
-Below is an example entry for atftpd in /etc/conf.d/local.start; |
139 |
+Below is an example entry for atftpd in <path>/etc/conf.d/local.start</path>; |
140 |
</p> |
141 |
|
142 |
<pre caption="/etc/conf.d/local.start"> |
143 |
@@ -420,7 +420,7 @@ |
144 |
|
145 |
<p> |
146 |
tftp-hpa comes with an init.d and the accompanying conf.d configuration file. |
147 |
-Check to make sure that INIITFTPD_PATH and INITFTP_OPTS in /etc/conf.d/in.tftpd |
148 |
+Check to make sure that INIITFTPD_PATH and INITFTP_OPTS in <path>/etc/conf.d/in.tftpd</path> |
149 |
match those below; |
150 |
</p> |
151 |
|
152 |
@@ -453,13 +453,13 @@ |
153 |
<p> |
154 |
Make sure you have an image you want to use for netbooting. For a sparc or |
155 |
sparc64 netboot image, please check your local Gentoo distfiles mirror under |
156 |
-experimental/sparc/tftpboot for the appropriate image. We'll assume you are |
157 |
+<path>experimental/sparc/tftpboot</path> for the appropriate image. We'll assume you are |
158 |
planning to boot a sparc64 host using the |
159 |
-gentoo-sparc64-1.4_rc4-20040102.tftpboot image. |
160 |
+<path>gentoo-sparc64-1.4_rc4-20040102.tftpboot</path> image. |
161 |
</p> |
162 |
|
163 |
<p> |
164 |
-Once you have an image, copy the image into /tftpboot; |
165 |
+Once you have an image, copy the image into <path>/tftpboot</path>; |
166 |
</p> |
167 |
|
168 |
<pre caption="Copying the image"> |
169 |
@@ -469,7 +469,7 @@ |
170 |
<p> |
171 |
Now, when the netboot client makes a tftp request, it looks for a file that is |
172 |
the hexidecimal number of its current IP address, and on some platforms an |
173 |
-.ARCH suffix. The hexidecimal number should use <e>capital</e> characters. |
174 |
+<path>.ARCH</path> suffix. The hexidecimal number should use <e>capital</e> characters. |
175 |
</p> |
176 |
|
177 |
<p> |
178 |
@@ -539,7 +539,7 @@ |
179 |
As a way to keep track of what netboot image you are using, and to allow |
180 |
multiple machines to use the same netboot image, you can use a soft link to |
181 |
create the file with the hexidecimal value. To create this using our sample |
182 |
-sparc64 host and the gentoo-sparc64-1.4_rc4-20040102.tftpboot, use the |
183 |
+sparc64 host and the <path>gentoo-sparc64-1.4_rc4-20040102.tftpboot</path>, use the |
184 |
following command; |
185 |
</p> |
186 |
|
187 |
@@ -609,7 +609,7 @@ |
188 |
|
189 |
<p> |
190 |
If the netboot server is a Gentoo/LINUX system and experiences problems |
191 |
-installing the rarpd and tftpd packages, please search http://forums.gentoo.org |
192 |
+installing the rarpd and tftpd packages, please search <uri>http://forums.gentoo.org</uri> |
193 |
and <uri>http://bugs.gentoo.org</uri> to see if this problem has been |
194 |
encountered by anyone else. If it has not, or the solutions found do not work, |
195 |
then please open a new bug at <uri>http://bugs.gentoo.org</uri> |
196 |
@@ -631,7 +631,7 @@ |
197 |
</pre> |
198 |
|
199 |
<p> |
200 |
-Double check that the file the client needs does exist in /tftpboot. You can |
201 |
+Double check that the file the client needs does exist in <path>/tftpboot</path>. You can |
202 |
confirm the filename it is requesting by looking in the system logs. Also, |
203 |
once this file exists, the client will try to load it. Sometimes, when |
204 |
the file is missing originally, it will freeze downloading the file once it |
205 |
@@ -652,7 +652,7 @@ |
206 |
|
207 |
<ol> |
208 |
<li> |
209 |
- Make sure the entry in /etc/ethers exists for the client in question. If |
210 |
+ Make sure the entry in <path>/etc/ethers</path> exists for the client in question. If |
211 |
the MAC address is incorrect and/or the netboot server cannot resolve the |
212 |
hostname for the client, it cannot respond with the needed information. |
213 |
|
214 |
|
215 |
|
216 |
-- |
217 |
gentoo-doc-cvs@g.o mailing list |