Differences between revisions 41 and 42
Revision 41 as of 2006-02-19 11:32:14
Size: 8471
Editor: 203-206-49-178
Comment: added a sudo and corrected a spelling mistake
Revision 42 as of 2006-03-04 15:49:17
Size: 8671
Editor: p5089CA24
Comment: added warning for edubuntu users
Deletions are marked like this. Additions are marked like this.
Line 38: Line 38:

Please dont use this Howto if you installed Edubuntu from CD, since the Installer does nearly all of the work described here already, if you use Edubuntu, follow the EdubuntuInstallNotes wikipage.

What is a Thin Client?

To the user, a thin client behaves like a regular desktop computer. To the administrator, a thin client has no storage of its own, is easy to maintain, and can give the user a modern computing experience even with ancient hardware.

How do thin clients work?

Thin clients are computers that load and run most of their programs from a central server, but are displayed on the thin client's screen. In more technical terms, the thin client can either obtain a kernel from local storage, or load the kernel across the network. (Using these instructions, you will collect the linux kernel from the server using a bootable network card. This way, the thin client needs no more storage than the boot rom built into a bootable network card.)

Boot sequence

The PXE network card makes a DHCP request on the local network. The DHCP reply gives information to the card where to collect the linux kernel from. The kernel is collected over the network through the TFTP protocol.

Once the kernel has been collected via TFTP, the kernel is executed; the machine boots linux. A initramfs collected with the linux kernel is mounted as a root file system. This carries and autodetect the necessary drivers for the network card, mouse, keyboard sound etc. Once the network card driver is loaded, a second DHCP request tells the client it's ip address, netmask, gateway, DNS server, and root NFS (Network File System) mount point.

The linux kernel runs the ubuntu initramfs, which mounts the root NFS share from the server onto the thin client read-only. The thin client now has a booted linux kernel, and a root file system, much like any Linux system. From now on, when we talk of the root file system on the client, we are actually talking about a root file system mounted read-only from the server. The root file system mounted by the thin client is not the same root file system the server itself uses, but is specially prepared for thin clients, and is shared by all thin clients connected to the server (located in /opt/ltsp/<arch> on the server) . The initramfs calls the init program, the Xserver settings are autodetected and the ubuntu breezy ltsp login manager, called ldm is started.

X nuts and bolts

After logging in, ldm starts a ssh tunnel and executes a X session on the server which is displayed through the tunnel on the thin clients X server. Using ssh here has the big advantage that you dont need to have a Xserver configured on the client and no unsafe tcp X transport is initialized like it was done in older days of ltsp.


You will need:

  • An Ubuntu 5.10 system to be the server
  • At least one PXE-bootable system to be a client
  • A bunch of disk space
  • A fast network connection, or a local Breezy mirror, or some patience
  • A DHCP server which is capable of supporting PXE clients, or a separate network segment where you can run a dedicated DHCP server
  • Command-line familiarity
  • A sense of adventure
  • A burning desire to send feedback to [ ubuntu-devel]


Please dont use this Howto if you installed Edubuntu from CD, since the Installer does nearly all of the work described here already, if you use Edubuntu, follow the EdubuntuInstallNotes wikipage.

The Ubuntu Breezy LTSP implementation is the new upcoming standard for LTSP and gets adopted by LTSP upstream under the codename MueCow since it is a very young implementation not all parameters LTSP 4.1 had are supported yet, nontheless you can use most solutions (like local device support or sound etc.) provided at See [EdubuntuLtsConfParams] for lts.conf options which are and are not supported. For some of the features that are planned/being worked on for default integration see:

  1. ["ThinClientAudioSupport"]

  2. ["ThinClientFasterStartup"]

  3. ["ThinClientLocalDevices"]

  4. ["ThinClientLocalDevicesForwardConnection"]

  5. ["ThinClientMemoryUsage"]

Do not use the tools ltspadm and ltspcfg with this implementation of LTSP, it will for sure ruin the ltsp setup !!!

