Folks, A little background ..
We are keen to stick with dapper for servers, for Long Term Support. I installed dapper, and (from dapper) all the listed dependencies for /edgy/ ltsp-build-client. I then installed edgy ltsp-build-client, pointed it to an edgy repo, and ran it. So, I have a dapper server, and an edgy client. I know there will be some issues trying to log in, but at the moment I just want ldm to come up on the client. An identical setup on Debian sarge (copy of /opt/ltsp, dhcpd.conf) worked great. I copied it from the non-working dapper setup. I just need it to work on dapper. On the client, it gets as far as "Running: /scripts/init-bottom" from the initrd, and then times out - nfs: server 192.168.42.1 not responding I turned logging on, the server indicates successful mount. Dec 5 11:22:28 musselcracker mountd[4045]: authenticated mount request from owl.aims.ac.za:995 for /opt/ltsp/i386 (/opt/ltsp) There are no firewall rules, nothing in hosts.allow/deny. Where should I start looking ? Cheers, Andy! ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _____________________________________________________________________ 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
