[nSLUG] difficulty with ltsp

Dop Ganger nslug at fop.ns.ca
Tue Oct 11 10:33:24 ADT 2005

On Sun, 9 Oct 2005, J. Paul Bissonnette wrote:

> I have managed to get ltsp to work up to the point where my notebook give me 
> a message
> client nic addr: xx:xx:xx:xx
> client ip: dhc IP:
> gateway ip;
> tftp.
> PXE-T01    file not found
> pxe-e3b: tftp error file not found
> Oct  8 21:41:58 maple atftpd[5574]: Serving /tftpboot/lts/vmlinuz-2.6.9-ltsp-3 to
> Oct  8 21:41:58 maple atftpd[5574]: Serving /tftpboot/lts/vmlinuz-2.6.9-ltsp-3 to

Some tftp servers implicitly add /tftpfboot to the start of the path. Some 
tftp servers need it explicitly added. A certain tftp server I used in the 
past broke if you used any path on the filesystem other than /tftpboot to 
store kernels on. This bit me several times when I was playing around with 
it (at one point I had a symlink /tftpboot/tftpboot pointing at 

On my boot server at home, I have all the kernels in /tftpboot. The 
xinetd.conf entry looks like this:

service tftp
        socket_type     = dgram
        protocol        = udp
        wait            = yes
        user            = root
        #server         = /usr/sbin/tcpd
        #server_args    = /usr/sbin/in.tftpd /tftpboot
        server          = /usr/sbin/in.tftpd
        server_args     = -v -s /tftpboot
        disable         = no

The tftp server I'm using is HPA's tftp server, available as tftpd-hpa as 
a Debian package or from http://www.kernel.org/pub/software/network/tftp/ 
if you want to compile from source. I've used this to successfully boot 
PXE clients, HPPA rboot clients and Sun Sparcs.

Cheers... Dop.


More information about the nSLUG mailing list