... >> Honestly I thought using the "ltsp-build-client" command would transfer >> all this into the chroot of the clients. >> > > No. Did you run ltsp-build-client and try booting a client? Do this, > log in as one of your users and see how it works. > > Thats what I expected > db > > Sorry, my fault. So here is what I did: I installed the ltsp-server-standalone package from the Lenny repos. used the 'ltsp-build-client' command, which finished with a success message I edited /etc/dhcp3/dhcpd.conf and /etc/ltsp/dhcpd.conf as mentioned in: http://wiki.debian.org/LTSP/Howto, which I followed further on (exports, restarting services..)
My client boots (with a kernel image from rom-o-matic), I get a login screen. But no user is able to log in. I changed to text console (F1) on the thinclient and get an error message "login incorrect", which is wrong. (created a dummy user with passwd dummy, so hardly a typo). any group settings I miss? I excuse for any confused writing Frank ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _____________________________________________________________________ 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
