Hi Jim,    The one thing to remember is that the ltsp-client-core part of the startup process does certain things like auto-configure X, create an automated fstab with detected devices, and so on. One would have to look at ltsp-client-core and ltsp-client-setup to understand exactly what it does at setup and startup. But I believe it would be better to explode the necessary items in the thin client chroot after an ltsp-build-client. I believe the ltsp startup parts are still quite valuable and will allow for upgrades without breaking anything, which is what I have tried to do in the wiki, by utilising elements like XF86CONFIG= and RC_FILENN= in lts.conf.    I know Ogra is looking into creating a script that does all of this automatically, but it is still a ways off (hardy+1 maybe?), but if you find it possible to do it the way you mentioned, please document it and add to the wiki... There are invariably many ways to achieve the same end result, but working with the ltsp structure so we can upgrade the environments as and when we need to will be important. David <div class="gmail_quote">On Feb 13, 2008 8:55 PM, Jim Kronebusch <<a href="mailto:jim@winonacotter.org">jim@winonacotter.org</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> On Wed, 13 Feb 2008 00:42:29 +0100, David Van Assche wrote <div><div></div><div class="Wj3C7c">> Hi there, >    I've recently documented the steps needed to make alternative fat chroots > with local apps and local cpu/memory usage. So called ltsp diskless > workstations, or low fat clients. The wiki is here, and though is not > complete, Ive tested it and it works (I am running it on 20 computers in my > computer lab that require multimedia apps, aswell as flash, java, video, > audio, etc. Take a look here and feel free to add to it or ask me questions: > > <a href="https://help.ubuntu.com/community/UbuntuLTSP/LTSPFatClients" target="_blank">https://help.ubuntu.com/community/UbuntuLTSP/LTSPFatClients</a> > > Kind Regards, > David V. </div></div>Very cool David.  Thanks for your work in documenting this.  I will be likely installing 50 "Low Fat" clients this summer in addition to our existing 108 thin clients (I think the name "Low Fat" by the way is awesome :-).  The thin clients will be for students, the low fat clients will be new full power machines for teachers. I am wondering if there is any reason one couldn't install a workstation as normal, tweak things, then copy the workstation directories over to the server into /opt/ltsp/lf_i386?  I think this is how it is recommended to build a PPC client tree, so I don't see why this wouldn't work.  If this is possible, would anyone care to provide instructions as to the best way to do this? Right now I have 3 teacher machines that are the test pilots for this over the summer. They are identical hardware, and are already completely configured for mounting /home and auth to ldap.  The only piece left for them is to get them booting from the server.  I would love to simply move the contents from one of these completed machines over. Thanks, Jim -- This message has been scanned for viruses and dangerous content by the Cotter Technology Department, and is believed to be clean. </blockquote></div>