/[gentoo]/xml/htdocs/doc/en/ltsp.xml
Gentoo

Diff of /xml/htdocs/doc/en/ltsp.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.7 Revision 1.21
1<?xml version='1.0' encoding="UTF-8"?> 1<?xml version='1.0' encoding="UTF-8"?>
2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/Attic/ltsp.xml,v 1.7 2004/04/11 13:30:27 swift Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/Attic/ltsp.xml,v 1.21 2008/05/19 21:16:02 swift Exp $ -->
3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4 4
5<guide link="/doc/en/ltsp.xml"> 5<guide link="/doc/en/ltsp.xml">
6<title>Gentoo - LTSP Guide</title> 6<title>Gentoo - LTSP Guide</title>
7<author title="Author"> 7<author title="Author">
8 <mail link="lanius@gentoo.org">Heinrich Wendel</mail> 8 <mail link="lanius@gentoo.org">Heinrich Wendel</mail>
9</author> 9</author>
10<author title="Author"> 10<author title="Author">
11 <mail link="josiah@ritchietribe.net">Josiah Ritchie</mail> 11 <mail link="josiah@ritchietribe.net">Josiah Ritchie</mail>
12</author> 12</author>
13<author title="Editor"> 13<author title="Editor">
14 <mail link="swift@gentoo.org">Sven Vermeulen</mail> 14 <mail link="swift@gentoo.org">Sven Vermeulen</mail>
15</author> 15</author>
16 16
17<abstract> 17<abstract>
18This guide shows you how to setup a LTSP Server with Gentoo. 18This guide shows you how to setup a LTSP Server with Gentoo.
19</abstract> 19</abstract>
20 20
21<license/> 21<license/>
22 22
23<version>1.4</version> 23<version>1.13</version>
24<date>April 11, 2004</date> 24<date>2007-05-02</date>
25
25<chapter> 26<chapter>
26<title>Introduction</title> 27<title>Introduction</title>
27<section> 28<section>
28<title>What is LTSP?</title> 29<title>What is LTSP?</title>
29<body> 30<body>
31
30<p> 32<p>
31LTSP is an abbreviation for "Linux Terminal Server Project". Installed 33LTSP is an abbreviation for "Linux Terminal Server Project". Installed
32on a server it can supply many workstations (so called thin-clients) 34on a server it can supply many workstations (so called thin-clients)
33with identical environments. All applications run on the server and 35with identical environments. All applications run on the server and
34therefore you can use old PCs and convert them into XTerminals. This 36therefore you can use old PCs and convert them into XTerminals. This
35reduces costs and maintenance especially in an environment where you 37reduces costs and maintenance especially in an environment where you
36need to have an uniform workspace on each computer you login, e.g. in 38need to have an uniform workspace on each computer you login, e.g. in
37schools or firms. 39schools or firms.
38</p> 40</p>
41
39</body> 42</body>
40</section> 43</section>
41</chapter> 44</chapter>
45
42<chapter> 46<chapter>
43<title>Installation</title> 47<title>Installation</title>
44<section> 48<section>
45<title>Preliminaries</title> 49<title>Preliminaries</title>
46<body> 50<body>
51
47<p> 52<p>
48All of the examples in this document presume that your server's IP is 53All of the examples in this document presume that your server's IP is
49192.168.0.254, your domain is named yourdomain.com and your network is 54192.168.0.254, your domain is named yourdomain.com and your network is
50192.168.0.0/24. 55192.168.0.0/24.
51</p> 56</p>
57
52</body> 58</body>
53</section> 59</section>
54<section> 60<section>
55<title>Installation</title> 61<title>Installation</title>
56<body> 62<body>
60Gentoo Installation Manual for your architecture on <uri 66Gentoo Installation Manual for your architecture on <uri
61link="http://www.gentoo.org/doc">Gentoo's Documentation Website</uri>. 67link="http://www.gentoo.org/doc">Gentoo's Documentation Website</uri>.
62</p> 68</p>
63 69
64<p> 70<p>
65Then lets begin with the easiest step, installing the ltsp core 71Then lets begin with the easiest step, installing the ltsp package:
66utils:
67</p> 72</p>
68 73
69<pre caption="Emerge LTSP"> 74<pre caption="Emerge LTSP">
70# <i>emerge ltsp-core</i> 75# <i>emerge ltsp</i>
71</pre> 76</pre>
72 77
73<p> 78<p>
74This will install the following packages as dependencies: 79This will install the following packages as dependencies:
75</p> 80</p>
76 81
77<ul> 82<ul>
78<li><b>XFree</b>: They are called XTerminals, guess why :)</li> 83 <li><b>XFree</b>: They are called XTerminals, guess why :)</li>
84 <li>
79<li><b>DHCP</b>: DHCP is a protocol for automating the configuration of 85 <b>DHCP</b>: DHCP is a protocol for automating the configuration of
80computers that use TCP/IP, used by ltsp to distribute IPs to the 86 computers that use TCP/IP, used by ltsp to distribute IPs to the
81workstations.</li> 87 workstations.
88 </li>
89 <li>
82<li><b>NFS</b>: NFS is a protocol to allow access to harddisks through 90 <b>NFS</b>: NFS is a protocol to allow access to harddisks through
83the network, used by ltsp to mount a base system for the 91 the network, used by ltsp to mount a base system for the
84workstations.</li> 92 workstations.
93 </li>
94 <li>
85<li><b>TFTP</b>: TFTP is a simple file transfer protocol, used by ltsp 95 <b>TFTP</b>: TFTP is a simple file transfer protocol, used by ltsp
86to transfer the kernel to the workstations.</li> 96 to transfer the kernel to the workstations.
97 </li>
98 <li>
87<li><b>XINETD</b>: Xinetd is a powerful replacement for inetd, with 99 <b>XINETD</b>: Xinetd is a powerful replacement for inetd, with
88advanced features, used by ltsp to start tftp.</li> 100 advanced features, used by ltsp to start tftp.
101 </li>
89</ul> 102</ul>
90 103
91<note> 104<note>
92If you have the kde/gnome useflag set, it will also install a complete kde/gnome system. 105If you have the kde/gnome useflag set, it will also install a complete kde/gnome
106system.
93</note> 107</note>
94 108
95</body> 109</body>
96</section> 110</section>
97</chapter> 111</chapter>
112
98<chapter> 113<chapter>
99<title>Configuration</title> 114<title>Configuration</title>
100<section> 115<section>
101<body> 116<body>
102 117
109<section> 124<section>
110<title>System Logger</title> 125<title>System Logger</title>
111<body> 126<body>
112 127
113<p> 128<p>
114To analyze problems easier, the system logger must be configured to 129To analyze problems easier, the system logger must be configured to
115accept remote connections. Please read the documentation of your 130accept remote connections. Please read the documentation of your
116system logger on how to achieve this. If, for example, you are using 131system logger on how to achieve this. If, for example, you are using
117sysklogd, all you need to do is edit <path>/etc/conf.d/sysklogd</path> and add 132sysklogd, all you need to do is edit <path>/etc/conf.d/sysklogd</path> and add
118"-r" to the SYSLOGD line: 133"-r" to the SYSLOGD line:
119</p> 134</p>
128<section> 143<section>
129<title>NFS</title> 144<title>NFS</title>
130<body> 145<body>
131 146
132<p> 147<p>
133Next step is to edit your <path>/etc/exports</path> file, in order to 148Next step is to edit your <path>/etc/exports</path> file, in order to
134allow the workstations to mount the root filesystem. There should be at 149allow the workstations to mount the root filesystem. There should be at
135least two lines in it: 150least two lines in it:
136</p> 151</p>
137 152
138<pre caption="/etc/exports"> 153<pre caption="/etc/exports">
139/opt/ltsp/i386 192.168.0.0/255.255.255.0(ro,no_root_squash,async) 154/opt/ltsp-4.1/i386 192.168.0.0/255.255.255.0(ro,no_root_squash,async)
140/var/opt/ltsp/swapfiles 192.168.0.0/255.255.255.0(rw,no_root_squash,async) 155/var/opt/ltsp/swapfiles 192.168.0.0/255.255.255.0(rw,no_root_squash,async)
141</pre> 156</pre>
142 157
143<note> 158<note>
144You have to alter the network/netmask to match your network/netmask 159You have to alter the network/netmask to match your network/netmask
145settings. 160settings.
146</note> 161</note>
147 162
148<p> 163<p>
149Now start NFS. 164Now start NFS.
154# <i>/etc/init.d/nfs start</i> 169# <i>/etc/init.d/nfs start</i>
155</pre> 170</pre>
156 171
157</body> 172</body>
158</section> 173</section>
159
160<section> 174<section>
161<title>xinetd/tftp</title> 175<title>xinetd/tftp</title>
162<body> 176<body>
163<p> 177<p>
164TFTP requires a bit of configuring to get it to work properly. First, 178TFTP requires a bit of configuring to get it to work properly. First, edit
165edit <path>/etc/conf.d/in.tftpd</path> to set tftpd's path correctly: 179<path>/etc/conf.d/in.tftpd</path> to set tftpd's options and path correctly:
166</p> 180</p>
167 181
168<pre caption="/etc/conf.d/in.tftpd"> 182<pre caption="/etc/conf.d/in.tftpd">
169INTFTPD_PATH="/tftpboot" 183INTFTPD_PATH="/tftpboot"
170INTFTPD_OPTS="${INTFTPD_PATH}" 184INTFTPD_OPTS="-s ${INTFTPD_PATH}"
171</pre> 185</pre>
172 186
187<p>
188The -s flag specifies that TFTP is to run in secure chrooted mode
189(recommended). This means that you don't need to include the
190<path>/tftpboot</path> path for example in the DHCP configuration.
173<p> 191</p>
192
193<p>
174Next, configure xinetd to run TFTP and allow remote connections. First, 194Next, configure xinetd to run TFTP and allow remote connections. By default
175check to see if the file <path>/etc/xinetd.d/tftp</path> was created when 195TFTP won't be started by xinetd, so edit <path>/etc/xinetd.d/tftp</path> and
176you emerged tftp. By default TFTP won't be started by xinetd, so to change 196replace <c>disable=yes</c> with <c>disable=no</c>. If the file is missing just
177this edit <path>/etc/xinetd.d/tftp</path> and replace <c>disable=yes</c> with 197go ahead and create <path>/etc/xinetd.d/tftp</path> with the contents below.
178<c>disable=no</c>.
179</p> 198</p>
180 199
181<pre caption="/etc/xinetd.d/tftp"> 200<pre caption="/etc/xinetd.d/tftp">
182service tftp 201service tftp
183{ 202{
185 socket_type = dgram 204 socket_type = dgram
186 protocol = udp 205 protocol = udp
187 wait = yes 206 wait = yes
188 user = root 207 user = root
189 server = /usr/sbin/in.tftpd 208 server = /usr/sbin/in.tftpd
209 server_args = -s /tftpboot
190} 210}
191</pre> 211</pre>
192 212
193<p> 213<p>
194Now 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. 214Now edit <path>/etc/xinetd.conf</path> and comment out the line <c>only_from =
215localhost</c> by prefacing it with a <c>#</c>. Finally, start xinetd.
195</p> 216</p>
196 217
197<pre caption="Starting xinetd"> 218<pre caption="Starting xinetd">
198# <i>rc-update add xinetd default</i> 219# <i>rc-update add xinetd default</i>
199# <i>/etc/init.d/xinetd start</i> 220# <i>/etc/init.d/xinetd start</i>
212simple) is to have almost identical <path>/etc/hosts</path> files on all 233simple) is to have almost identical <path>/etc/hosts</path> files on all
213systems. We are going to use the latter. 234systems. We are going to use the latter.
214</p> 235</p>
215 236
216<p> 237<p>
217All workstations must be listed in <path>/etc/hosts</path>. Take a look 238All workstations must be listed in <path>/etc/hosts</path>. Take a look
218at the example: 239at the example:
219</p> 240</p>
220 241
221<pre caption="/etc/hosts"> 242<pre caption="/etc/hosts">
222127.0.0.1 localhost 243127.0.0.1 localhost
223192.168.0.254 server server.yourdomain.com 244192.168.0.254 server server.yourdomain.com
224192.168.0.1 ws-1 ws-1.yourdomain.com 245192.168.0.1 ws001 ws001.yourdomain.com
225</pre> 246</pre>
226 247
227</body> 248</body>
228</section> 249</section>
229<section> 250<section>
230<title>DHCP Config</title> 251<title>DHCP Config</title>
231<body> 252<body>
232 253
233<p> 254<p>
234This is the most complicated step in my opinion, you have to create a 255This is the most complicated step in my opinion, you have to create a
235valid DHCP Config (<path>/etc/dhcp/dhcpd.conf</path>). Here is an 256valid DHCP Config (<path>/etc/dhcp/dhcpd.conf</path>). Here is an
236example: 257example:
237</p> 258</p>
238 259
239<pre caption = "dhcpd.conf"> 260<pre caption = "dhcpd.conf">
240<codenote>Some general options</codenote> 261<comment>(Some general options)</comment>
241default-lease-time 21600; 262default-lease-time 21600;
242max-lease-time 21600; 263max-lease-time 21600;
243use-host-decl-names on; 264use-host-decl-names on;
244ddns-update-style ad-hoc; 265ddns-update-style ad-hoc;
245 266
246<codenote>Bootp options</codenote> 267<comment>(Bootp options)</comment>
247allow booting; 268allow booting;
248allow bootp; 269allow bootp;
249 270
250<codenote>Network Options</codenote> 271<comment>(Network Options)</comment>
251option subnet-mask 255.255.255.0; 272option subnet-mask 255.255.255.0;
252option broadcast-address 192.168.0.255; 273option broadcast-address 192.168.0.255;
253option routers 192.168.0.254; 274option routers 192.168.0.254;
254option domain-name-servers 192.168.0.254; 275option domain-name-servers 192.168.0.254;
255option log-servers 192.168.0.254; 276option log-servers 192.168.0.254;
256option domain-name "yourdomain.com"; 277option domain-name "yourdomain.com";
257 278
258<codenote>LTSP Path Options</codenote> 279<comment>(LTSP Path Options)</comment>
259option root-path "192.168.0.254:/opt/ltsp/i386"; 280option root-path "192.168.0.254:/opt/ltsp-4.1/i386";
260filename "/lts/vmlinuz-2.4.19-ltsp-1"; 281filename "/lts/vmlinuz-2.4.26-ltsp-2";
282<comment>(Address of the tftp server to download the ltsp file from)</comment>
283next-server 192.168.0.254;
261 284
262<codenote>If your workstations have ISA NICs uncomment the following</codenote> 285<comment>(If your workstations have ISA NICs uncomment the following)</comment>
263<codenote>lines and alter the driver and IO</codenote> 286<comment>(lines and alter the driver and IO)</comment>
264#option option-128 code 128 = string; 287#option option-128 code 128 = string;
265#option option-129 code 129 = text; 288#option option-129 code 129 = text;
266#option option-128 e4:45:74:68:00:00; 289#option option-128 e4:45:74:68:00:00;
267#option option-129 "NIC=ne IO=0x300"; 290#option option-129 "NIC=ne IO=0x300";
268 291
269shared-network WORKSTATIONS { 292shared-network WORKSTATIONS {
270 subnet 192.168.0.0 netmask 255.255.255.0 { 293 subnet 192.168.0.0 netmask 255.255.255.0 {
271 <codenote>Distribute dynamic IPs to the workstations</codenote> 294 <comment>(Distribute dynamic IPs to the workstations)</comment>
272 range dynamic-bootp 192.168.1.1 192.168.1.16; 295 range dynamic-bootp 192.168.0.1 192.168.0.16;
273 <codenote>Workstation specific configuration for PXE booting</codenote> 296 <comment>(Workstation specific configuration for PXE booting)</comment>
274 #host ws001 { 297 #host ws001 {
275 # hardware ethernet 00:E0:06:E8:00:84; 298 # hardware ethernet 00:E0:06:E8:00:84;
276 # fixed-address 192.168.0.1; 299 # fixed-address 192.168.0.1;
277 #} 300 #}
278 } 301 }
281 304
282<p> 305<p>
283If your workstations support PXE, you should list each one of them as we 306If your workstations support PXE, you should list each one of them as we
284have done with <e>host ws001</e> (don't forget to uncomment it). Don't 307have done with <e>host ws001</e> (don't forget to uncomment it). Don't
285give them an adress in the dynamic range, otherwise it would be possible 308give them an adress in the dynamic range, otherwise it would be possible
286that 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. 309that more workstations have the same IP (which is troublesome). Remember,
287</p> 310if you cut-n-paste the above example, replace any "//" comments with "##",
288 311or else dhcp will fail to start.
289<p> 312</p>
313
314<p>
290For more documentation on this item read the official dhcp handbook: 315For more documentation on this item read the official dhcp handbook:
291<uri>http://www.dhcp-handbook.com/</uri> 316<uri>http://www.dhcp-handbook.com/</uri>
292</p> 317</p>
293 318
294<p> 319<p>
295Now start DHCP as you did with NFS and xinetd: 320Now start DHCP as you did with NFS and xinetd:
304DHCPD needs CONFIG_PACKET and CONFIG_FILTER activated in the kernel to work. 329DHCPD needs CONFIG_PACKET and CONFIG_FILTER activated in the kernel to work.
305</note> 330</note>
306 331
307</body> 332</body>
308</section> 333</section>
309
310<section> 334<section>
311<title>LTSP Configuration</title> 335<title>LTSP Configuration</title>
312<body> 336<body>
313 337
314<p> 338<p>
315There are many options to configure your workstations, visit 339There are many options to configure your workstations, visit
316<uri>http://www.ltsp.org/documentation/ltsp-3.0-4-en.html#AEN903</uri> 340<uri>http://ltsp.mirrors.tds.net/pub/ltsp/docs/ltsp-4.1-en.html#AEN1190</uri>
317for a full description of <path>/opt/ltsp/i386/etc/lts.conf</path>. 341for a full description of <path>/opt/ltsp/i386/etc/lts.conf</path>.
318</p> 342</p>
319 343
320<p> 344<p>
321As 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 345As a few suggestions to get started, you will want to first copy
322<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: 346<path>/opt/ltsp/i386/etc/lts.conf.example</path> to
347<path>/opt/ltsp/i386/etc/lts.conf</path> and edit it from there. You may want
348to try changing the <c>SCREEN_01</c> option to read <c>SCREEN_01 = startx</c>.
349To use a USB mouse on the remote client, add the following MODULE lines, and
350change the X_MOUSE_* lines as follows:
323</p> 351</p>
324 352
325<pre caption="/opt/ltsp/i386/etc/lts.conf"> 353<pre caption="/opt/ltsp/i386/etc/lts.conf">
326MODULE_01 = usb-uhci 354MODULE_01 = usb-uhci
327MODULE_02 = mousedev 355MODULE_02 = mousedev
330X_MOUSE_DEVICE = "/dev/input/mice" 358X_MOUSE_DEVICE = "/dev/input/mice"
331</pre> 359</pre>
332 360
333</body> 361</body>
334</section> 362</section>
335
336<section> 363<section>
337<title>Displaymanager</title> 364<title>Displaymanager</title>
338<body> 365<body>
339 366
340<p> 367<p>
341Now you have to change your displaymanager's configuration to 368Now you have to change your displaymanager's configuration to
342also accept remote connections. 369also accept remote connections.
343</p> 370</p>
344 371
345<p> 372<p>
346First change your <path>Xaccess</path> file, uncomment the following line: 373First change your <path>/etc/X11/xdm/Xaccess</path> file,
374uncomment the following line:
347</p> 375</p>
348 376
349<pre caption="Xaccess"> 377<pre caption="/etc/X11/xdm/Xaccess">
350#* #any host can get a login window 378#* #any host can get a login window
351</pre> 379</pre>
352 380
353<p> 381<p>
354Now change the configuration of the displaymanager you use: 382Now change the configuration of the displaymanager you use:
355</p> 383</p>
356 384
357<p> 385<p>
358<b>XDM</b>: In <path>/etc/X11/xdm/xdm-config</path> comment out <c>DisplayManager.requestPort: 0</c> 386<b>XDM</b>: In <path>/etc/X11/xdm/xdm-config</path> comment out
359</p> 387<c>DisplayManager.requestPort: 0</c>
360
361<p> 388</p>
389
390<p>
362<b>KDM</b>: In <path>/usr/kde/3.1/share/config/kdm/kdmrc</path> look 391<b>KDM</b>: In <path>/usr/kde/3.1/share/config/kdm/kdmrc</path> look
363for the <c>[Xdmcp]</c> section and change <c>Enable = false</c> to 392for the <c>[Xdmcp]</c> section and change <c>Enable = false</c> to
364<c>Enable = true</c>. 393<c>Enable = true</c>.
365</p> 394</p>
366 395
367<p> 396<p>
368<b>GDM</b>: In <path>/etc/X11/gdm/gdm.conf</path> look for the 397<b>GDM</b>: In <path>/etc/X11/gdm/gdm.conf</path> look for the
369<c>[xdmcp]</c> section and change <c>Enable = false</c> to 398<c>[xdmcp]</c> section and change <c>Enable = false</c> to
370<c>Enable = True</c>. 399<c>Enable = True</c>.
371</p> 400</p>
372 401
373<p> 402<p>
374Then start the displaymanager: 403Then start the displaymanager:
383There seem to be problems currently with XDM and GDM. The author used 412There seem to be problems currently with XDM and GDM. The author used
384KDM to resolve these issues. 413KDM to resolve these issues.
385</warn> 414</warn>
386 415
387<p> 416<p>
388Remember, if your display manager is already running, restarting the X server via CTRL-ALT-BACKSPACE doesn't restart the display manager. 417Remember, if your display manager is already running, restarting the X server
418via CTRL-ALT-BACKSPACE doesn't restart the display manager.
389</p> 419</p>
390 420
391</body> 421</body>
392</section> 422</section>
393
394<section> 423<section>
395<title>Creating a bootfloppy</title> 424<title>Creating a bootfloppy</title>
396<body> 425<body>
397 426
398<p> 427<p>
399If you workstations don't support PXE booting, you must create a 428If your workstations don't support PXE booting, you can create a boot-floppy
400boot-floppy, which is needed to start your workstations. Go to 429which is used to start your workstations and connect to the terminal server.
401<uri>http://www.rom-o-matic.net/5.0.9/</uri>, select your NIC, press 430Go to <uri>http://www.rom-o-matic.net</uri>, select the latest version, select
402<e>Get ROM</e> and write the image to a floppy: 431your NIC, press <e>Get ROM</e> and write the image to a floppy:
403</p> 432</p>
404 433
405<pre caption="Write floppy image"> 434<pre caption="Write floppy image">
406# <i>cat nicfile.lzdsk > /dev/fd0</i> 435# <i>cat nicfile.zdsk > /dev/fd0</i>
407</pre> 436</pre>
408 437
409</body> 438</body>
410</section> 439</section>
411</chapter> 440</chapter>
414<title>Troubleshooting</title> 443<title>Troubleshooting</title>
415<section> 444<section>
416<body> 445<body>
417 446
418<p> 447<p>
419There are a lot of things that can be the source of trouble, but there 448There are a lot of things that can be the source of trouble, but there
420are also several resources around which help you solve your problems: 449are also several resources around which help you solve your problems:
421</p> 450</p>
422 451
423<ul> 452<ul>
453 <li>
424<li>The official documentation: 454 The official documentation:
425<uri>http://www.ltsp.org/documentation/</uri>, especially the 455 <uri>http://wiki.ltsp.org/twiki/bin/view/Ltsp/Documentation</uri>,
456 especially the
457 <uri link="http://wiki.ltsp.org/twiki/bin/view/Ltsp/TroubleShooting">
426Troubleshooting section.</li> 458 Troubleshooting section</uri>.
459 </li>
427<li>The gentoo IRC channel: irc.freenode.org #gentoo</li> 460 <li>The gentoo IRC channel: irc.freenode.org #gentoo</li>
428<li>The ltsp irc channel: irc.freenode.org #ltsp</li> 461 <li>The ltsp irc channel: irc.freenode.org #ltsp</li>
429<li>The ltsp mailinglists <uri>http://ltsp.org/mailinglists.php</uri> 462 <li>
463 The ltsp mailinglists <uri>http://marc.info/?l=ltsp-discuss</uri> are full
430are full of some real good knowledge.</li> 464 of some real good knowledge.
465 </li>
431</ul> 466</ul>
467
432</body> 468</body>
433</section> 469</section>
434</chapter> 470</chapter>
435 471
436<chapter> 472<chapter>
437<title>FAQ</title> 473<title>FAQ</title>
438<section> 474<section>
439<body> 475<body>
476
440<p> 477<p>
441<b>Q:</b> My workstations have Pentium II CPUs, but my server is compiled 478<b>Q:</b> My workstations have Pentium II CPUs, but my server is compiled
442with <c>march=athlon-xp</c>, does this work? 479with <c>march=athlon-xp</c>, does this work?
443</p> 480</p>
444 481
445<p> 482<p>
446<b>A:</b> This is no problem, because all applications run on the server. 483<b>A:</b> This is no problem, because all applications run on the server.
449<p> 486<p>
450<b>Q:</b> Which CPU and how much RAM should the server have? 487<b>Q:</b> Which CPU and how much RAM should the server have?
451</p> 488</p>
452 489
453<p> 490<p>
454<b>A:</b> There is a good document with suggestions at 491<b>A:</b> There is a good document with suggestions at
455<uri>http://ltsp.org/documentation/server_suggestions.html</uri>. 492<uri>http://wiki.ltsp.org/twiki/bin/view/Ltsp/ServerSizing</uri>.
456</p> 493</p>
457 494
458<p> 495<p>
459<b>Q:</b> Do you have more information about this PXE stuff? 496<b>Q:</b> Do you have more information about this PXE stuff?
460</p> 497</p>
461 498
462<p> 499<p>
463<b>A:</b> Yes, take a look at 500<b>A:</b> Yes, take a look at
464<uri>http://ltsp.org/documentation/eproms.txt</uri> 501<uri>http://wiki.ltsp.org/twiki/bin/view/Ltsp/PXE</uri>.
465and <uri>http://ltsp.org/documentation/pxe.howto.html</uri>.
466</p> 502</p>
467 503
468<p> 504<p>
469<b>Q:</b> Is it possibly to use 3D-Accelerated software on the workstations? 505<b>Q:</b> Is it possibly to use 3D-Accelerated software on the workstations?
470</p> 506</p>
471 507
472<p> 508<p>
473<b>A:</b> If you are using NVidia cards take a look at 509<b>A:</b> If you are using NVidia cards take a look at
474<uri>http://ltsp.org/documentation/nvidia.txt</uri>. 510<uri>http://wiki.ltsp.org/twiki/bin/view/Ltsp/NvidiaLtsp411</uri>.
475</p> 511</p>
476 512
477<p> 513<p>
478<b>Q:</b> In some applications the fonts look crappy, what to do? 514<b>Q:</b> In some applications the fonts look crappy, what to do?
479</p> 515</p>
480 516
481<p> 517<p>
482<b>A:</b> You have to setup the XFontServer, add <c>USE_XFS=Y</c> to your 518<b>A:</b> You have to setup the XFontServer, add <c>USE_XFS=Y</c> to your
483<path>lts.conf</path>, edit <path>/etc/X11/fs/config</path> and comment 519<path>lts.conf</path>, edit <path>/etc/X11/fs/config</path> and comment
484<c>no-listen: tcp</c> out, replace <c>XFS_PORT="-1"</c> with 520<c>no-listen: tcp</c> out, replace <c>XFS_PORT="-1"</c> with
485<c>XFS_PORT="7100"</c> in <path>/etc/conf.d/xfs</path> and start xfs: 521<c>XFS_PORT="7100"</c> in <path>/etc/conf.d/xfs</path> and start xfs:
486<c>/etc/init.d/xfs start</c>. 522<c>/etc/init.d/xfs start</c>. Also doublecheck that
523<path>/etc/X11/XF86Config</path> (or <path>/etc/X11/xorg.conf</path>) contains
524<c>FontPath "unix/:7100"</c> in the Files-section.
487</p> 525</p>
488 526
489<p> 527<p>
490<b>Q: </b> How can I use the soundcard of my workstation? 528<b>Q: </b> How can I use the soundcard of my workstation?
491</p> 529</p>
510graphical or character based terminals on a GNU/Linux server." 548graphical or character based terminals on a GNU/Linux server."
511</p> 549</p>
512 550
513<p> 551<p>
514<b><uri link="http://www.webopedia.com/TERM/P/PXE.html">PXE</uri></b> 552<b><uri link="http://www.webopedia.com/TERM/P/PXE.html">PXE</uri></b>
515"Short for Pre-Boot Execution Environment. Pronounced pixie, PXE is one of the 553"Short for Pre-Boot Execution Environment. Pronounced pixie, PXE is one of the
516components of Intel's WfM specification. It allows a workstation to boot from 554components of Intel's WfM specification. It allows a workstation to boot from
517a server on a network prior to booting the operating system on the local hard 555a server on a network prior to booting the operating system on the local hard
518drive. A PXE-enabled workstation connects its NIC to the LAN via a jumper, 556drive. A PXE-enabled workstation connects its NIC to the LAN via a jumper,
519which keeps the workstation connected to the network even when the power is 557which keeps the workstation connected to the network even when the power is
520off." 558off."
521</p> 559</p>
522 560
523</body> 561</body>

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

  ViewVC Help
Powered by ViewVC 1.1.20