On Tue, Oct 21, 2008 at 12:18:12PM +0200, Oded Naveh wrote: > Vagrant Cascadian Monday, October 20, 2008 8:55 PM > > you shouldn't need to specify that there at all, rather > > specify the root-path option in in dhcpd.conf: > > > > option root-path "/opt/ltsp/i386"; > > This works for the thin clients but not for the stateless workstations. > On my system starting a machine connected to 10.0.2.0/23 subnet, without > this declaration, results in looping: > Begin: Retrying nfs mount ... > ...<some correct network configuration from DHCP 10.0.2.2>... > Begin: Running /scripts/nfs-premount ... > Done. > nfsmount: need a path > Done. > Begin: Retrying nfs mount ... etc. > After (or while?) loading the kernel (modules?). > > Having "nfsroot=/opt/ltsp/i386" In > "/var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default" solves that. > Therefore it's reasonable to avoid overwriting this file or find another > work around.
something else must be broken with your DHCP setup, then. there isn't any magic to network booting a thin client vs. a diskless workstation. how would it work for one but not the other? > Would it be appropriate to file a bug against ltsp-update-kernels in this > case? take a look at /usr/share/doc/ltsp-server/FAQ "How do i configure boot prompt options" and http://bugs.debian.org/428446 another option, simply don't use the default generated pxelinux setup, but rather specify your own in a different location... i.e. use /var/lib/tftpboot/pxelinux.0 and your own custom /var/lib/tftpboot/pxelinux.cfg/default live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
