Hi jam, >>>> some general questions about LTSP5: We have numerous thin clients >> and multiple workstations. So far we use LTSP 4.2 to boot an OS and >> then use XDMCP to get on the workstations. Users often really need CPU >> power, so we can not just set up one LTSP server on which everyone >> works. We wanted to change to LTSP 5. It is much easier to install >> programs there via chroot. We'd like to have local device support. As >> far as I know, that does not work with XDMCP because it doesn't use >> SSH compared to LDM. >>>> So the final question: Is there any way to get local device support >> for multiple workstations and LTSP? This would be great. You're logged >> in on a workstation via the thin client, plug in the usb device and >> you can access it from the workstation's OS. >>>> >>> It is not that hard to set up direct ltspfs access in a ltsp5 >>> environment. The only trick is to have a coherent dhcp/dns setup in >>> order to have X cookies authentication working (otherwise you can >> just >>> disable it). >>> >>> You just have to set up properly a few udev rules, a few binaries >>> (ltspfsd, lbuscd, etc.) and startup scripts, and then you have >> access on >>> what ever ltsp tree you are using (being debian, ubuntu, opensuse, >>> mandriva or whatever) with ldm or not. > >> It would be really great if you could elucidate a bit. >> > > Denis every word makes sense, just when you put them all together, me > being a bear of little brain (Winnie ther Pooh - AA Milne) gets > confused. Please ...
sorry, me french, me english not good :-p > Jamrs Sorry if I was too confusing. What I wanted to underline is that you can look at ltsp project just as a base framework to make up for what ever thin client setup you want. The framework offer a way to boot a kernel on the network, an initrd, nfsrooting and then a few wisely written script to set up every thing properly. Kernel/initrd twicking is not too hard if you have some kernel compiling background. The only ltsp specific part is mainly to put all the network modules in the initrd file (obviously you need network to get nfsroot) and the nicely written ltsp linuxrc startup script, which in ltsp case takes care of getting network up and nfsrooting (usually network is taken care at init.d stage). Planting and growing a new ltsp tree is the trickiest part. You may install a base system of your choice in a chroot, copy over the ltsp specific binaries (rc.early_sysinit, rc.local, rc.sysinit, rc.localdev, getltspcfg, lbuscd, ltspfsd, ltsp_functions, ltspinfod, lp_server, etc.), some conf file like lts.conf and the ltsp specific udev rules, point the nfs export there, and then fire up a terminal and start debuging to see what is missing and what works. That's a little bit LFS-ish (one can make a pun diverting the acronym and calling it LTSP From Scratch :-), but nevertheless it is very interesting. Once one can get free from prepackaged ltsp and set up one on his own (actually it is the purpose of ltps5 to be distribution centric and not ltsp centric), then solving ltsp terminals issues is like solving issues between two fat clients. In my office we are somehow biased toward MandrivaLinux (yes, we are French...), so one day I just woke up and started to set up a new ltsp tree based on Mandriva distribution for some R&D project. In the end it looks like it does work not so bad. When I have time to clean up the thing a little bit, I'll post it somewhere. For Peter : as far as the initial post was concerned, I just wanted to underline that a ltsp client, once boot up, is more or less a standard linux desktop (for debuging you can chroot'aptitude install netstat tcpdump etc.). I'm not sure if the ubuntu ltspfsd binary has been compiled to just listen on the local interface (if it is the case, you can take the one from ltsp4.2, I'm sure it isn't). Otherwise connection/authentication should works in the same way as in ltsp4.2 (ie X cookie auth). I hope I have been a little bit less cryptic. Cheers, Denis > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _____________________________________________________________________ > 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 > -- Denis Cardon Tranquil IT Systems 44 bvd des pas enchantés 44230 Saint Sébastien sur Loire tel : +33 (0) 2.40.97.62.67 http://www.tranquil-it-systems.fr ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _____________________________________________________________________ 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
