I have this solution running -- did require a few tweaks -- my setup notes are attached.
HTH, Lee -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Varun Sent: Monday, November 24, 2003 9:01 AM To: [EMAIL PROTECTED] Subject: [Ltsp-discuss] Ltsp On Mandrake 9.2 Hello, I've had ltsp perfectly running on Mandrake 9.1. I am trying to switch to Mandrake 9.2. Ltsp packages don't directly install on Mandrake 9.2 so I changed the version temporarily in /etc/mandrake-release. After that I could install all ltsp packages and initialze. The client are booting all right at runlevel 3. But at runlevel 5 the screen comes crashes. All my configs are the same as previously for Mandrake 9.1. Thanks Varun ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.netTitle: LTSP Setup
Linux Terminal Server & Workstation Setup
Lee HughesNovember 21, 2003
Overview
This document describes how to setup up the ltsp.org terminal server on a Mandrake 9.2 server and how to bring up a new thin-client workstation.In my environment, I have the server at 172.17.17.201 and the workstations at 172.17.17.202-20x. Adjust the instructions below for your physical network setup.
Server Setup
Follow the instructions in the Mandrake/ltsp how-to at http://ltsp.sourceforge.net/documentation/mandrake_ltsp.html. Then follow the additional instructions below and restart the DHCP, NFS, and XINETD services.NOTE: Disable the firewall on the LTSP server. It will prevent the workstations from booting unless you configure it correctly, and you don't need one because you already have a firewall on the Internet connection, right?
ltsp_core Installation
On my server I got the message "Sorry but Mandrake version 9.2 not supported" when installing the ltsp_core rpm. Seems to work though. ;)dhcpd.conf
I ran into many problems having both the LTSP server and Windows DHCP
server on the same LAN. Supposedly there are settings in dhcpd.conf that
will force the thin-clients to ignore the Windows DHCP server and only
talk to the LTSP server, but they didn't work for me. So I applied the
KISS principle and replaced the Windows DHCP server with the LTSP DHCP
server -- so the LTSP server not only assigns fixed IP addresses to the
thin-client workstations, it also assigns dynamic IP addresses to
Windows clients on the LAN. BE SURE
TO TEST THE LTSP DHCP SERVER WITH WINDOWS CLIENTS WHILE THE LTSP SERVER
IS DISCONNECTED FROM THE MAIN LAN (USING A SMALL SWITCH BETWEEN THE
TEST WORKSTATIONS AND THE LTSP SERVER), AND REPLACE THE WINDOWS DHCP
SERVER AFTER HOURS, AND REBOOT ALL WINDOWS WORKSTATIONS TO MAKE SURE
THEY GET LAN AND INTERNET CONNECTIONS. Here is my /etc/dhcpd.conf file:
ddns-update-style none;
option subnet-mask 255.255.0.0;
option broadcast-address 172.17.255.255;
# default Internet gateway -- should match Router entry in Windows DHCP
option routers 172.17.17.100;
# DNS server -- should match DNS Servers entry in Windows DHCP
option domain-name-servers 172.17.17.225;
# Local domain name -- should match Domain Name entry in Windows DHCP
option domain-name "owens.owensforestproducts.com";
# NBNS server -- should match WINS/NBNS Server entry in Windows DHCP
option netbios-name-servers 172.17.17.225;
option netbios-node-type 8;
option root-path "172.17.17.201:/opt/ltsp/i386";
shared-network WORKSTATIONS {
subnet 172.17.0.0 netmask 255.255.0.0 {
# non-thin-client IP address range -- should match Address Pool in Windows DHCP
range 172.17.17.10 172.17.17.30;
}
}
# thin-client workstation properties
group {
use-host-decl-names on;
option log-servers 172.17.17.201;
host ws001 {
hardware ethernet 00:04:5A:67:21:8C;
fixed-address 172.17.17.202;
filename "/lts/vmlinuz-2.4.21-ltsp-1";
}
}
lts.conf
Here is my /opt/ltsp/i386/etc/lts.conf file:#
# Config file for the Linux Terminal Server Project (www.ltsp.org)
#
[Default]
SERVER = 172.17.17.201
XSERVER = auto
X_MOUSE_PROTOCOL = "PS/2"
X_MOUSE_DEVICE = "/dev/psaux"
X_MOUSE_RESOLUTION = 400
X_MOUSE_BUTTONS = 3
USE_XFS = N
LOCAL_APPS = N
RUNLEVEL = 5
#------------------------------------------------------------------------------
#
[ws001]
XF86CONFIG_FILE=XF86Config-4.ws001
Note the last line specifies a custom XF86Config file for ws001 -- more on this later in Workstation Setup.
kdmrc
Be sure to edit /usr/share/config/kdm/kdmrc and change Enable to "true" under the [Xdmcp] section -- otherwise you will not get a graphical login screen on the workstations.tftp Configuration
Edit the file /etc/xinetd.d/tftp and change the server_args line to -s /tftpboot or the workstations will not find the correct root directory on the server.NFS Configuration
Add exports for /tftpboot/lts and /opt/ltsp/i386 in /etc/exports or the workstations will not be able to mount these directories. Webmin is a great tool for adding these paths with the correct syntax./etc/hosts
Add a line for each workstation. Here is my /etc/hosts file:172.17.17.202 ws001 ws001.owens.owensforestproducts.com
172.17.17.201 ltsp_server
127.0.0.1 localhost
Workstation Setup
Follow the instructions below for each workstation you want to connect to the terminal server.- Boot the workstation with a Knoppix CD (version 3.3 as of this writing).
- Verify that you have a network connection and can read/write
from/to the floppy drive. Resolve any problems found.
- Open a console and enter dmesg. This displays the boot messages. Look for the loading of the network drivers. On my workstation the lines looked like
...
00:0f.0: 3Com PCI 3c905B Cyclone 100baseTx at 0x1400. Vers LK1.1.18-ac 00:50:04:73:3a:5a, IRQ 5
- The information we're interested in here is the network driver
name (3c59x) and the MAC address of the network card
(00:50:04:73:3a:5a). You can verify the driver name by entering lsmod -- if you have a network
connection the name of the network driver will appear on one of the
lines.
- Copy /etc/X11/XF86Config-4 to a floppy with mcopy /etc/X11/XF86Config-4 a:\
- Bring up a browser on another machine and go to rom-o-matic.org
- Follow the form to create and download the boot floppy image for
the network driver you identified above, and copy it to floppy per the
instructions in the Mandrake/ltsp
how-to. You don't need to customize the boot image on
rom-o-matic -- just take the defaults.
- Boot the workstation from the new floppy and verify the MAC
address is the same one you found in #3 above.
- Copy the XF86Config-4 file from #4 to the server at /opt/ltsp/i386/etc/XF86Config-4.wsXXX where XXX is the workstation number, e.g., 001.
- Edit /opt/ltsp/i386/etc/lts.conf on the server and add an entry for the new workstation, similar to the one shown in Server Setup above.
- Edit /etc/dhcpd.conf on the server and add an entry for the new workstation using the MAC address from #7, similar to the one shown in Server Setup above.
- Edit /etc/hosts and add an entry for the new workstation, similar to the one shown in Server Setup above.
- Restart the DHCP, NFS, and XINETD services on the server.
- Boot the workstation from floppy. Flame me if you don't get a
graphical login.
