/[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.4 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.4 2003/11/15 00:35:19 neysx 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
17<license/>
18 16
19<abstract> 17<abstract>
20This guide shows you how to setup a LTSP Server with Gentoo. 18This guide shows you how to setup a LTSP Server with Gentoo.
21</abstract> 19</abstract>
20
21<license/>
22
22<version>1.2</version> 23<version>1.13</version>
23<date>October 11, 2003</date> 24<date>2007-05-02</date>
25
24<chapter> 26<chapter>
25<title>Introduction</title> 27<title>Introduction</title>
26<section> 28<section>
27<title>What is LTSP?</title> 29<title>What is LTSP?</title>
28<body> 30<body>
31
29<p> 32<p>
30LTSP is an abbreviation for "Linux Terminal Server Project". Installed 33LTSP is an abbreviation for "Linux Terminal Server Project". Installed
31on a server it can supply many workstations (so called thin-clients) 34on a server it can supply many workstations (so called thin-clients)
32with identical environments. All applications run on the server and 35with identical environments. All applications run on the server and
33therefore you can use old PCs and convert them into XTerminals. This 36therefore you can use old PCs and convert them into XTerminals. This
34reduces costs and maintenance especially in an environment where you 37reduces costs and maintenance especially in an environment where you
35need 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
36schools or firms. 39schools or firms.
37</p> 40</p>
41
38</body> 42</body>
39</section> 43</section>
40</chapter> 44</chapter>
45
41<chapter> 46<chapter>
42<title>Installation</title> 47<title>Installation</title>
43<section> 48<section>
44<title>Preliminaries</title> 49<title>Preliminaries</title>
45<body> 50<body>
51
46<p> 52<p>
47All 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
48192.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
49192.168.0.0/24. 55192.168.0.0/24.
50</p> 56</p>
57
51</body> 58</body>
52</section> 59</section>
53<section> 60<section>
54<title>Installation</title> 61<title>Installation</title>
55<body> 62<body>
59Gentoo Installation Manual for your architecture on <uri 66Gentoo Installation Manual for your architecture on <uri
60link="http://www.gentoo.org/doc">Gentoo's Documentation Website</uri>. 67link="http://www.gentoo.org/doc">Gentoo's Documentation Website</uri>.
61</p> 68</p>
62 69
63<p> 70<p>
64Then lets begin with the easiest step, installing the ltsp core 71Then lets begin with the easiest step, installing the ltsp package:
65utils:
66</p> 72</p>
67 73
68<pre caption="Emerge LTSP"> 74<pre caption="Emerge LTSP">
69# <i>emerge ltsp-core</i> 75# <i>emerge ltsp</i>
70</pre> 76</pre>
71 77
72<p> 78<p>
73This will install the following packages as dependencies: 79This will install the following packages as dependencies:
74</p> 80</p>
75 81
76<ul> 82<ul>
77<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>
78<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
79computers 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
80workstations.</li> 87 workstations.
88 </li>
89 <li>
81<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
82the network, used by ltsp to mount a base system for the 91 the network, used by ltsp to mount a base system for the
83workstations.</li> 92 workstations.
93 </li>
94 <li>
84<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
85to transfer the kernel to the workstations.</li> 96 to transfer the kernel to the workstations.
97 </li>
98 <li>
86<li><b>XINETD</b>: Xinetd is a powerful replacement for inetd, with 99 <b>XINETD</b>: Xinetd is a powerful replacement for inetd, with
87advanced features, used by ltsp to start tftp.</li> 100 advanced features, used by ltsp to start tftp.
101 </li>
88</ul> 102</ul>
89 103
90<note> 104<note>
91If 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.
92</note> 107</note>
93 108
94</body> 109</body>
95</section> 110</section>
96</chapter> 111</chapter>
112
97<chapter> 113<chapter>
98<title>Configuration</title> 114<title>Configuration</title>
115<section>
99<body> 116<body>
100 117
101<p> 118<p>
102After the emerge process has finished all services must be configured: 119After the emerge process has finished all services must be configured:
103</p> 120</p>
104 121
105</body> 122</body>
123</section>
106<section> 124<section>
107<title>System Logger</title> 125<title>System Logger</title>
108<body> 126<body>
109 127
110<p> 128<p>
111To analyze problems easier, the system logger must be configured to 129To analyze problems easier, the system logger must be configured to
112accept remote connections. Please read the documentation of your 130accept remote connections. Please read the documentation of your
113system logger on how to achieve this. 131system logger on how to achieve this. If, for example, you are using
132sysklogd, all you need to do is edit <path>/etc/conf.d/sysklogd</path> and add
133"-r" to the SYSLOGD line:
134</p>
135
136<pre caption="/etc/conf.d/sysklogd">
137SYSLOGD="-m 0 -r"
138KLOGD="-c 3 -2"
114</p> 139</pre>
115 140
116</body> 141</body>
117</section> 142</section>
118<section> 143<section>
119<title>NFS</title> 144<title>NFS</title>
120<body> 145<body>
121 146
122<p> 147<p>
123Next 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
124allow the workstations to mount the root filesystem. There should be at 149allow the workstations to mount the root filesystem. There should be at
125least two lines in it: 150least two lines in it:
126</p> 151</p>
127 152
128<pre caption="/etc/exports"> 153<pre caption="/etc/exports">
129/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)
130/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)
131</pre> 156</pre>
132 157
133<note> 158<note>
134You have to alter the network/netmask to match your network/netmask 159You have to alter the network/netmask to match your network/netmask
135settings. 160settings.
136</note> 161</note>
137 162
138<p> 163<p>
139Now start NFS. 164Now start NFS.
144# <i>/etc/init.d/nfs start</i> 169# <i>/etc/init.d/nfs start</i>
145</pre> 170</pre>
146 171
147</body> 172</body>
148</section> 173</section>
149
150<section> 174<section>
151<title>xinetd/tftp</title> 175<title>xinetd/tftp</title>
152<body> 176<body>
153 177<p>
178TFTP requires a bit of configuring to get it to work properly. First, edit
179<path>/etc/conf.d/in.tftpd</path> to set tftpd's options and path correctly:
154<p> 180</p>
155By default TFTP won't be started, to change this edit 181
156<path>/etc/xinetd.d/tftp</path> and replace <c>disable=yes</c> with 182<pre caption="/etc/conf.d/in.tftpd">
157<c>disable=no</c>. Afterwards, start xinetd. 183INTFTPD_PATH="/tftpboot"
184INTFTPD_OPTS="-s ${INTFTPD_PATH}"
185</pre>
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.
191</p>
192
193<p>
194Next, configure xinetd to run TFTP and allow remote connections. By default
195TFTP won't be started by xinetd, so edit <path>/etc/xinetd.d/tftp</path> and
196replace <c>disable=yes</c> with <c>disable=no</c>. If the file is missing just
197go ahead and create <path>/etc/xinetd.d/tftp</path> with the contents below.
198</p>
199
200<pre caption="/etc/xinetd.d/tftp">
201service tftp
202{
203 disable = no
204 socket_type = dgram
205 protocol = udp
206 wait = yes
207 user = root
208 server = /usr/sbin/in.tftpd
209 server_args = -s /tftpboot
210}
211</pre>
212
213<p>
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.
158</p> 216</p>
159 217
160<pre caption="Starting xinetd"> 218<pre caption="Starting xinetd">
161# <i>rc-update add xinetd default</i> 219# <i>rc-update add xinetd default</i>
162# <i>/etc/init.d/xinetd start</i> 220# <i>/etc/init.d/xinetd start</i>
175simple) 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
176systems. We are going to use the latter. 234systems. We are going to use the latter.
177</p> 235</p>
178 236
179<p> 237<p>
180All 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
181at the example: 239at the example:
182</p> 240</p>
183 241
184<pre caption="/etc/hosts"> 242<pre caption="/etc/hosts">
185127.0.0.1 localhost 243127.0.0.1 localhost
186192.168.0.254 server server.yourdomain.com 244192.168.0.254 server server.yourdomain.com
187192.168.0.1 ws-1 ws-1.yourdomain.com 245192.168.0.1 ws001 ws001.yourdomain.com
188</pre> 246</pre>
189 247
190</body> 248</body>
191</section> 249</section>
192<section> 250<section>
193<title>DHCP Config</title> 251<title>DHCP Config</title>
194<body> 252<body>
195 253
196<p> 254<p>
197This 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
198valid DHCP Config (<path>/etc/dhcp/dhcpd.conf</path>). Here is an 256valid DHCP Config (<path>/etc/dhcp/dhcpd.conf</path>). Here is an
199example: 257example:
200</p> 258</p>
201 259
202<pre caption = "dhcpd.conf"> 260<pre caption = "dhcpd.conf">
203<codenote>Some general options</codenote> 261<comment>(Some general options)</comment>
204default-lease-time 21600; 262default-lease-time 21600;
205max-lease-time 21600; 263max-lease-time 21600;
206use-host-decl-names on; 264use-host-decl-names on;
207ddns-update-style ad-hoc; 265ddns-update-style ad-hoc;
208 266
209<codenote>Bootp options</codenote> 267<comment>(Bootp options)</comment>
210allow booting; 268allow booting;
211allow bootp; 269allow bootp;
212 270
213<codenote>Network Options</codenote> 271<comment>(Network Options)</comment>
214option subnet-mask 255.255.255.0; 272option subnet-mask 255.255.255.0;
215option broadcast-address 192.168.0.255; 273option broadcast-address 192.168.0.255;
216option routers 192.168.0.254; 274option routers 192.168.0.254;
217option domain-name-servers 192.168.0.254; 275option domain-name-servers 192.168.0.254;
218option log-servers 192.168.0.254; 276option log-servers 192.168.0.254;
219option domain-name "yourdomain.com"; 277option domain-name "yourdomain.com";
220 278
221<codenote>LTSP Path Options</codenote> 279<comment>(LTSP Path Options)</comment>
222option root-path "192.168.0.254:/opt/ltsp/i386"; 280option root-path "192.168.0.254:/opt/ltsp-4.1/i386";
223filename "/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;
224 284
225<codenote>If your workstations have ISA NICs uncomment the following</codenote> 285<comment>(If your workstations have ISA NICs uncomment the following)</comment>
226<codenote>lines and alter the driver and IO</codenote> 286<comment>(lines and alter the driver and IO)</comment>
227#option option-128 code 128 = string; 287#option option-128 code 128 = string;
228#option option-129 code 129 = text; 288#option option-129 code 129 = text;
229#option option-128 e4:45:74:68:00:00; 289#option option-128 e4:45:74:68:00:00;
230#option option-129 "NIC=ne IO=0x300"; 290#option option-129 "NIC=ne IO=0x300";
231 291
232shared-network WORKSTATIONS { 292shared-network WORKSTATIONS {
233 subnet 192.168.0.0 netmask 255.255.255.0 { 293 subnet 192.168.0.0 netmask 255.255.255.0 {
234 <codenote>Distribute dynamic IPs to the workstations</codenote> 294 <comment>(Distribute dynamic IPs to the workstations)</comment>
235 range dynamic-bootp 192.168.1.1 192.168.1.16; 295 range dynamic-bootp 192.168.0.1 192.168.0.16;
236 <codenote>Workstation specific configuration for PXE booting</codenote> 296 <comment>(Workstation specific configuration for PXE booting)</comment>
237 #host ws001 { 297 #host ws001 {
238 # hardware ethernet 00:E0:06:E8:00:84; 298 # hardware ethernet 00:E0:06:E8:00:84;
239 # fixed-address 192.168.0.1; 299 # fixed-address 192.168.0.1;
240 #} 300 #}
241 } 301 }
244 304
245<p> 305<p>
246If 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
247have 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
248give 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
249that more workstations have the same IP (which is troublesome). 309that more workstations have the same IP (which is troublesome). Remember,
250</p> 310if you cut-n-paste the above example, replace any "//" comments with "##",
251 311or else dhcp will fail to start.
252<p> 312</p>
313
314<p>
253For more documentation on this item read the official dhcp handbook: 315For more documentation on this item read the official dhcp handbook:
254<uri>http://www.dhcp-handbook.com/</uri> 316<uri>http://www.dhcp-handbook.com/</uri>
255</p> 317</p>
256 318
257<p> 319<p>
258Now start DHCP as you did with NFS and xinetd: 320Now start DHCP as you did with NFS and xinetd:
267DHCPD 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.
268</note> 330</note>
269 331
270</body> 332</body>
271</section> 333</section>
272
273<section> 334<section>
274<title>LTSP Configuration</title> 335<title>LTSP Configuration</title>
275<body> 336<body>
276 337
277<p> 338<p>
278There are many options to configure your workstations, visit 339There are many options to configure your workstations, visit
279<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>
280for 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>.
281</p> 342</p>
282 343
283</body> 344<p>
284</section> 345As a few suggestions to get started, you will want to first copy
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:
351</p>
285 352
353<pre caption="/opt/ltsp/i386/etc/lts.conf">
354MODULE_01 = usb-uhci
355MODULE_02 = mousedev
356MODULE_03 = usbmouse
357X_MOUSE_PROTOCOL = "IMPS/2"
358X_MOUSE_DEVICE = "/dev/input/mice"
359</pre>
360
361</body>
362</section>
286<section> 363<section>
287<title>Displaymanager</title> 364<title>Displaymanager</title>
288<body> 365<body>
289 366
290<p> 367<p>
291Now you have to change your displaymanager's configuration to 368Now you have to change your displaymanager's configuration to
292also accept remote connections. 369also accept remote connections.
293</p> 370</p>
294 371
295<p> 372<p>
296<b>XDM</b>: In <path>/etc/X11/xdm/xdm-config</path> comment out <c>DisplayManager.requestPort: 0</c> 373First change your <path>/etc/X11/xdm/Xaccess</path> file,
297</p> 374uncomment the following line:
298
299<p> 375</p>
376
377<pre caption="/etc/X11/xdm/Xaccess">
378#* #any host can get a login window
379</pre>
380
381<p>
382Now change the configuration of the displaymanager you use:
383</p>
384
385<p>
386<b>XDM</b>: In <path>/etc/X11/xdm/xdm-config</path> comment out
387<c>DisplayManager.requestPort: 0</c>
388</p>
389
390<p>
300<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
301for 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
302<c>Enable = true</c>. 393<c>Enable = true</c>.
303</p> 394</p>
304 395
305<p> 396<p>
306<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
307<c>[xdmcp]</c> section and change <c>Enable = false</c> to 398<c>[xdmcp]</c> section and change <c>Enable = false</c> to
308<c>Enable = True</c>. 399<c>Enable = True</c>.
309</p> 400</p>
310 401
311<p> 402<p>
312Then start the displaymanager: 403Then start the displaymanager:
320<warn> 411<warn>
321There 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
322KDM to resolve these issues. 413KDM to resolve these issues.
323</warn> 414</warn>
324 415
325</body> 416<p>
326</section> 417Remember, if your display manager is already running, restarting the X server
418via CTRL-ALT-BACKSPACE doesn't restart the display manager.
419</p>
327 420
421</body>
422</section>
328<section> 423<section>
329<title>Creating a bootfloppy</title> 424<title>Creating a bootfloppy</title>
330<body> 425<body>
331 426
332<p> 427<p>
333If 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
334boot-floppy, which is needed to start your workstations. Go to 429which is used to start your workstations and connect to the terminal server.
335<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
336<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:
337</p> 432</p>
338 433
339<pre caption="Write floppy image"> 434<pre caption="Write floppy image">
340# <i>cat nicfile.lzdsk > /dev/fd0</i> 435# <i>cat nicfile.zdsk > /dev/fd0</i>
341</pre> 436</pre>
342 437
343</body> 438</body>
344</section> 439</section>
345</chapter> 440</chapter>
346 441
347<chapter> 442<chapter>
348<title>Troubleshooting</title> 443<title>Troubleshooting</title>
444<section>
349<body> 445<body>
350 446
351<p> 447<p>
352There 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
353are also several resources around which help you solve your problems: 449are also several resources around which help you solve your problems:
354</p> 450</p>
355 451
356<ul> 452<ul>
453 <li>
357<li>The official documentation: 454 The official documentation:
358<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">
359Troubleshooting section.</li> 458 Troubleshooting section</uri>.
459 </li>
360<li>The gentoo IRC channel: irc.freenode.org #gentoo</li> 460 <li>The gentoo IRC channel: irc.freenode.org #gentoo</li>
361<li>The ltsp irc channel: irc.freenode.org #ltsp</li> 461 <li>The ltsp irc channel: irc.freenode.org #ltsp</li>
362<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
363are full of some real good knowledge.</li> 464 of some real good knowledge.
465 </li>
364</ul> 466</ul>
467
365</body> 468</body>
469</section>
366</chapter> 470</chapter>
367 471
368<chapter> 472<chapter>
369<title>FAQ</title> 473<title>FAQ</title>
474<section>
370<body> 475<body>
476
371<p> 477<p>
372<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
373with <c>march=athlon-xp</c>, does this work? 479with <c>march=athlon-xp</c>, does this work?
374</p> 480</p>
375 481
376<p> 482<p>
377<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.
380<p> 486<p>
381<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?
382</p> 488</p>
383 489
384<p> 490<p>
385<b>A:</b> There is a good document with suggestions at 491<b>A:</b> There is a good document with suggestions at
386<uri>http://ltsp.org/documentation/server_suggestions.html</uri>. 492<uri>http://wiki.ltsp.org/twiki/bin/view/Ltsp/ServerSizing</uri>.
387</p> 493</p>
388 494
389<p> 495<p>
390<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?
391</p> 497</p>
392 498
393<p> 499<p>
394<b>A:</b> Yes, take a look at 500<b>A:</b> Yes, take a look at
395<uri>http://ltsp.org/documentation/eproms.txt</uri> 501<uri>http://wiki.ltsp.org/twiki/bin/view/Ltsp/PXE</uri>.
396and <uri>http://ltsp.org/documentation/pxe.howto.html</uri>.
397</p> 502</p>
398 503
399<p> 504<p>
400<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?
401</p> 506</p>
402 507
403<p> 508<p>
404<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
405<uri>http://ltsp.org/documentation/nvidia.txt</uri>. 510<uri>http://wiki.ltsp.org/twiki/bin/view/Ltsp/NvidiaLtsp411</uri>.
406</p> 511</p>
407 512
408<p> 513<p>
409<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?
410</p> 515</p>
411 516
412<p> 517<p>
413<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
414<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
415<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
416<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:
417<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.
525</p>
526
418</p> 527<p>
528<b>Q: </b> How can I use the soundcard of my workstation?
529</p>
419 530
531<p>
532<b>A: </b> There is a ltsp-sound package in gentoo, for more instructions read
533the included <path>README</path> file.
534</p>
535
420</body> 536</body>
537</section>
421</chapter> 538</chapter>
422 539
423<chapter> 540<chapter>
424<title>Glossary</title> 541<title>Glossary</title>
542<section>
425<body> 543<body>
426 544
427<p> 545<p>
428<b><uri link="http://www.ltsp.org">LTSP</uri></b> 546<b><uri link="http://www.ltsp.org">LTSP</uri></b>
429"The LTSP provides a simple way to utilize low cost workstations as either 547"The LTSP provides a simple way to utilize low cost workstations as either
430graphical or character based terminals on a GNU/Linux server." 548graphical or character based terminals on a GNU/Linux server."
431</p> 549</p>
432 550
433<p> 551<p>
434<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>
435"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
436components 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
437a 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
438drive. 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,
439which 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
440off." 558off."
441</p> 559</p>
442 560
443</body> 561</body>
562</section>
444</chapter> 563</chapter>
445</guide> 564</guide>

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

  ViewVC Help
Powered by ViewVC 1.1.20