On Thu, Apr 14, 2011 at 08:32:37AM +0100, Rainer Stumbaum wrote: > I just did a fresh > ltsp-build-client --dist squeeze --mirror http://ftp.de.debian.org/debian/ > and strangely enough now this setup tries to boot from the last device it > finds (eth2) which is not > the one it should use (eth0). > At least it uses ipconfig now to get the dhcpd information.
ipconfig (as used in initramfs-tools in squeeze) should ask on all available interfaces, and takes the first that gives a DHCP response... do you have your thin client on multiple networks with DHCP on every network? > How can we force it to use the first device? > (still under the "nfsmount: need a path" error-description since it shows the > same error ;-) ). you can do a couple things: 1) set "ipappend 2" in /var/lib/tftpboot/i386/ltsp/pxelinux.cfg/default which passes the mac address of the network card it's booting and initramfs-tools will use the interface that matches that mac address. 2) in /opt/ltsp/i386/etc/initramfs-tools/initramfs-tools.conf hard-code DEVICE=eth0. then rebuild your initramfs: "ltsp-chroot update-initramfs -u" and update the tftp dir(s) "ltsp-update-kernels". hard-coding eth0 was the default on lenny, but typically didn't work well with multi-NIC setups if you wanted to boot from anything other than eth0. live well, vagrant ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _____________________________________________________________________ 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
