tftp config problem (ltsp)

[sean]

Paul Lussier wrote:

> 
> Blindly killing/restarting things is not likely to help.  Rather, it's
> more likely to cause problems.  Be deliberate and precise in what you
> do, don't flail blindly, you'll knock something over or poke someone's
> eye out.  And, as you know, it's all fun and games until someone loses
> an eye!
> 

Thanks Paul.

	I only killed a few things if I knew, or thought I knew what it should 
be doing. TFTP is working.

I have had a bit more success but still not over the summit.
Specifying in dhcpd.conf a certain setting for filename yields different 
results.


In my dhcpd.conf file if I set
filename "/pxe/prelinux.0"; the client will start the boot process.
After the DHCP output the screen will display

"TFTP prefix" /pxe/"

Then a series of lines stating Trying to load" pxelinux.cfg/"filename"
finally trying "default" in the end.
After this point I get

Could not find kernel image: linux
boot:

I know from reading the docs that this should mean the kernel is not in
the expected place.
In /tftpboot/lts I have either "bzImage-2.6.17.8-ltsp-1" or
"vmlinuz-2.6.17.8-ltsp-1".

I thought tftpboot/lts was the proper location?


The default file is located in /tftpboot/pxelinux.cfg

prompt 0
label linux
    kernel vmlinuz-2.6.17.8-ltsp-1
    append rw root=/dev/ram0 initrd=initramfs.gz

I have also tried the bz file as well. Same results.
I can only boot this far if I have filename "/pxe/pxelinux.0"; set in
dhcpd.conf .

#General Options
default-lease-time                      21600;
max-lease-time                          21620;
ddns-update-style                       ad-hoc;
use-host-decl-names                     on;
#authoritative;

#Boot Options
allow booting;
allow bootp;

#Network Options
option subnet-mask                      255.255.255.0;
option broadcast-address                192.168.0.255;
option domain-name                      "mydomain.net";
option domain-name-servers              192.168.0.1;
option log-servers                      192.168.0.11;
option routers                          192.168.0.1;

#LTSP Path Options
option root-path                        "192.168.0.11:/opt/ltsp-4.2/i386";
#filename                               "/lts/vmlinuz-2.6.17.8-ltsp-1";
filename                                "/pxe/pxelinux.0";
next-server                             192.168.0.11;

shared-network WORKSTATIONS
          {
          subnet 192.168.0.0 netmask 255.255.255.0
                  {
                  range dynamic-bootp     192.168.0.40 192.168.0.50;
                  }
          }

If I set filename to the vm or bz image mentioned earlier, I will get 
the "NBP is to large" error.
So far no idea how to cure this problem.

				Thanks
				Sean