1 |
swift 08/05/19 21:16:02 |
2 |
|
3 |
Modified: ltsp.xml |
4 |
Log: |
5 |
Last coding style for today, nite folks |
6 |
|
7 |
Revision Changes Path |
8 |
1.21 xml/htdocs/doc/en/ltsp.xml |
9 |
|
10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/ltsp.xml?rev=1.21&view=markup |
11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/ltsp.xml?rev=1.21&content-type=text/plain |
12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/ltsp.xml?r1=1.20&r2=1.21 |
13 |
|
14 |
Index: ltsp.xml |
15 |
=================================================================== |
16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/ltsp.xml,v |
17 |
retrieving revision 1.20 |
18 |
retrieving revision 1.21 |
19 |
diff -u -r1.20 -r1.21 |
20 |
--- ltsp.xml 3 May 2007 05:56:27 -0000 1.20 |
21 |
+++ ltsp.xml 19 May 2008 21:16:02 -0000 1.21 |
22 |
@@ -1,17 +1,17 @@ |
23 |
<?xml version='1.0' encoding="UTF-8"?> |
24 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/ltsp.xml,v 1.20 2007/05/03 05:56:27 nightmorph Exp $ --> |
25 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/ltsp.xml,v 1.21 2008/05/19 21:16:02 swift Exp $ --> |
26 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
27 |
|
28 |
<guide link="/doc/en/ltsp.xml"> |
29 |
<title>Gentoo - LTSP Guide</title> |
30 |
<author title="Author"> |
31 |
- <mail link="lanius@g.o">Heinrich Wendel</mail> |
32 |
+ <mail link="lanius@g.o">Heinrich Wendel</mail> |
33 |
</author> |
34 |
<author title="Author"> |
35 |
- <mail link="josiah@××××××××××××.net">Josiah Ritchie</mail> |
36 |
+ <mail link="josiah@××××××××××××.net">Josiah Ritchie</mail> |
37 |
</author> |
38 |
<author title="Editor"> |
39 |
- <mail link="swift@g.o">Sven Vermeulen</mail> |
40 |
+ <mail link="swift@g.o">Sven Vermeulen</mail> |
41 |
</author> |
42 |
|
43 |
<abstract> |
44 |
@@ -30,18 +30,19 @@ |
45 |
<body> |
46 |
|
47 |
<p> |
48 |
-LTSP is an abbreviation for "Linux Terminal Server Project". Installed |
49 |
-on a server it can supply many workstations (so called thin-clients) |
50 |
-with identical environments. All applications run on the server and |
51 |
-therefore you can use old PCs and convert them into XTerminals. This |
52 |
-reduces costs and maintenance especially in an environment where you |
53 |
-need to have an uniform workspace on each computer you login, e.g. in |
54 |
+LTSP is an abbreviation for "Linux Terminal Server Project". Installed |
55 |
+on a server it can supply many workstations (so called thin-clients) |
56 |
+with identical environments. All applications run on the server and |
57 |
+therefore you can use old PCs and convert them into XTerminals. This |
58 |
+reduces costs and maintenance especially in an environment where you |
59 |
+need to have an uniform workspace on each computer you login, e.g. in |
60 |
schools or firms. |
61 |
</p> |
62 |
|
63 |
</body> |
64 |
</section> |
65 |
</chapter> |
66 |
+ |
67 |
<chapter> |
68 |
<title>Installation</title> |
69 |
<section> |
70 |
@@ -49,8 +50,8 @@ |
71 |
<body> |
72 |
|
73 |
<p> |
74 |
-All of the examples in this document presume that your server's IP is |
75 |
-192.168.0.254, your domain is named yourdomain.com and your network is |
76 |
+All of the examples in this document presume that your server's IP is |
77 |
+192.168.0.254, your domain is named yourdomain.com and your network is |
78 |
192.168.0.0/24. |
79 |
</p> |
80 |
|
81 |
@@ -81,32 +82,34 @@ |
82 |
<ul> |
83 |
<li><b>XFree</b>: They are called XTerminals, guess why :)</li> |
84 |
<li> |
85 |
- <b>DHCP</b>: DHCP is a protocol for automating the configuration of |
86 |
- computers that use TCP/IP, used by ltsp to distribute IPs to the |
87 |
+ <b>DHCP</b>: DHCP is a protocol for automating the configuration of |
88 |
+ computers that use TCP/IP, used by ltsp to distribute IPs to the |
89 |
workstations. |
90 |
</li> |
91 |
<li> |
92 |
- <b>NFS</b>: NFS is a protocol to allow access to harddisks through |
93 |
- the network, used by ltsp to mount a base system for the |
94 |
+ <b>NFS</b>: NFS is a protocol to allow access to harddisks through |
95 |
+ the network, used by ltsp to mount a base system for the |
96 |
workstations. |
97 |
</li> |
98 |
<li> |
99 |
- <b>TFTP</b>: TFTP is a simple file transfer protocol, used by ltsp |
100 |
+ <b>TFTP</b>: TFTP is a simple file transfer protocol, used by ltsp |
101 |
to transfer the kernel to the workstations. |
102 |
</li> |
103 |
<li> |
104 |
- <b>XINETD</b>: Xinetd is a powerful replacement for inetd, with |
105 |
+ <b>XINETD</b>: Xinetd is a powerful replacement for inetd, with |
106 |
advanced features, used by ltsp to start tftp. |
107 |
</li> |
108 |
</ul> |
109 |
|
110 |
<note> |
111 |
-If you have the kde/gnome useflag set, it will also install a complete kde/gnome system. |
112 |
+If you have the kde/gnome useflag set, it will also install a complete kde/gnome |
113 |
+system. |
114 |
</note> |
115 |
|
116 |
</body> |
117 |
</section> |
118 |
</chapter> |
119 |
+ |
120 |
<chapter> |
121 |
<title>Configuration</title> |
122 |
<section> |
123 |
@@ -123,7 +126,7 @@ |
124 |
<body> |
125 |
|
126 |
<p> |
127 |
-To analyze problems easier, the system logger must be configured to |
128 |
+To analyze problems easier, the system logger must be configured to |
129 |
accept remote connections. Please read the documentation of your |
130 |
system logger on how to achieve this. If, for example, you are using |
131 |
sysklogd, all you need to do is edit <path>/etc/conf.d/sysklogd</path> and add |
132 |
@@ -142,8 +145,8 @@ |
133 |
<body> |
134 |
|
135 |
<p> |
136 |
-Next step is to edit your <path>/etc/exports</path> file, in order to |
137 |
-allow the workstations to mount the root filesystem. There should be at |
138 |
+Next step is to edit your <path>/etc/exports</path> file, in order to |
139 |
+allow the workstations to mount the root filesystem. There should be at |
140 |
least two lines in it: |
141 |
</p> |
142 |
|
143 |
@@ -153,7 +156,7 @@ |
144 |
</pre> |
145 |
|
146 |
<note> |
147 |
-You have to alter the network/netmask to match your network/netmask |
148 |
+You have to alter the network/netmask to match your network/netmask |
149 |
settings. |
150 |
</note> |
151 |
|
152 |
@@ -168,7 +171,6 @@ |
153 |
|
154 |
</body> |
155 |
</section> |
156 |
- |
157 |
<section> |
158 |
<title>xinetd/tftp</title> |
159 |
<body> |
160 |
@@ -209,7 +211,8 @@ |
161 |
</pre> |
162 |
|
163 |
<p> |
164 |
-Now edit <path>/etc/xinetd.conf</path> and comment out the line <c>only_from = localhost</c> by prefacing it with a <c>#</c>. Finally, start xinetd. |
165 |
+Now edit <path>/etc/xinetd.conf</path> and comment out the line <c>only_from = |
166 |
+localhost</c> by prefacing it with a <c>#</c>. Finally, start xinetd. |
167 |
</p> |
168 |
|
169 |
<pre caption="Starting xinetd"> |
170 |
@@ -232,9 +235,9 @@ |
171 |
</p> |
172 |
|
173 |
<p> |
174 |
-All workstations must be listed in <path>/etc/hosts</path>. Take a look |
175 |
+All workstations must be listed in <path>/etc/hosts</path>. Take a look |
176 |
at the example: |
177 |
-</p> |
178 |
+</p> |
179 |
|
180 |
<pre caption="/etc/hosts"> |
181 |
127.0.0.1 localhost |
182 |
@@ -249,8 +252,8 @@ |
183 |
<body> |
184 |
|
185 |
<p> |
186 |
-This is the most complicated step in my opinion, you have to create a |
187 |
-valid DHCP Config (<path>/etc/dhcp/dhcpd.conf</path>). Here is an |
188 |
+This is the most complicated step in my opinion, you have to create a |
189 |
+valid DHCP Config (<path>/etc/dhcp/dhcpd.conf</path>). Here is an |
190 |
example: |
191 |
</p> |
192 |
|
193 |
@@ -303,11 +306,13 @@ |
194 |
If your workstations support PXE, you should list each one of them as we |
195 |
have done with <e>host ws001</e> (don't forget to uncomment it). Don't |
196 |
give them an adress in the dynamic range, otherwise it would be possible |
197 |
-that more workstations have the same IP (which is troublesome). Remember, if you cut-n-paste the above example, replace any "//" comments with "##", or else dhcp will fail to start. |
198 |
+that more workstations have the same IP (which is troublesome). Remember, |
199 |
+if you cut-n-paste the above example, replace any "//" comments with "##", |
200 |
+or else dhcp will fail to start. |
201 |
</p> |
202 |
|
203 |
<p> |
204 |
-For more documentation on this item read the official dhcp handbook: |
205 |
+For more documentation on this item read the official dhcp handbook: |
206 |
<uri>http://www.dhcp-handbook.com/</uri> |
207 |
</p> |
208 |
|
209 |
@@ -326,7 +331,6 @@ |
210 |
|
211 |
</body> |
212 |
</section> |
213 |
- |
214 |
<section> |
215 |
<title>LTSP Configuration</title> |
216 |
<body> |
217 |
@@ -338,8 +342,12 @@ |
218 |
</p> |
219 |
|
220 |
<p> |
221 |
-As a few suggestions to get started, you will want to first copy <path>/opt/ltsp/i386/etc/lts.conf.example</path> to <path>/opt/ltsp/i386/etc/lts.conf</path> and edit it from there. You may want to try changing the <c>SCREEN_01</c> option to read |
222 |
-<c>SCREEN_01 = startx</c>. To use a USB mouse on the remote client, add the following MODULE lines, and change the X_MOUSE_* lines as follows: |
223 |
+As a few suggestions to get started, you will want to first copy |
224 |
+<path>/opt/ltsp/i386/etc/lts.conf.example</path> to |
225 |
+<path>/opt/ltsp/i386/etc/lts.conf</path> and edit it from there. You may want |
226 |
+to try changing the <c>SCREEN_01</c> option to read <c>SCREEN_01 = startx</c>. |
227 |
+To use a USB mouse on the remote client, add the following MODULE lines, and |
228 |
+change the X_MOUSE_* lines as follows: |
229 |
</p> |
230 |
|
231 |
<pre caption="/opt/ltsp/i386/etc/lts.conf"> |
232 |
@@ -352,13 +360,12 @@ |
233 |
|
234 |
</body> |
235 |
</section> |
236 |
- |
237 |
<section> |
238 |
<title>Displaymanager</title> |
239 |
<body> |
240 |
|
241 |
<p> |
242 |
-Now you have to change your displaymanager's configuration to |
243 |
+Now you have to change your displaymanager's configuration to |
244 |
also accept remote connections. |
245 |
</p> |
246 |
|
247 |
@@ -376,18 +383,19 @@ |
248 |
</p> |
249 |
|
250 |
<p> |
251 |
-<b>XDM</b>: In <path>/etc/X11/xdm/xdm-config</path> comment out <c>DisplayManager.requestPort: 0</c> |
252 |
+<b>XDM</b>: In <path>/etc/X11/xdm/xdm-config</path> comment out |
253 |
+<c>DisplayManager.requestPort: 0</c> |
254 |
</p> |
255 |
|
256 |
<p> |
257 |
-<b>KDM</b>: In <path>/usr/kde/3.1/share/config/kdm/kdmrc</path> look |
258 |
-for the <c>[Xdmcp]</c> section and change <c>Enable = false</c> to |
259 |
+<b>KDM</b>: In <path>/usr/kde/3.1/share/config/kdm/kdmrc</path> look |
260 |
+for the <c>[Xdmcp]</c> section and change <c>Enable = false</c> to |
261 |
<c>Enable = true</c>. |
262 |
</p> |
263 |
|
264 |
<p> |
265 |
-<b>GDM</b>: In <path>/etc/X11/gdm/gdm.conf</path> look for the |
266 |
-<c>[xdmcp]</c> section and change <c>Enable = false</c> to |
267 |
+<b>GDM</b>: In <path>/etc/X11/gdm/gdm.conf</path> look for the |
268 |
+<c>[xdmcp]</c> section and change <c>Enable = false</c> to |
269 |
<c>Enable = True</c>. |
270 |
</p> |
271 |
|
272 |
@@ -406,12 +414,12 @@ |
273 |
</warn> |
274 |
|
275 |
<p> |
276 |
-Remember, if your display manager is already running, restarting the X server via CTRL-ALT-BACKSPACE doesn't restart the display manager. |
277 |
+Remember, if your display manager is already running, restarting the X server |
278 |
+via CTRL-ALT-BACKSPACE doesn't restart the display manager. |
279 |
</p> |
280 |
|
281 |
</body> |
282 |
</section> |
283 |
- |
284 |
<section> |
285 |
<title>Creating a bootfloppy</title> |
286 |
<body> |
287 |
@@ -437,7 +445,7 @@ |
288 |
<body> |
289 |
|
290 |
<p> |
291 |
-There are a lot of things that can be the source of trouble, but there |
292 |
+There are a lot of things that can be the source of trouble, but there |
293 |
are also several resources around which help you solve your problems: |
294 |
</p> |
295 |
|
296 |
@@ -445,17 +453,18 @@ |
297 |
<li> |
298 |
The official documentation: |
299 |
<uri>http://wiki.ltsp.org/twiki/bin/view/Ltsp/Documentation</uri>, |
300 |
- especially the |
301 |
+ especially the |
302 |
<uri link="http://wiki.ltsp.org/twiki/bin/view/Ltsp/TroubleShooting"> |
303 |
Troubleshooting section</uri>. |
304 |
</li> |
305 |
-<li>The gentoo IRC channel: irc.freenode.org #gentoo</li> |
306 |
-<li>The ltsp irc channel: irc.freenode.org #ltsp</li> |
307 |
+ <li>The gentoo IRC channel: irc.freenode.org #gentoo</li> |
308 |
+ <li>The ltsp irc channel: irc.freenode.org #ltsp</li> |
309 |
<li> |
310 |
The ltsp mailinglists <uri>http://marc.info/?l=ltsp-discuss</uri> are full |
311 |
of some real good knowledge. |
312 |
</li> |
313 |
</ul> |
314 |
+ |
315 |
</body> |
316 |
</section> |
317 |
</chapter> |
318 |
@@ -464,8 +473,9 @@ |
319 |
<title>FAQ</title> |
320 |
<section> |
321 |
<body> |
322 |
+ |
323 |
<p> |
324 |
-<b>Q:</b> My workstations have Pentium II CPUs, but my server is compiled |
325 |
+<b>Q:</b> My workstations have Pentium II CPUs, but my server is compiled |
326 |
with <c>march=athlon-xp</c>, does this work? |
327 |
</p> |
328 |
|
329 |
@@ -478,7 +488,7 @@ |
330 |
</p> |
331 |
|
332 |
<p> |
333 |
-<b>A:</b> There is a good document with suggestions at |
334 |
+<b>A:</b> There is a good document with suggestions at |
335 |
<uri>http://wiki.ltsp.org/twiki/bin/view/Ltsp/ServerSizing</uri>. |
336 |
</p> |
337 |
|
338 |
@@ -487,7 +497,7 @@ |
339 |
</p> |
340 |
|
341 |
<p> |
342 |
-<b>A:</b> Yes, take a look at |
343 |
+<b>A:</b> Yes, take a look at |
344 |
<uri>http://wiki.ltsp.org/twiki/bin/view/Ltsp/PXE</uri>. |
345 |
</p> |
346 |
|
347 |
@@ -496,7 +506,7 @@ |
348 |
</p> |
349 |
|
350 |
<p> |
351 |
-<b>A:</b> If you are using NVidia cards take a look at |
352 |
+<b>A:</b> If you are using NVidia cards take a look at |
353 |
<uri>http://wiki.ltsp.org/twiki/bin/view/Ltsp/NvidiaLtsp411</uri>. |
354 |
</p> |
355 |
|
356 |
@@ -505,10 +515,10 @@ |
357 |
</p> |
358 |
|
359 |
<p> |
360 |
-<b>A:</b> You have to setup the XFontServer, add <c>USE_XFS=Y</c> to your |
361 |
-<path>lts.conf</path>, edit <path>/etc/X11/fs/config</path> and comment |
362 |
-<c>no-listen: tcp</c> out, replace <c>XFS_PORT="-1"</c> with |
363 |
-<c>XFS_PORT="7100"</c> in <path>/etc/conf.d/xfs</path> and start xfs: |
364 |
+<b>A:</b> You have to setup the XFontServer, add <c>USE_XFS=Y</c> to your |
365 |
+<path>lts.conf</path>, edit <path>/etc/X11/fs/config</path> and comment |
366 |
+<c>no-listen: tcp</c> out, replace <c>XFS_PORT="-1"</c> with |
367 |
+<c>XFS_PORT="7100"</c> in <path>/etc/conf.d/xfs</path> and start xfs: |
368 |
<c>/etc/init.d/xfs start</c>. Also doublecheck that |
369 |
<path>/etc/X11/XF86Config</path> (or <path>/etc/X11/xorg.conf</path>) contains |
370 |
<c>FontPath "unix/:7100"</c> in the Files-section. |
371 |
@@ -540,10 +550,10 @@ |
372 |
|
373 |
<p> |
374 |
<b><uri link="http://www.webopedia.com/TERM/P/PXE.html">PXE</uri></b> |
375 |
-"Short for Pre-Boot Execution Environment. Pronounced pixie, PXE is one of the |
376 |
-components of Intel's WfM specification. It allows a workstation to boot from |
377 |
-a server on a network prior to booting the operating system on the local hard |
378 |
-drive. A PXE-enabled workstation connects its NIC to the LAN via a jumper, |
379 |
+"Short for Pre-Boot Execution Environment. Pronounced pixie, PXE is one of the |
380 |
+components of Intel's WfM specification. It allows a workstation to boot from |
381 |
+a server on a network prior to booting the operating system on the local hard |
382 |
+drive. A PXE-enabled workstation connects its NIC to the LAN via a jumper, |
383 |
which keeps the workstation connected to the network even when the power is |
384 |
off." |
385 |
</p> |
386 |
|
387 |
|
388 |
|
389 |
-- |
390 |
gentoo-doc-cvs@l.g.o mailing list |