On 8 Sep 2014, at 11:46 pm, ltsp-discuss-requ...@lists.sourceforge.net wrote:
> > Yeah, thank you for your answer, but the project you have referred to > considers RPi as Fat clients. Actually, I have played a bit with @gbaman's > project and I have to admit that it works. Nonetheless, RPi Fat clients are > extremely slow, because all the operations are calculated on target. What I > need is RPi as a Thin client. I will loose an opportunity to access GPIO, > but I will gain speed, for all the calculations will be performed on server > side. > > Best Regards > Pawe? Ptasznik > > 2014-09-08 13:29 GMT+02:00 <asmo.koski...@arkki.info>: > >> Mark Ellse m...@chasegrammar.com kirjoitti 2014-09-08 11:55: >> >>> For me, running LTSP extensively in a school, a small robust thin >>> client like RPi, running reliably with Edubuntu would be a dream >>> situation. >>> >>> Mark Ellse >> >> I think, the answer is here: http://pi.gbaman.info/?p=256 >> >> "A full 34 page userguide detailing all steps and troubleshooting help": >> >> http://pi.gbaman.info/wp-content/uploads/2014/05/small_Userguide-pi-ltsp-full-size.pdf I do. It’s easy. It works well. RPi as a stand alone machine running X on the ltsp server. All the heavy lifting is done on the ltsp server and frankly once it works why ever bother to upgrade the RPi. IE LTSP with the server doing the X but not the boot-run bit. James ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce. Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
