Robert,
> > {
> > filename "/tftpboot/lts/2.6.16.1-ltsp-2/pxelinux.0"; #<--Check
> > version
>
> Should this be "/lts/2.6.16.1-ltsp-2/pxelinux.0"?
Don't think so as it was taken from the sample - perhaps worth a try though.
If your tftpd is using the "-s" option (which it says it is), then you
shouldn't need to put the "/tftpboot" bit in there. /tftpboot becomes
the root directory for any tftp clients.
> > group {
> > use-host-decl-names on;
> > # Counter computer
> > host ws001 {
> > hardware ethernet 00:50:fc:69:c7:da;
> > fixed-address 192.168.1.150;
> > filename "/lts/vmlinuz-2.6.17.8-ltsp-1";
I think this is "nearly there" as the client gets the correct IP address but
hangs on trying to load the kernel image.
>
> Does /tftpboot/lts/vmlinuz-2.6.17.8-ltsp-1 exist?
Yes it does but I just had a thought that maybe there is incorrect case in the
filename - will check tomorrow - clutching at straws at the moment.
>
> > option root-path "192.168.1.11:/opt/ltsp/i386";
> > }
>
> Are your clients using PXE or some other sort of network booting?
Well I think the network booting must be OK for it to get as far as it does.
Is that a fair assumption.
What I meant was "which type of network booting are you using" (PXE,
etherboot floppy or other)?
If you are using PXE, check that the kernel listed in
/tftpboot/lts/2.6.16.1-ltsp-2/pxelinux.cfg/default is correct.
--
Later
David Kirk
