Building and Updating LTSP chroots or client images
THIS POST IS A WORK IN PROGRESS -Be Careful!
LTSP is confusing because you actually have to keep up at least 2 working linux file systems. Your server file system is under root, just like you’d expect. But the image for your clients is (ubuntu’s default) within /opt/ltsp/i386 or /opt/ltsp/amd64 (or whatever you choose to name the home folder)
You can build additional chroots with this command:
$ sudo ltsp-build-client --chroot i386_w_localapps
chroot into the image (chroot means to change your root directory so that when you install software, the software is installed in the client image and not the ltsp server)
$ sudo chroot /opt/ltsp/i386_w_localapps
$ mount -t proc proc /proc
Create a file in the root directory to remind yourself whether you’re still in the chroot or not (Do “ls /” and check for the file):
$sudo touch /thisIsMyLtspClientImage
Edit your /etc/apt/sources.list so that it is identical to your non-ltsp image source.list
Update your software (edit firefox version as necessary):
1) aptitude update && aptitude safe-upgrade
2) If Firefox updated and you’re running Jaunty or previous, you’ll need to softlink “firefox” to firefox-3.5 (adjust the firefox extension accordingly):
$ ln -s /usr/bin/firefox /usr/bin/firefox-3.5.x
3) move over the firefox defaults:
move peter.cfg and all .js from the previous /usr/bin/firefox-3.5.x to the new firefox version.
Leave the chroot and build those changes into a bootable image:
sudo ltsp-update-image -a i386_w_localapps