swift 08/05/19 21:16:02 Modified: ltsp.xml Log: Last coding style for today, nite folks
Revision Changes Path 1.21 xml/htdocs/doc/en/ltsp.xml file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/ltsp.xml?rev=1.21&view=markup plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/ltsp.xml?rev=1.21&content-type=text/plain diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/ltsp.xml?r1=1.20&r2=1.21 Index: ltsp.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/ltsp.xml,v retrieving revision 1.20 retrieving revision 1.21 diff -u -r1.20 -r1.21 --- ltsp.xml 3 May 2007 05:56:27 -0000 1.20 +++ ltsp.xml 19 May 2008 21:16:02 -0000 1.21 @@ -1,17 +1,17 @@ <?xml version='1.0' encoding="UTF-8"?> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/ltsp.xml,v 1.20 2007/05/03 05:56:27 nightmorph Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/ltsp.xml,v 1.21 2008/05/19 21:16:02 swift Exp $ --> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> <guide link="/doc/en/ltsp.xml"> <title>Gentoo - LTSP Guide</title> <author title="Author"> - <mail link="[EMAIL PROTECTED]">Heinrich Wendel</mail> + <mail link="[EMAIL PROTECTED]">Heinrich Wendel</mail> </author> <author title="Author"> - <mail link="[EMAIL PROTECTED]">Josiah Ritchie</mail> + <mail link="[EMAIL PROTECTED]">Josiah Ritchie</mail> </author> <author title="Editor"> - <mail link="[EMAIL PROTECTED]">Sven Vermeulen</mail> + <mail link="[EMAIL PROTECTED]">Sven Vermeulen</mail> </author> <abstract> @@ -30,18 +30,19 @@ <body> <p> -LTSP is an abbreviation for "Linux Terminal Server Project". Installed -on a server it can supply many workstations (so called thin-clients) -with identical environments. All applications run on the server and -therefore you can use old PCs and convert them into XTerminals. This -reduces costs and maintenance especially in an environment where you -need to have an uniform workspace on each computer you login, e.g. in +LTSP is an abbreviation for "Linux Terminal Server Project". Installed +on a server it can supply many workstations (so called thin-clients) +with identical environments. All applications run on the server and +therefore you can use old PCs and convert them into XTerminals. This +reduces costs and maintenance especially in an environment where you +need to have an uniform workspace on each computer you login, e.g. in schools or firms. </p> </body> </section> </chapter> + <chapter> <title>Installation</title> <section> @@ -49,8 +50,8 @@ <body> <p> -All of the examples in this document presume that your server's IP is -192.168.0.254, your domain is named yourdomain.com and your network is +All of the examples in this document presume that your server's IP is +192.168.0.254, your domain is named yourdomain.com and your network is 192.168.0.0/24. </p> @@ -81,32 +82,34 @@ <ul> <li><b>XFree</b>: They are called XTerminals, guess why :)</li> <li> - <b>DHCP</b>: DHCP is a protocol for automating the configuration of - computers that use TCP/IP, used by ltsp to distribute IPs to the + <b>DHCP</b>: DHCP is a protocol for automating the configuration of + computers that use TCP/IP, used by ltsp to distribute IPs to the workstations. </li> <li> - <b>NFS</b>: NFS is a protocol to allow access to harddisks through - the network, used by ltsp to mount a base system for the + <b>NFS</b>: NFS is a protocol to allow access to harddisks through + the network, used by ltsp to mount a base system for the workstations. </li> <li> - <b>TFTP</b>: TFTP is a simple file transfer protocol, used by ltsp + <b>TFTP</b>: TFTP is a simple file transfer protocol, used by ltsp to transfer the kernel to the workstations. </li> <li> - <b>XINETD</b>: Xinetd is a powerful replacement for inetd, with + <b>XINETD</b>: Xinetd is a powerful replacement for inetd, with advanced features, used by ltsp to start tftp. </li> </ul> <note> -If you have the kde/gnome useflag set, it will also install a complete kde/gnome system. +If you have the kde/gnome useflag set, it will also install a complete kde/gnome +system. </note> </body> </section> </chapter> + <chapter> <title>Configuration</title> <section> @@ -123,7 +126,7 @@ <body> <p> -To analyze problems easier, the system logger must be configured to +To analyze problems easier, the system logger must be configured to accept remote connections. Please read the documentation of your system logger on how to achieve this. If, for example, you are using sysklogd, all you need to do is edit <path>/etc/conf.d/sysklogd</path> and add @@ -142,8 +145,8 @@ <body> <p> -Next step is to edit your <path>/etc/exports</path> file, in order to -allow the workstations to mount the root filesystem. There should be at +Next step is to edit your <path>/etc/exports</path> file, in order to +allow the workstations to mount the root filesystem. There should be at least two lines in it: </p> @@ -153,7 +156,7 @@ </pre> <note> -You have to alter the network/netmask to match your network/netmask +You have to alter the network/netmask to match your network/netmask settings. </note> @@ -168,7 +171,6 @@ </body> </section> - <section> <title>xinetd/tftp</title> <body> @@ -209,7 +211,8 @@ </pre> <p> -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. +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. </p> <pre caption="Starting xinetd"> @@ -232,9 +235,9 @@ </p> <p> -All workstations must be listed in <path>/etc/hosts</path>. Take a look +All workstations must be listed in <path>/etc/hosts</path>. Take a look at the example: -</p> +</p> <pre caption="/etc/hosts"> 127.0.0.1 localhost @@ -249,8 +252,8 @@ <body> <p> -This is the most complicated step in my opinion, you have to create a -valid DHCP Config (<path>/etc/dhcp/dhcpd.conf</path>). Here is an +This is the most complicated step in my opinion, you have to create a +valid DHCP Config (<path>/etc/dhcp/dhcpd.conf</path>). Here is an example: </p> @@ -303,11 +306,13 @@ If your workstations support PXE, you should list each one of them as we have done with <e>host ws001</e> (don't forget to uncomment it). Don't give them an adress in the dynamic range, otherwise it would be possible -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. +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. </p> <p> -For more documentation on this item read the official dhcp handbook: +For more documentation on this item read the official dhcp handbook: <uri>http://www.dhcp-handbook.com/</uri> </p> @@ -326,7 +331,6 @@ </body> </section> - <section> <title>LTSP Configuration</title> <body> @@ -338,8 +342,12 @@ </p> <p> -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 -<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: +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 <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: </p> <pre caption="/opt/ltsp/i386/etc/lts.conf"> @@ -352,13 +360,12 @@ </body> </section> - <section> <title>Displaymanager</title> <body> <p> -Now you have to change your displaymanager's configuration to +Now you have to change your displaymanager's configuration to also accept remote connections. </p> @@ -376,18 +383,19 @@ </p> <p> -<b>XDM</b>: In <path>/etc/X11/xdm/xdm-config</path> comment out <c>DisplayManager.requestPort: 0</c> +<b>XDM</b>: In <path>/etc/X11/xdm/xdm-config</path> comment out +<c>DisplayManager.requestPort: 0</c> </p> <p> -<b>KDM</b>: In <path>/usr/kde/3.1/share/config/kdm/kdmrc</path> look -for the <c>[Xdmcp]</c> section and change <c>Enable = false</c> to +<b>KDM</b>: In <path>/usr/kde/3.1/share/config/kdm/kdmrc</path> look +for the <c>[Xdmcp]</c> section and change <c>Enable = false</c> to <c>Enable = true</c>. </p> <p> -<b>GDM</b>: In <path>/etc/X11/gdm/gdm.conf</path> look for the -<c>[xdmcp]</c> section and change <c>Enable = false</c> to +<b>GDM</b>: In <path>/etc/X11/gdm/gdm.conf</path> look for the +<c>[xdmcp]</c> section and change <c>Enable = false</c> to <c>Enable = True</c>. </p> @@ -406,12 +414,12 @@ </warn> <p> -Remember, if your display manager is already running, restarting the X server via CTRL-ALT-BACKSPACE doesn't restart the display manager. +Remember, if your display manager is already running, restarting the X server +via CTRL-ALT-BACKSPACE doesn't restart the display manager. </p> </body> </section> - <section> <title>Creating a bootfloppy</title> <body> @@ -437,7 +445,7 @@ <body> <p> -There are a lot of things that can be the source of trouble, but there +There are a lot of things that can be the source of trouble, but there are also several resources around which help you solve your problems: </p> @@ -445,17 +453,18 @@ <li> The official documentation: <uri>http://wiki.ltsp.org/twiki/bin/view/Ltsp/Documentation</uri>, - especially the + especially the <uri link="http://wiki.ltsp.org/twiki/bin/view/Ltsp/TroubleShooting";> Troubleshooting section</uri>. </li> -<li>The gentoo IRC channel: irc.freenode.org #gentoo</li> -<li>The ltsp irc channel: irc.freenode.org #ltsp</li> + <li>The gentoo IRC channel: irc.freenode.org #gentoo</li> + <li>The ltsp irc channel: irc.freenode.org #ltsp</li> <li> The ltsp mailinglists <uri>http://marc.info/?l=ltsp-discuss</uri> are full of some real good knowledge. </li> </ul> + </body> </section> </chapter> @@ -464,8 +473,9 @@ <title>FAQ</title> <section> <body> + <p> -<b>Q:</b> My workstations have Pentium II CPUs, but my server is compiled +<b>Q:</b> My workstations have Pentium II CPUs, but my server is compiled with <c>march=athlon-xp</c>, does this work? </p> @@ -478,7 +488,7 @@ </p> <p> -<b>A:</b> There is a good document with suggestions at +<b>A:</b> There is a good document with suggestions at <uri>http://wiki.ltsp.org/twiki/bin/view/Ltsp/ServerSizing</uri>. </p> @@ -487,7 +497,7 @@ </p> <p> -<b>A:</b> Yes, take a look at +<b>A:</b> Yes, take a look at <uri>http://wiki.ltsp.org/twiki/bin/view/Ltsp/PXE</uri>. </p> @@ -496,7 +506,7 @@ </p> <p> -<b>A:</b> If you are using NVidia cards take a look at +<b>A:</b> If you are using NVidia cards take a look at <uri>http://wiki.ltsp.org/twiki/bin/view/Ltsp/NvidiaLtsp411</uri>. </p> @@ -505,10 +515,10 @@ </p> <p> -<b>A:</b> You have to setup the XFontServer, add <c>USE_XFS=Y</c> to your -<path>lts.conf</path>, edit <path>/etc/X11/fs/config</path> and comment -<c>no-listen: tcp</c> out, replace <c>XFS_PORT="-1"</c> with -<c>XFS_PORT="7100"</c> in <path>/etc/conf.d/xfs</path> and start xfs: +<b>A:</b> You have to setup the XFontServer, add <c>USE_XFS=Y</c> to your +<path>lts.conf</path>, edit <path>/etc/X11/fs/config</path> and comment +<c>no-listen: tcp</c> out, replace <c>XFS_PORT="-1"</c> with +<c>XFS_PORT="7100"</c> in <path>/etc/conf.d/xfs</path> and start xfs: <c>/etc/init.d/xfs start</c>. Also doublecheck that <path>/etc/X11/XF86Config</path> (or <path>/etc/X11/xorg.conf</path>) contains <c>FontPath "unix/:7100"</c> in the Files-section. @@ -540,10 +550,10 @@ <p> <b><uri link="http://www.webopedia.com/TERM/P/PXE.html";>PXE</uri></b> -"Short for Pre-Boot Execution Environment. Pronounced pixie, PXE is one of the -components of Intel's WfM specification. It allows a workstation to boot from -a server on a network prior to booting the operating system on the local hard -drive. A PXE-enabled workstation connects its NIC to the LAN via a jumper, +"Short for Pre-Boot Execution Environment. Pronounced pixie, PXE is one of the +components of Intel's WfM specification. It allows a workstation to boot from +a server on a network prior to booting the operating system on the local hard +drive. A PXE-enabled workstation connects its NIC to the LAN via a jumper, which keeps the workstation connected to the network even when the power is off." </p> -- [email protected] mailing list
