TFTP error

[Gavin McCullagh]

Hi,

On Mon, 05 Feb 2007, Paul J. Thompson wrote:

> Hi Gavin, I was just doing that when you responded. Here is dhcp.conf

>  if substring( option vendor-class-identifier, 0, 9 ) = "PXEClient" {
>    filename "/ltsp/i386/pxelinux.0";
>  }
>  else{
>    filename "/ltsp/i386/nbi.img";
>  }
>  option root-path "/opt/ltsp/i386";
> }

> After doing a search, I cannot find " /ltsp/i386/pxelinux.0" or
> "/ltsp/i386/nbi.img" niether can I find the path "/opt/ltsp/i386"
> 
> There is a "/opt/ltsp/amd64" there is a /var/lib/tftpboot/ltsp/amd64 that
> contains pxelinux.0 but no nbi.img I am going to change dhcp.conf to point
> to /var/lib/tftpboot/ltsp/amd64/pxelinux.0 and the root path to
> /opt/ltsp/amd64. I am not sure about /ltsp/i386/nbi.img as there is no
> nbi.img

It appears your problem is that the ltsp-build-client built an ltsp
environment similar to that of your server -- ie an amd64 one.  However,
your dhcp server is set up to point everyone at the i386 directory where
the i386 image should be.  I presume your thin clients are i386 and not
amd64 machines, so you need to convince ltsp-build-client to build and i386
environment.

According to /usr/share/doc/ltsp-server/README.Debian you should be able to
run:
	ltsp-build-client --arch i386

to achieve this.  Then you can check that the i386 files are in place and
reboot the thin client.

Gavin