/[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.11 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.11 2004/10/13 17:43:44 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.8</version> 23<version>1.13</version>
24<date>October 13, 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>
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>
99<section> 115<section>
100<body> 116<body>
101 117
108<section> 124<section>
109<title>System Logger</title> 125<title>System Logger</title>
110<body> 126<body>
111 127
112<p> 128<p>
113To analyze problems easier, the system logger must be configured to 129To analyze problems easier, the system logger must be configured to
114accept remote connections. Please read the documentation of your 130accept remote connections. Please read the documentation of your
115system 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
116sysklogd, 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
117"-r" to the SYSLOGD line: 133"-r" to the SYSLOGD line:
118</p> 134</p>
127<section> 143<section>
128<title>NFS</title> 144<title>NFS</title>
129<body> 145<body>
130 146
131<p> 147<p>
132Next 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
133allow the workstations to mount the root filesystem. There should be at 149allow the workstations to mount the root filesystem. There should be at
134least two lines in it: 150least two lines in it:
135</p> 151</p>
136 152
137<pre caption="/etc/exports"> 153<pre caption="/etc/exports">
138/opt/ltsp-4.1/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)
139/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)
140</pre> 156</pre>
141 157
142<note> 158<note>
143You have to alter the network/netmask to match your network/netmask 159You have to alter the network/netmask to match your network/netmask
144settings. 160settings.
145</note> 161</note>
146 162
147<p> 163<p>
148Now start NFS. 164Now start NFS.
153# <i>/etc/init.d/nfs start</i> 169# <i>/etc/init.d/nfs start</i>
154</pre> 170</pre>
155 171
156</body> 172</body>
157</section> 173</section>
158
159<section> 174<section>
160<title>xinetd/tftp</title> 175<title>xinetd/tftp</title>
161<body> 176<body>
162<p> 177<p>
163TFTP requires a bit of configuring to get it to work properly. First, edit 178TFTP requires a bit of configuring to get it to work properly. First, edit
189 socket_type = dgram 204 socket_type = dgram
190 protocol = udp 205 protocol = udp
191 wait = yes 206 wait = yes
192 user = root 207 user = root
193 server = /usr/sbin/in.tftpd 208 server = /usr/sbin/in.tftpd
209 server_args = -s /tftpboot
194} 210}
195</pre> 211</pre>
196 212
197<p> 213<p>
198Now 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.
199</p> 216</p>
200 217
201<pre caption="Starting xinetd"> 218<pre caption="Starting xinetd">
202# <i>rc-update add xinetd default</i> 219# <i>rc-update add xinetd default</i>
203# <i>/etc/init.d/xinetd start</i> 220# <i>/etc/init.d/xinetd start</i>
216simple) 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
217systems. We are going to use the latter. 234systems. We are going to use the latter.
218</p> 235</p>
219 236
220<p> 237<p>
221All 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
222at the example: 239at the example:
223</p> 240</p>
224 241
225<pre caption="/etc/hosts"> 242<pre caption="/etc/hosts">
226127.0.0.1 localhost 243127.0.0.1 localhost
227192.168.0.254 server server.yourdomain.com 244192.168.0.254 server server.yourdomain.com
228192.168.0.1 ws001 ws001.yourdomain.com 245192.168.0.1 ws001 ws001.yourdomain.com
233<section> 250<section>
234<title>DHCP Config</title> 251<title>DHCP Config</title>
235<body> 252<body>
236 253
237<p> 254<p>
238This 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
239valid DHCP Config (<path>/etc/dhcp/dhcpd.conf</path>). Here is an 256valid DHCP Config (<path>/etc/dhcp/dhcpd.conf</path>). Here is an
240example: 257example:
241</p> 258</p>
242 259
243<pre caption = "dhcpd.conf"> 260<pre caption = "dhcpd.conf">
244<codenote>Some general options</codenote> 261<comment>(Some general options)</comment>
245default-lease-time 21600; 262default-lease-time 21600;
246max-lease-time 21600; 263max-lease-time 21600;
247use-host-decl-names on; 264use-host-decl-names on;
248ddns-update-style ad-hoc; 265ddns-update-style ad-hoc;
249 266
250<codenote>Bootp options</codenote> 267<comment>(Bootp options)</comment>
251allow booting; 268allow booting;
252allow bootp; 269allow bootp;
253 270
254<codenote>Network Options</codenote> 271<comment>(Network Options)</comment>
255option subnet-mask 255.255.255.0; 272option subnet-mask 255.255.255.0;
256option broadcast-address 192.168.0.255; 273option broadcast-address 192.168.0.255;
257option routers 192.168.0.254; 274option routers 192.168.0.254;
258option domain-name-servers 192.168.0.254; 275option domain-name-servers 192.168.0.254;
259option log-servers 192.168.0.254; 276option log-servers 192.168.0.254;
260option domain-name "yourdomain.com"; 277option domain-name "yourdomain.com";
261 278
262<codenote>LTSP Path Options</codenote> 279<comment>(LTSP Path Options)</comment>
263option root-path "192.168.0.254:/opt/ltsp-4.1/i386"; 280option root-path "192.168.0.254:/opt/ltsp-4.1/i386";
264filename "/lts/vmlinuz-2.4.26-ltsp-2"; 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;
265 284
266<codenote>If your workstations have ISA NICs uncomment the following</codenote> 285<comment>(If your workstations have ISA NICs uncomment the following)</comment>
267<codenote>lines and alter the driver and IO</codenote> 286<comment>(lines and alter the driver and IO)</comment>
268#option option-128 code 128 = string; 287#option option-128 code 128 = string;
269#option option-129 code 129 = text; 288#option option-129 code 129 = text;
270#option option-128 e4:45:74:68:00:00; 289#option option-128 e4:45:74:68:00:00;
271#option option-129 "NIC=ne IO=0x300"; 290#option option-129 "NIC=ne IO=0x300";
272 291
273shared-network WORKSTATIONS { 292shared-network WORKSTATIONS {
274 subnet 192.168.0.0 netmask 255.255.255.0 { 293 subnet 192.168.0.0 netmask 255.255.255.0 {
275 <codenote>Distribute dynamic IPs to the workstations</codenote> 294 <comment>(Distribute dynamic IPs to the workstations)</comment>
276 range dynamic-bootp 192.168.0.1 192.168.0.16; 295 range dynamic-bootp 192.168.0.1 192.168.0.16;
277 <codenote>Workstation specific configuration for PXE booting</codenote> 296 <comment>(Workstation specific configuration for PXE booting)</comment>
278 #host ws001 { 297 #host ws001 {
279 # hardware ethernet 00:E0:06:E8:00:84; 298 # hardware ethernet 00:E0:06:E8:00:84;
280 # fixed-address 192.168.0.1; 299 # fixed-address 192.168.0.1;
281 #} 300 #}
282 } 301 }
285 304
286<p> 305<p>
287If 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
288have 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
289give 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
290that 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,
291</p> 310if you cut-n-paste the above example, replace any "//" comments with "##",
292 311or else dhcp will fail to start.
293<p> 312</p>
313
314<p>
294For more documentation on this item read the official dhcp handbook: 315For more documentation on this item read the official dhcp handbook:
295<uri>http://www.dhcp-handbook.com/</uri> 316<uri>http://www.dhcp-handbook.com/</uri>
296</p> 317</p>
297 318
298<p> 319<p>
299Now start DHCP as you did with NFS and xinetd: 320Now start DHCP as you did with NFS and xinetd:
308DHCPD 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.
309</note> 330</note>
310 331
311</body> 332</body>
312</section> 333</section>
313
314<section> 334<section>
315<title>LTSP Configuration</title> 335<title>LTSP Configuration</title>
316<body> 336<body>
317 337
318<p> 338<p>
319There are many options to configure your workstations, visit 339There are many options to configure your workstations, visit
320<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>
321for 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>.
322</p> 342</p>
323 343
324<p> 344<p>
325As 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
326<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:
327</p> 351</p>
328 352
329<pre caption="/opt/ltsp/i386/etc/lts.conf"> 353<pre caption="/opt/ltsp/i386/etc/lts.conf">
330MODULE_01 = usb-uhci 354MODULE_01 = usb-uhci
331MODULE_02 = mousedev 355MODULE_02 = mousedev
334X_MOUSE_DEVICE = "/dev/input/mice" 358X_MOUSE_DEVICE = "/dev/input/mice"
335</pre> 359</pre>
336 360
337</body> 361</body>
338</section> 362</section>
339
340<section> 363<section>
341<title>Displaymanager</title> 364<title>Displaymanager</title>
342<body> 365<body>
343 366
344<p> 367<p>
345Now you have to change your displaymanager's configuration to 368Now you have to change your displaymanager's configuration to
346also accept remote connections. 369also accept remote connections.
347</p> 370</p>
348 371
349<p> 372<p>
350First change your <path>/etc/X11/xdm/Xaccess</path> file, 373First change your <path>/etc/X11/xdm/Xaccess</path> file,
358<p> 381<p>
359Now change the configuration of the displaymanager you use: 382Now change the configuration of the displaymanager you use:
360</p> 383</p>
361 384
362<p> 385<p>
363<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
364</p> 387<c>DisplayManager.requestPort: 0</c>
365
366<p> 388</p>
389
390<p>
367<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
368for 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
369<c>Enable = true</c>. 393<c>Enable = true</c>.
370</p> 394</p>
371 395
372<p> 396<p>
373<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
374<c>[xdmcp]</c> section and change <c>Enable = false</c> to 398<c>[xdmcp]</c> section and change <c>Enable = false</c> to
375<c>Enable = True</c>. 399<c>Enable = True</c>.
376</p> 400</p>
377 401
378<p> 402<p>
379Then start the displaymanager: 403Then start the displaymanager:
388There 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
389KDM to resolve these issues. 413KDM to resolve these issues.
390</warn> 414</warn>
391 415
392<p> 416<p>
393Remember, 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.
394</p> 419</p>
395 420
396</body> 421</body>
397</section> 422</section>
398
399<section> 423<section>
400<title>Creating a bootfloppy</title> 424<title>Creating a bootfloppy</title>
401<body> 425<body>
402 426
403<p> 427<p>
419<title>Troubleshooting</title> 443<title>Troubleshooting</title>
420<section> 444<section>
421<body> 445<body>
422 446
423<p> 447<p>
424There 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
425are also several resources around which help you solve your problems: 449are also several resources around which help you solve your problems:
426</p> 450</p>
427 451
428<ul> 452<ul>
453 <li>
429<li>The official documentation: 454 The official documentation:
430<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">
431Troubleshooting section.</li> 458 Troubleshooting section</uri>.
459 </li>
432<li>The gentoo IRC channel: irc.freenode.org #gentoo</li> 460 <li>The gentoo IRC channel: irc.freenode.org #gentoo</li>
433<li>The ltsp irc channel: irc.freenode.org #ltsp</li> 461 <li>The ltsp irc channel: irc.freenode.org #ltsp</li>
434<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
435are full of some real good knowledge.</li> 464 of some real good knowledge.
465 </li>
436</ul> 466</ul>
467
437</body> 468</body>
438</section> 469</section>
439</chapter> 470</chapter>
440 471
441<chapter> 472<chapter>
442<title>FAQ</title> 473<title>FAQ</title>
443<section> 474<section>
444<body> 475<body>
476
445<p> 477<p>
446<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
447with <c>march=athlon-xp</c>, does this work? 479with <c>march=athlon-xp</c>, does this work?
448</p> 480</p>
449 481
450<p> 482<p>
451<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.
454<p> 486<p>
455<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?
456</p> 488</p>
457 489
458<p> 490<p>
459<b>A:</b> There is a good document with suggestions at 491<b>A:</b> There is a good document with suggestions at
460<uri>http://ltsp.org/documentation/server_suggestions.html</uri>. 492<uri>http://wiki.ltsp.org/twiki/bin/view/Ltsp/ServerSizing</uri>.
461</p> 493</p>
462 494
463<p> 495<p>
464<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?
465</p> 497</p>
466 498
467<p> 499<p>
468<b>A:</b> Yes, take a look at 500<b>A:</b> Yes, take a look at
469<uri>http://ltsp.org/documentation/eproms.txt</uri> 501<uri>http://wiki.ltsp.org/twiki/bin/view/Ltsp/PXE</uri>.
470and <uri>http://ltsp.org/documentation/pxe.howto.html</uri>.
471</p> 502</p>
472 503
473<p> 504<p>
474<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?
475</p> 506</p>
476 507
477<p> 508<p>
478<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
479<uri>http://ltsp.org/documentation/nvidia.txt</uri>. 510<uri>http://wiki.ltsp.org/twiki/bin/view/Ltsp/NvidiaLtsp411</uri>.
480</p> 511</p>
481 512
482<p> 513<p>
483<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?
484</p> 515</p>
485 516
486<p> 517<p>
487<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
488<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
489<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
490<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:
491<c>/etc/init.d/xfs start</c>. Also doublecheck that 522<c>/etc/init.d/xfs start</c>. Also doublecheck that
492<path>/etc/X11/XF86Config</path> (or <path>/etc/X11/xorg.conf</path>) contains 523<path>/etc/X11/XF86Config</path> (or <path>/etc/X11/xorg.conf</path>) contains
493<c>FontPath "unix/:7100"</c> in the Files-section. 524<c>FontPath "unix/:7100"</c> in the Files-section.
494</p> 525</p>
495 526
517graphical or character based terminals on a GNU/Linux server." 548graphical or character based terminals on a GNU/Linux server."
518</p> 549</p>
519 550
520<p> 551<p>
521<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>
522"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
523components 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
524a 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
525drive. 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,
526which 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
527off." 558off."
528</p> 559</p>
529 560
530</body> 561</body>

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

  ViewVC Help
Powered by ViewVC 1.1.20