> > I found the regression: > > udhcpc is called in init-premount to get the DHCP > configuration. > > The udhcpd used in the busybox does not ask the DHCP > server for the rootpath option. > > Adjusting the udhcpc call in > > > /usr/share/initramfs-tools/scripts/init-premount/udhcp > > with "-O rootpath" fixes my problem. > > udhcpc isn't part of the default LTSP install on Debian. > there are hooks to > use it if present. so apparently you've got a customized > install.
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. 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 ;-) ). Best regards Rainer ------------------------------------------------------------------------------ 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
