AFAICT, eth0 is started automatically by the default boot process and udhcpd is started by the entry in bootlocal.sh.
The automation just starts eth0.sh from bootlocal If you take a look now, it should be there. Move it before udhcpd, and remove the '&'.
TC's boot is a bit mixed, parts are generic, parts are unique.
Thanks. The machine's at work, so I'll have to look in the morning.
Your help is much appreciated.
I did have a look in the morning and udhcpd did appear to be working. Thanks again for that. However, I then moved on to getting a DNS server to work and hit a few more problems.
Being new to all this, I searched these forums and found that some people seemed to favour dnsmasq, so I tried that, with no success. Whatever I did, the client would get an IP Address, but no name resolution. I then spent a bit of time trying to set up named, with similar results. One problem I had is that I've found it difficult to be sure that the program starts without errors. I enable syslog in the boot codes, but TinyCore doesn't seem to have any more useful logs. Have I missed something?
Apart from that, I discovered (by accident, because it's not mentioned on these forums), that BusyBox provides a DNS server (dnsd). The config for this appears to be simple and I seem to have a running DNS server; here is the output of ps ax|grep dns:
2777 root /usr/sbin/dnsd -c /etc/dnsd.conf -i 192.168.0.1
3661 tc grep dns
but still no name resolution.
In my udhcpd.conf file I have:
opt dns 192.168.0.1
so can anyone suggest why the client isn't getting the IP address of the nameserver?
BTW I've been running Wireshark and have seen quite a lot of DHCP transactions (as you'd expect), but nothing that idicates that DNS is working other than requests for who has this or that IP.