Page History

...

http://ubuntuforums.org/archive/index.php/t-1156240.html

...

Install and configure LTSP

if not done before configure the sources.list file to use the cache of the server:

sudo sed -i 's#http://#http://192.168.10.1:3142#g'

...

 /etc/apt/sources.list

...

sudo sed -i '

...

s#http:/#http://192.168.10.1:3142/#g' /etc/apt/sources.list.d/medibuntu.list

 Install ltsp-server-standalone:

sudo apt-get install ltsp-server-standalone

...

Edit the installation option of ltsp-build-client:

...

# The chroot architecture. 
ARCH=i386
# ubuntu-desktop and edubuntu-desktop are tested. 
# If you test with [k|x]ubuntu-desktop, edit this page and mention if it worked OK. 
# kubuntu lucid (10.10) working okay. 
FAT_CLIENT_DESKTOPS="ubuntu-desktop"
# Space separated list of programs to install. 
# The java plugin installation contained in ubuntu-restricted-extras 
# needs some special care, so let's use it as an example. 
LATE_PACKAGES=" 
 ubuntu-restricted-extras 
 gimp 
 nfs-client 
"
# This is needed to answer "yes" to the Java EULA. 
# We'll create that file in the next step. 
DEBCONF_SEEDS="/etc/ltsp/debconf.seeds"
# This uses the server apt cache to speed up downloading. 
# This locks the servers dpkg, so you can't use apt on 
# the server while building the chroot. 
MOUNT_PACKAGE_DIR="/var/cache/apt/archives/"

...

Create and edit the following file for the unattented Java and msttcorefonts installation:

...

# Do you agree with the DLJ license terms?
sun-java6-bin shared/accepted-sun-dlj-v1-1 boolean true
sun-java6-jre shared/accepted-sun-dlj-v1-1 boolean true
# In order to install this package, you must accept the license terms, the
# "TrueType core fonts for the Web EULA ". Not accepting will cancel the
# installation. Do you accept the EULA license terms?
ttf-mscorefonts-installer msttcorefonts/accepted-mscorefonts-eula boolean true

sudo ltsp-build-client --mirror http://192.168.10.1:3142/archive.ubuntu.com/ubuntuIf LTSP is install on an Oneiric system (otherwise go to the next step):

The fat client plugin blacklists some packages that don't make sense to have in a fat client chroot.

Unfortunately in Oneiric xdiagnose depends on one of those packages, apport, so the fat client plugin needs to be manually edited for ltsp-build-client to complete successfully.  

Open the following file and remove the word "apport" from line 43:

/usr/share/ltsp/plugins/ltsp-build-client/Ubuntu/030-fat-client

 Build the client (even if using the cache of the server some of the files will be downloaded on the internet, if a solution is found please update  )

sudo ltsp-build-client --mirror http://192.168.10.1:3142/archive.ubuntu.com/ubuntu

You can use the fat chroot also to run thin clients, not only fat ones. This way you can have a mix of powerful and not powerful clients, that they will become "fat" or "thin" based upon their RAM (consider fat chroot a "superset" of a thin one, so thin boot uses only a small but common part of it).  The parameter that affects the RAM threshold is:

FAT_RAM_THRESHOLD

that defaults to 300 (MB).  So if you want your client boot as FAT ones only if they have more than 800MB edit lts.conf and put:

FAT_RAM_THRESHOLD=800

Another interesting feature is have a server's directory available to all the fat clients.  For instance, to have the fat clients mount as their own /srv the /srv of the server add this parameter:

LOCAL_APPS_EXTRAMOUNTS=/srv