Last modified 5 years ago Last modified on 08/11/11 07:52:51


This page is kept for historical purposes. We do not recommend trying this. It doesn't work very well.


LTSP5 enabled by these instructions on a RHEL5 server is reasonably stable for basic thin clients, but local storage and sound do not work. Warren considers RHEL5-based LTSP to be a dead end. Please see K12Linux EL6 for the next generation of long-term supported LTSP.


  1. The client chroot is Fedora 9. Too many changes are necessary to make RHEL5 work as a client.
  2. ltsp-build-client cannot run on RHEL5 because it needs newer libraries than what are available. So I provide a pre-built Fedora 9 client chroot in a 155MB tarball. See instructions below.
  3. Bug #456294: ltspfs (local storage devices) is broken. Actually, it might work if the user is added to the fuse group. I haven't tested this yet. Anybody?
  4. Bug #456295: Sound doesn't work.

Install Instructions

  1. Enable EPEL on your RHEL5 machine first.
    ### Add the EPEL repository - Extra Packages for Enterprise Linux
    # rpm -Uhv
  2. Install This tells your yum to use the temporary RHEL5 k12linux repo.
    ### Add the temporary RHEL5 k12linux repository
    # wget
    # rpm -Uhv k12linux-temp-release-5-1.el5.noarch.rpm
  3. Install the ltsp-server package and its prerequisites
    # yum install ltsp-server
  4. Configure the server exactly as described in with one exception:
    1. put stuff here
    2. put more stuff here
    3. Instead of using ltsp-build-client, you must untar the client chroot.

      I provide the client chroot here: (UPDATE: The original download link is gone. You could try this newer one, but it is UNTESTED on RHEL5.)
      # cd /opt/ltsp
      # wget
      # tar xfvj i386-client-chroot-f10-20090206.tar.bz2
      # ltsp-update-sshkeys
      # ltsp-update-kernels

Reasons why a full featured backport of LTSP5 for RHEL5 is a dead end

  1. RHEL5-based client chroot was not possible primarily because mkinitrd changes necessary for automatic network driver loading are too large and invasive. It would require using modprobe instead of insmod which could have too many unknown implications for a 7-year stable supported distribution.
  2. RHEL5 lacks fuse necessary on the server. The above repos provide a totally unsupported dkms-fuse package so it at least has a chance of working, but this is highly distasteful.
  3. RHEL5 openssh lacks the new sftp-server statvfs stuff added only recently to openssh-5.1. This is necessary for sshfs mounted home dirs to support applications like firefox for local applications.

Please ask the mailing list if you have any questions or comments.