On Mon, Mar 10, 2014 at 09:14:37PM +0100, Larry Tucker wrote: > On the server machine, I'm running Debian Testing.
for future reference, try using ltsp-info to show specific information about your LTSP configuration. > On it, I would like to run ltsp, but not dhcp, which is already provided by a > D-Link router. (The router's IP address is 192.168.0.1. I have used the > router's user interface to give my server machine a static IP address: > 192.168.0.202. The rest of the machines are given dynamic IP addresses by > the router's DHCP service.) ... > Question 1: How to undo the changes made by the ltsp-build-client command? > I haven't found anything like an ltsp-remove-client command. rm -rf /opt/ltsp/* /var/lib/tftpboot/ltsp/* /srv/tftp/ltsp/* > Still following the above referenced instructions, I added "ipappend 3" to > the bottom of the file at /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default. > > I then created a file at /etc/dnsmasq.d/ltsp.conf and put into it: Your dnsmasq configuration didn't appear to include a setting for root-path: # The rootpath option is used by both NFS and NBD. dhcp-option=17,/opt/ltsp/i386 Try using ltsp-config to generate the dnsmasq configuration, as it should create a reasonable default, and has most options with comments: mv /etc/dnsmasq.d/ltsp.conf /etc/dnsmasq.d/ltsp.conf.old ltsp-config dnsmasq service dnsmasq restart > The "read: Connection refused" messages were repeated about once or twice > per second until, after a minute or so, came > > > NFS over TCP not available from 192.168.0.1 > connect: Connection refused > read: Connection refused It sounds like it's still trying to connect to the router's for NFS, rather than your LTSP server. This may be because you didn't have the root-path setting in dnsmasq. You also may want to specify in /opt/ltsp/i386/etc/ltsp/update-kernels.conf: # Commandline used with NFS root CMDLINE_NFS="root=/dev/nfs ip=dhcp boot=nfs nfsroot=/opt/ltsp/i386" IPAPPEND=3 And then run: ltsp-chroot /usr/share/ltsp/update-kernels ltsp-update-kernels You could also try the above with the corresponding CMDLINE_NBD= with nbdroot; I forget the syntax off the top of my head. Using NBD requires running ltsp-update-image after making changes to anything in /opt/ltsp/i386... NBD is noticeably faster to boot, but a little more hassle when troubleshooting because of ltsp-update-image. live well, vagrant ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _____________________________________________________________________ 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
