Hi Oliver,<br> well, my explanation was pretty bad I guess, but this is the way drbl works, from what I understand of it. At least during setup, I see it setting up nodes, based on ip, for every client. Now... it may be its not the entire chroot, but just parts of it... In any case, it uploads these files to the client's swap space or ram so the client takes the burden and not the server.
<br><br>Anyway I would love to know a better way to make workstation thin clients using LTSP instead... any ideas?<br><br><div><span class="gmail_quote">On 10/30/07, <b class="gmail_sendername">Oliver Grawert</b> <<a href="mailto:ogra@ubuntu.com">
ogra@ubuntu.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">hi,<br>Am Dienstag, den 30.10.2007, 14:23 +0100 schrieb David Van Assche:
<br>> Hi Nicolas,<br>> I looked into the possibility of using edubuntu as a thin client<br>> server for 'fat clients', sometimes called workstations... Basically,<br>> each client gets its own chroot
<br>thats a pretty insane setup, why not use the same chroot for all users<br>and mount /home from the server, user settings and data are only saved<br>in the home dir so there is no point in having a gigabyte sized chroot
<br>for everyone that only duplicates the system files multiple times ...<br><br>ciao<br> oli<br><br>--<br>edubuntu-users mailing list<br><a href="mailto:edubuntu-users@lists.ubuntu.com">edubuntu-users@lists.ubuntu.com
</a><br>Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/edubuntu-users">https://lists.ubuntu.com/mailman/listinfo/edubuntu-users</a><br><br><br></blockquote></div><br>