On Fri, Dec 28, 2007 at 04:05:22PM -0500, Theodore Flamouropoulos wrote: > Package: ltsp-server > Version: 5.0.39 debian1
thanks for the report. i suspect you mean 5.0.39debian1 ? > I also noticed that although tftpd-hpa and openbsd-inetd were packages > installed as dependencies, the 'tftp' entry in inetd.conf was not inserted as > part of the package install. consequently tftpd did not work when I tried to > boot the ltsp client. After I inserted the following entry --> > > 'tftp dgram udp wait root /usr/sbin/in.tftpd /usr/sbin/in.tftpd -s / > var/lib/tftpboot -r blksize' the tftpd-hpa package runs update-inetd as part of it's postinst by default, so you may want to explore what happened there and file a separate bug on the tftpd-hpa package for that. > into inetd.conf the ltsp client successfully received the kernel from the > tftpboot directory and began the booting process through the initial stage > until 'something went wrong' and I ended up staring at the following lines on > the ltsp client monitor: > > ------------------------------------------------------- > /init: 14: grep: not found > /init: 14: tr: not found > [: 14: 49152: unexpected operator > mount: No such device > mount: Invalid argument > /init: 14: tr: not found > Begin: Running /scripts/nfs-bottom > Done: > Done: > Begin: Running /scripts/init-bottom > mount: No such file or directory > Done: > mount: No such file or directory > mount: No such file or directory > Target filesystem doesn't have /sbin/init > No init found. Try passing init= bootargs > (initramfs)_ > ----------------------------------------------------------------------- sounds like it's missing "grep" and "tr" used by the ltsp_nbd script, and a recent change in initramfs-tools causes it to select ltsp_nbd instead of the nfs script, which doesn't use grep and tr... try adding boot=nfs to /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default although i'm still surprised that it would be missing grep and tr, as i've tested with nfs as well as ltsp_nbd with both physical thin clients and virtualbox thin clients. (though i would expect other things to break without additional manual configuration) live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
