tftp config problem (ltsp)

[Paul Lussier]

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

> My in.tftpd
[...]
> I read that the -s option means secure and that the /tftboot
> is understood to be preceding the /pxe below?

I can not verify this. I do not have an in.tftpd file, I do not use
lts-whatever, and am therefore completely unfamiliar with it.

> filename                                "/pxe/pxelinux.0";

In theory, the dhcpd server will pass this path to the dhcp client.
The client will then use tftp to 'get /pxe/pxelinux.0'.  You should
verify manually from the command line, that you can do the same.

> When I specified the above in dhcpd.conf the client booted till it
> could not find the kerne

It will look for the kernel, based on the path specified in the
pxelinux.0/default file.  If you are specifying only:

  kernel foo

in the pxelinux.0/default file, it will look only in $TFTPROOT, in
this case /tftpboot, for the kernel.  I'm not completely sure of the
semantics of the pxelinux.0/default file syntax.  You *may* be able to
specify:

  kernel lts/foo

but I'm not sure.

> When filename was setup as
>
> filename                               "/lts/vmlinuz-2.6.17.8-ltsp-1";
>
> The client tried appeared to pull the file. I received a NBP is too
> large error. That would seem to be that the file is transferred.
> My next server is by IP.

Well, right.  You're restricted to about the size of a floppy for a
bootable image, especially over tftp.  Which means, if you bootable
kernel is larger than about 1.4M, it's not going to work.

It seems like you need to develop a deeper understanding of the
relationships between the dhcp and tftp server and how pxelinux works.
It's not overly complicated, but can be confusing, since there's a lot
of indirection going on.  The DHCP server tells the client "go over
here and get this file", that "file" says "boot me, then go over there
and get that other file", which then says...

-- 
Seeya,
Paul