On Thursday 17 May 2007 4:14 pm, David Kirk wrote:
> Robert,
>
> Here's a few things to check.
>
>
> Are you sure this is the copy of dhcpd.conf that is being used by
> dhcpd on your system? If you're editing the wrong file, then it
> doesn't matter how much you change it, it will never work.
>
> Also, you may have to restart dhcpd for changes to take effect.
Yes because if I make changes they are reflected in what the client tries to
look for when it boots.
> > {
> > 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.
>
> >
> > 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.
Rob
