DRBL and Technology
Todd O'Bryan
toddobryan at gmail.com
Wed Nov 24 03:35:55 GMT 2010
OK, still trying to clarify this...
I create a fat-client chroot that has a bunch of stuff in it. In
particular, in my lab I teach programming, so I've got a few
programming languages installed, Google Chrome, etc. Then I run
ltsp-update-kernels, ltsp-update-image, and ltsp-update-sshkeys, just
to make sure everything got updated.
Now, does the fat-client download *everything* in the chroot into RAM,
or does it mount the chroot remotely and only download what it needs
to boot, loading the other stuff from (the server's) disk as it needs
it? I guess what I'm asking is, is the part that the client gets over
the network to boot considerably more for a fat-client than a
thin-client, or is it about the same, with the fat-client then
mounting the files it needs on the server?
Todd
On Mon, Nov 15, 2010 at 5:51 PM, Jonathan Carter (highvoltage)
<jonathan at ubuntu.com> wrote:
> Hi Todd
>
> On 10-11-15 05:22 PM, Todd O'Bryan wrote:
>> What if the thin clients are i386 and the fat clients are amd64?
>
> You'll have to have separate i386 and amd64 chroots. Typically though,
> i386 images are used for both.
>
>> Also, I guess I'm not understanding something about how the chroot
>> works. Do I not install the packages I want to run locally in the
>> chroot for the fat clients? If so, does the fat client "just know" to
>> download the binary the first time something is run so that it runs on
>> the local machine instead of the server?
>
> Yep, you'll need to install them in the chroot. You could then run them
> by doing "ltsp-localapps appname" to run it locally. You can also
> specify which applications you want to run locally in lts.conf, and the
> user menus will then be modified to run those programs with ltsp-localapps.
>
> -Jonathan
>
> --
> edubuntu-users mailing list
> edubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
>
More information about the edubuntu-users
mailing list