Getting Started

NOTE: If you plan to use the server as gateway/nat/firewall machine, it is strongly suggested to configure all the network interfaces before proceeding with the following steps.

  1. Set up the DHCP server
    • If you have an existing DHCP server which can support PXE clients:
      • Configure it to pass a boot filename of /ltsp/pxelinux.0 and a root path of /opt/ltsp/i386

      • For ISC DHCPD, use the following options:

        filename "/ltsp/pxelinux.0";
        option root-path "/opt/ltsp/i386";
      • Install ltsp-server on the server: {{{sudo apt-get install ltsp-server


  • If you want to run a dedicated DHCP server on the thin client server:
    1. Install ltsp-server-standalone on the server: {{{sudo apt-get install ltsp-server-standalone


  1. If necessary, customize /etc/ltsp/dhcpd.conf (by default it's configured for a server at serving PXE clients)

  2. If you are running a firewall on the server, you'll need to open TFTP and NFS (and DHCP if you're running the standalone server). Also, make sure portmap isn't limited to the loopback interface in /etc/default/portmap (comment out the line with "-i") if it exists, could be a leftover from Hoary. You also may want to edit `/etc/hosts.allow' and limit access for portmap, rpc.mountd, rpc.statd, and in.tftpd to the local network: {{{portmap:

rpc.mountd: rpc.statd: in.tftpd:}}}

  1. Restart the nfs subsystem: {{{sudo invoke-rc.d nfs-kernel-server restart

sudo invoke-rc.d nfs-common restart sudo invoke-rc.d portmap restart}}}

  1. Build the thin client runtime environment: {{{sudo ltsp-build-client


  • This script is hardcoded to use a particular Ubuntu mirror, so you may wish to edit it if you have a nearby mirror or CD (sudo ltsp-build-client --mirror file:///cdrom), remember to copy sources.list from the server into the chroot)

  • If you changed your aptitude dependency-settings not to select recommended packages automatically, not all required packages will be downloaded and installed by this script. Then no login with sdm is possible for example because some parts of the x-server are missing
  1. {{{sudo apt-get install openssh-server

sudo ltsp-update-sshkeys}}} Check /opt/ltsp/i386/etc/ssh/ssh_known_hosts and ensure that your host key is associated with your host's IP address. Depending on your /etc/hosts configuration, this may not always be correct automatically (yet). If it looks like this:

servername ssh-rsa AAAAB3NzaC1yc2EAAAABI...

then add the IP address like this:

servername, ssh-rsa AAAAB3NzaC1yc2EAAAABI...

AND file a bug in [ Malone]. THIS SHOULD NOT HAPPEN.

  1. {{{sudo invoke-rc.d dhcp3-server start


  1. Optionally, create /opt/ltsp/i386/etc/lts.conf. If you don't create one, reasonable defaults and auto-detected values will be used. Note: Not all options are supported (see [EdubuntuLtsConfParams]).

  2. PXE boot the client and see what happens. If all goes well, you should see a graphical login dialog.
  3. If your client doesn't have PXE on the network card, you can generate a custom boot CD or floppy at []. Burn the iso or floppy image and boot from that.

  4. Log in, with any user authorized to login remotely via ssh, and see what happens. If all goes well, you should get a working desktop session on the server.
  5. Send mail to [ ubuntu-devel] with your findings


If you have a separate DHCP that you do not want to install LTSP on you can just redirect the thin-client to boot off a different server.

In your DHCP server's dhcpd.conf: {{{next-server; }}} where is the address of your LTSP server


  • [ Bug 19407]: OpenSSH doesn't appear to release ports used for X forwarding in a timely manner, preventing you from logging out and logging back in immediately when IPv6 support is enabled. Disable it by adding "AddressFamily inet" to /etc/ssh/sshd_config, and restarting the openssh daemon.


  1. ["ThinClientHowtoNAT"]


ThinClientHowto (last edited 2008-08-06 16:14:39 by localhost)