tftp config problem (ltsp)

[Paul Lussier]

sean <tech.junk at verizon.net> writes:

> I am trying to get LTSP working here.
> All appear on the right track with one apparent problem, tftp'ing the file.
>
> When I boot a client it appears to pull in the network information but 
> when it starts to tftp the file, I receive a message that the file is 
> not found on the client display.

A good way to debug tftp is to use it from the command line:

 $ tftp ww
 tftp> get foo
 Error code 1: File not found
 tftp> get vmlinuz-2.4.31pcore-a.13
 tftp> q
 pll at ethics-gradient - /tmp#[823]
 $ ls -l vmlinuz-2.4.31pcore-a.13 
 -rw-r--r-- 1 pll staff 1322415 Nov  6 09:38 vmlinuz-2.4.31pcore-a.13

So, from the command line, run tftp and connect to your tftp server
and try to get some file you know exists.  Remember that tftp
effectively chroots you to $INTFTPD_PATH. Therefore, whatever file you
need to 'get' will have to be in the form of a literal path with that
in mind.

If you've set $INTFTPD_PATH to /tftpboot, you can not specify a DHCP
server "filename" option for some path that is NOT downn /tftpboot.

Which is exactly what you're doing :)

For example:

  My inetd.conf file specifies:

    tftp dgram udp wait root  /usr/sbin/in.tftpd /usr/sbin/in.tft pd \
    -s -r blksize /boot/fai

  That last argument is the tftp root directory.

  My DHCP config specifies:

    next-server fai;
    filename "pxelinux.0";

Guess where "pxelinux.0" lives ?  In /boot/fai.
-- 
Seeya,
Paul