Looking around the net some, I find the following little trick that can be used in the /etc/dhcpd.conf file :
Code:
shared-network WORKSTATIONS {
subnet 192.168.2.0 netmask 255.255.255.0 {
range dynamic-bootp 192.168.2.100 192.168.2.253;
use-host-decl-names on;
option log-servers 192.168.2.254;
# trick from Peter Rundle <peter.rundle@au.interpath.net>
if substring (option vendor-class-identifier, 0, 9) = "PXEClient"
{
filename "/lts/pxelinux.0";
# NOTE: kernels are specified in /tftpboot/lts/pxe/pxelinux.cfg/
}
else
{
filename "/lts/vmlinuz-2.4.21-ltsp";
}
}
}
and my reference board TRIES to boot. Got a good message in the /var/log/messages file - rpc.mountd: refused mount request from ws253.ltsp for /opt/ltsp/i386 (/): no export entry.
OOOps - have to edit the /opt/ltsp/i386/etc/lts.conf file - change references to 192.168.0 to be 192.168.2
[Default]
SERVER = 192.168.0.254
should be 192.168.2.254
It's looking in the wrong subnet for the server
(Also change RUNLEVEL = 5 to be a 2 instead... This would change the netbooted startup from an Xterminal log into the server to just a local bash shell - when the board boots, you can actually run things locally on the netbooted board. X isn't set up correctly to run, so you have to do this, I guess.)
And one last thing I found that I missed, you have to change the 192.168.0.0 entries in /etc/exports to be 192.168.2.254, then restart the NFS server with /etc/rc/.d/init.d/nfs restart
fiddle with /opt/ltsp/i386/etc/lts.conf - add nearly everything including RCFILE_01 = startfah to the default section.
add startfah to /opt/ltsp/i386/etc/rc.d with a /bin/bash --login -i
AND MY REFERENCE BOARD BOOTS and runs a bash prompt....
whew... tomorrow fiddle with /opt/ltsp/i386/etc/rc.local to mount a local /home on the netbooted card, change my fah script to start something in the home directory, and I'm ready to run DF on netbooted boards.
Notice that I don't tie my MAC addresses to any entries in dhcpd.conf file - I just let server pass out addresses to the netbooted boards.... Guess I'll have to change that - if you don't do the assignment, the client board doesn't receive a hostname....