On 28 August 2012 06:56, Alkis Georgopoulos <[email protected]> wrote: > For the LTSP use case, another possible workaround for post-12.10 releases: > * In the last stages of installation, copy the whole /target system to > /target/opt/ltsp/i386, > * Chroot to /target/opt/ltsp/i386 and install ltsp-client and ldm, > * Run /target/opt/ltsp/i386/usr/share/ltsp/cleanup to remove the user > account that was created, regenerate dbus machine id etc, > * Install ltsp-server to /target, > * And run /target/ltsp-update-image to generate a squashfs image in > /target/opt/ltsp/images/i386.img out of the fat chroot in > /target/opt/ltsp/i386. > > This changes the default LTSP chroot to one that supports fat+thin > clients (instead of only thins), but with the current trends that > require 3d acceleration on desktops, that's probably a good thing. > > And it only requires minimal network connectivity to generate the > chroot, or a couple of MB of packages in the installation media > (ltsp-server, ltsp-client, ldm). >
This sounds very ubiquity friendly. We would probably install ltsp-server, ltsp-client & ldm in the squashfs, and remove them as needed (this is what ubiquity currently does). Then an ltsp installation plugin needs to be added that can do the rest of the steps =) Copied to prevent disappearing: https://blueprints.launchpad.net/ubuntu/+spec/foundations-r-ubiquity-ltsp Regards, Dmitrijs. -- ubuntu-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
